Trying to use events deal with it was impossible, or at least highly problematic, given that the ones that trigger before the 'tween zones' kick of QUEST_LOG_UPDATE fire damned often.
I eventually just decided to scan a table of completed IDs then compare that before and after scan of the quest log. Since the scan only ADDs quests to the table (and they're removed fro it by QUEST_REMOVED), it provides the count data that the list should provide.
I think QUEST_LOG_UPDATE now suffers from the same issue that, er, crap, WORLD_MAP_something does where it returns 0,0 as interim coordinates from the nether region between one zone and another.
|