event QUEST_ACCEPTED getting weird arg

webtaz99 · 07-15-23, 09:42 AM

Sometime before Dragonflight, I started getting weird questId values in my quest tracker.
Lua says it's a table. All the documentation says it should be in int.
I get stuff like 000002067A296EE0 or 0000023BDDFEF130.

Obviously the game operates normally, but what change in the API is causing this?

Fizzlemizz · 07-15-23, 10:08 AM

Are you sure you didn't accidently change your code and are seeing the frame (self) that is processing the event rather than the first argument in the payload?

It might help to see your code that registers, sets and process the OnEvent scripts.

webtaz99 · 07-17-23, 04:14 PM

Thanks! Got it working.
Sure enough, Blizz is now sending a userdata table before the questId.
Strange that etrace doesn't call that out.

Kanegasi · 07-17-23, 07:19 PM

The first arg given to every function attached to a frame with setscript is the frame itself.

QUEST_ACCEPTED has only one return on retail: the quest ID.

Blizzard didn't change anything, that "user data" is the frame you registered the event to. Somehow you changed something, most likely a simple : to . in how you handle events, which caused your first arg to be the frame instead of the quest ID.