🐛 [Bug Report] [TBC] Server Crash when adds spawn in Razorgore the Untamed event #2677
Assignees
Labels
Info: Needs Replication
Issue needs replication before further action.
Comments
Trystanosaurus
added
the
Info: Needs Replication
|
for future reference, if you want to paste a block of text on github use ```the text``` so that it is formatted correctly. I'll look into it. |
|
OK, got a fix for it. But this has uncovered some issues with Anti-Cheat that need to be looked into some. I'll create a PR for the fix but I want to keep this issue open for the Anti-Cheat issue After some time of controlling the orb the user is kicked from the server: |
1 task
|
The Anti-Cheat might need some exceptions, for example spells on him that modify the movement |
|
I think the same thing's happening on Gluth in Naxxramas, when he summons zombies the server crashes. |
|
should be solved by the same PR |
killerwife
added a commit
to cmangos/mangos-classic
that referenced
this issue
Feb 17, 2022
…is not yet existant Happens during Creature Create, all calls needs to be after spawning. We can not silently fail Creature::CallAssistance because it will lead to it not working Closes cmangos/issues#2677 Closes cmangos/mangos-tbc#508
killerwife
added a commit
to cmangos/mangos-wotlk
that referenced
this issue
Feb 17, 2022
…is not yet existant Happens during Creature Create, all calls needs to be after spawning. We can not silently fail Creature::CallAssistance because it will lead to it not working Closes cmangos/issues#2677 Closes cmangos/mangos-tbc#508
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Details
In the Razorgore boss fight the server crashed 40 seconds in, when the first wave of adds should spawn.
I had a look at the log with log level 2 and there wasn't anything obvious to me, the last few frames of the log are below.
I was playing solo on a server with ahbots and bots enabled (though no bots in game when the crash happened).
Steps to Reproduce
Expected behavior
The server shouldn't crash
Suggested Workaround
No response
Crash Log
Core SHA1 Commit Hash
88d1de3d6033b8acd98d55eb44ef8c7f455f24f2
Database SHA1 Commit Hash
72ece9baa24cbdff43ea0ced3b21dfdf80df70e6
Operating System
Windows 10
Client Version
2.4.3 (The Burning Crusade)
The text was updated successfully, but these errors were encountered: