yes.. Ive read that tutorial several times, however what Im saying is the
quest::setglobal([varname],[value],[options],[duration]);
command, after used once, doesnt want to modify the value again.. like if it was originally 0.. then I change it to 1,.. when I change it to 1 it creates the variable and sets it to 1.. but when I try to use it again, and put in
quest::setglobal("zavious",2,0,"M2");
for instance, it doesnt change the variable zavious to 2 like it says in that tutorial..
Ill quote:
"setglobal
quest::setglobal([varname],[value],[options],[duration]); (perl format)
The setglobal command allows you to create or
modify an existing global variable for the mob you are using the command on."
If the variable exists, and its currently set at 1, this command will not modify the variable and change it to 2.
Quote:
|
Originally Posted by ylosh
the quest tutorial wiki page explains everything else pretty well.
|
so yea.. like I said.. Ive done all the reading.. searching.. and everything on here.. Ive searched peq's site as well.. I wouldnt post unless I completely didnt understand, and have searched in every possible manner. I read in peq's site that its a problem with qglobal. Im wondering if this is true.
If I can figure out how to update a global variable up to like 5 different times on 1 npc I would be set. I need to make it where people can only do 1 step at a time, not skip steps and not do steps more than once in a single npc quest. I cant do that when quest::setglobal doesnt modify the variable like specified in the wiki..:( Is anyone else having problems with this? If so, is there any other way to do this if globals dont update more than 1 time?
Threaded Mode
