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

World Server Crash #8

Open
jshplayer opened this issue Sep 27, 2023 · 2 comments
Open

World Server Crash #8

jshplayer opened this issue Sep 27, 2023 · 2 comments

Comments

@jshplayer
Copy link

Certain cases where the reagent banker is attempting to locate an item that no longer exists causes a world server crash.

AddGossipItemFor(player, GOSSIP_ICON_MONEY_BAG, GetItemIcon(itemEntry, 30, 30, -18, 0) + GetItemLink(itemEntry, session) + " (" + std::to_string(entryToAmountMap.find(itemEntry)->second) + ")", itemEntry, gossipPageNumber);

#2 0x0000000000ab009b in AddGossipItemFor (player=player@entry=0x7fad9c4fcd40, icon=icon@entry=6, text=<error: Cannot access memory at address 0x232d2d2d2d2d2d2d>, sender=0, sender@entry=11370, action=2206496960) at /home/x/azerothcore-wotlk/src/server/game/AI/ScriptedAI/ScriptedGossip.cpp:30

@ZhengPeiRu21
Copy link
Owner

When you say an item no longer exists, do you mean that the item_template for this entry has been deleted from the database?

@jshplayer
Copy link
Author

I'm assuming a little here but I think it's when the gossip menu is navigated very quickly and an item no longer exists within storage as it was recently withdrawn however gossip is attempting to locate it? Possibly a clause to handle events where an item cannot be located would help?

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