Questie

Questie

116M Downloads

No Tracker - SortID : 0 was not found in the database

YoShiiro opened this issue ยท 9 comments

commented

Bug description

When i load the wow TBC session i got this error below, and no tracker appear, but the rest of questie work (item on map & quest announce in chat). I've try to delete folder / WTF but still have this problem.

And the strangest things is that i got this error on one account, my second account got no problem tracker & quest.

_ Questie: [ERROR] SortID: 0 was not found in the Database. Please file a bugreport at:
Questie: [ERROR] https://github.com/Questie/Questie/issues _

Screenshots

image

Questie version

Question version 6.6.4

commented

See #3222

commented

These are different issues I think. The quests in #3222 had no sortID, not 0.

commented

Oh right. You are correct. This issue maches the one that was on Discord earlier. #3222 is maybe different, at least it manifest itself differently.

commented

stream:WriteShort(32760 + (value[questKeys['zoneOrSort']] or 0))

commented

It is the same. Most users don't have lua errors enabled, so they see only the message in chat. And seems some who have lua errors enabled ignore the chat message.
#3222 tried to compare number to string.

if zoneorsort is <0 or >0 it gets converted to string. while 0, it stays as 0. Imo another bug, which should be fixed. And while fixing the sort function should be declared before passed to function.

commented

I'm having the same issue on a new boosted character after accepting the Boost-related starter quests that get you some gear, skills and send you off to the Dark Portal.

All my other characters on this account work just fine!

For the record, the suggested temp fix in the #3222 thread to disable tracking sorting works and I can now see the tracker again (albeit unsorted).

commented

@NordikaMan Check #3222 for temporary solution

commented

@NordikaMan Check #3222 for temporary solution

Haha I was just editing my comment to say that temp fix does indeed work :) tyty

commented

Fixed by eaa009f in release v6.7.0, which available to download.