Build 944 and Quest Globals

Dymerius · #1 01-19-2007, 07:40 AM

I saw in the change log that an issue with quest globals expiring had been fixed, but I'm still having issues in 944 with quest globals not working.

Can someone fill me in on the current status? Is this a problem on my end or are there still problems in this build?

Thanks in advance

Angelox · #2 01-19-2007, 11:23 AM

whats your problem with globals? they work for me- and I'm the big "global whiner", ask anyone

EDIT;
Ok , I see, the fixes are not out yet - next update will have them

Dymerius · #3 02-05-2007, 10:31 AM

I am still having problems with quest globals in 948. Any new info?

bleh · #4 02-09-2007, 11:46 AM

The old method to access quest globals is to use $varname. The new way is $qglobals{varname}. This gives globals their own namespace inside of the %qglobals hash. The older style should be considered deprecated.

Angelox · #5 02-09-2007, 12:19 PM

You mean EQEmu-0.7.0-949? i think that would be the version that has the fix. Also, did you fix the table in the mysql database?

Code:

ALTER TABLE quest_globals CHANGE expdate expdate INT;

Won't work if you don't fix the table.
Forget about all the other fixes - the true, working fix (by Bleh) is in EQEmu-0.7.0-949 before that either it was thought to be in, or was not in right.
951 and 965 do not reflect fixes in the logs yet, but I'm sure 949 and up have the true fix.