A wise man once told me he'd recommend using ini files over globally named variables 99% of the time, he was correct.
Use that to set your values instead, they're very easy to deal with once you've gotten started.
Here's the syntax:
Writeini Example.ini Section Item Value
Turns out like this:
Example.ini
[Section]
Item=Value
-
To get the value you use $readini. Syntax:
$readini(Example.Ini,Section,Item) which will return: Value
Use the helpfiles for further reference. You won't regret it.
I already do you use ini files for other storage of user and channel data, but at this current time I feel this does not require it as I am not storing many values; I am only storing 3 values, so I figure that just using a few dynamic variables would save the time and keep them parted for me to retrieve later on while I test a few things for now.
Although in the future I will transfer this data to an ini to be read from, I would rather stick with just a couple of dynamic variables to test and ensure each of the executed commands are properly working on my end.
