Closed luis-ortiz closed 5 years ago
Do you happen to know what you were doing at the time (like zone or map, etc.)?
It just happened right now on a Blood DK about his mail in Stormwind near the Dwarven District AH. Right after login.
Were you playing on a European server by any chance?
Nope. NA, Garrosh.
BTW, I threw this line in just before the bad access:
print(string.format("questId=%q, codePrefix=%q, quests[questId]=%s",questId,codePrefix,tostring(self.quests[questId])))
And the last thing printed on my Alliance DK was:
questId="48602", codePrefix="I", quests[questId]=nil
The same last line was printed on my void elf on the same server.
That questId is not valid, but I see it in:
Grail-Quests.lua:G[49787]='FA K0000 L110 N120 A:126321 T:130919 P:50239+48602'
And indeed, all I can cause the error on all my alliance toons, by enabling Wholly.
That's definitely it. I was never able to debug that since none of my characters fell into that pitfall. Perhaps I should have started a new character. At least now I can track down what the fix is. I should be updating GitHub soon. Thanks a ton.
The latest release should fix this from both removing the bogus questId and checking for nil.
It is fixed, thanks!
Cool.