You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
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
The text was updated successfully, but these errors were encountered: