Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

looting items are broken after ulduar patch (wotlk classic) #16

Open
dh-harald opened this issue Jan 20, 2023 · 4 comments
Open

looting items are broken after ulduar patch (wotlk classic) #16

dh-harald opened this issue Jan 20, 2023 · 4 comments

Comments

@dh-harald
Copy link

Hi,

It looks, not updating every time when I loot something. sometimes it's working but usually it's not.
for example I'm looting couple of items in a dungeon and not showing them, and after I HSing/teleporting to Dalaran, it shows all the items bulky.
Maybe some event missing, like known BAG_UPDATE_DELAYED

@syndenbock
Copy link
Owner

People have reported this issue already but I couldn't reproduce it while questing, so narrowing it down to dungeons is very helpful already. Unfortunately I only have a level 7 character on WotlK classic so I cannot go into dungeons to check it myself.

That indeed sounds like BAG_UPDATE_DELAYED is not being fired by the game because that's the event I'm using to check what changed in the bags. Do you have any means to check if the event is fired while in dungeons?

@syndenbock
Copy link
Owner

I have looked around on the UIDev Discord and people are reporting that the game does not reliably fire BAG_UPDATE_DELAYED in the current WotlK classic patch. This hopefully gets fixed by Blizzard because I don't think there is a reliable workaround.

@dh-harald
Copy link
Author

I runned etrace, and it looks, the BAG_UPDATE_DELAYED event is still missing... I tried to debug it, but after 3 BAG_UPDATE there was no BAG_UPDATE_DELAYED (and the addon didn't showed any loots)

@syndenbock
Copy link
Owner

I implemented a workaround that should hopefully work. Once Blizzard fixes the issue on their side, I'll remove the workaround and close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants