fix(Scripts/Naxxramas): Thaddius casting Ball Lightning shouldn't pr…#24624
fix(Scripts/Naxxramas): Thaddius casting Ball Lightning shouldn't pr…#24624Nyeriah wants to merge 7 commits intoazerothcore:masterfrom
Conversation
…event other spells
There was a problem hiding this comment.
Pull request overview
This PR fixes an issue where Thaddius in Naxxramas would stop casting Chain Lightning and Polarity Shift while spamming Ball Lightning when players were out of melee range. The fix removes the UNIT_STATE_CASTING check that was blocking event execution and refactors the berserk mechanic to use the modern ScheduleEnrageTimer method.
Changes:
- Removed UNIT_STATE_CASTING check to allow Chain Lightning and Polarity Shift events to fire while Ball Lightning is being cast
- Refactored berserk timer to use
ScheduleEnrageTimerinstead of a manual event - Updated spell casting to use helper methods (
DoCastVictim,DoCastAOE) for cleaner code
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Tested: https://youtu.be/jPIS6HrLWJQ In addition, after you kill Stalagg and Feugen this error appears (but this isn't your PR's fault):
|
|
this pr could be test 2 character (?) |
When handling EVENT_THADDIUS_POLARITY_SHIFT, check if the boss is currently casting and, if so, defer the event by 1s and disable ball lightning until the cast completes. Also schedule EVENT_ALLOW_BALL_LIGHTNING 3s after successfully casting SPELL_POLARITY_SHIFT. This prevents overlapping casts and ensures ball lightning is re-enabled at the correct time.
|
Please retest |
Tested. Thaddius casts Ball Lightning and Polarity Shift (I didn’t see Chain Lightning being cast). |
not related to this PR by any means but widespread error in the core |

…event other spells
Changes Proposed:
This PR proposes changes to:
AI-assisted Pull Requests
Important
While the use of AI tools when preparing pull requests is not prohibited, contributors must clearly disclose when such tools have been used and specify the model involved.
Contributors are also expected to fully understand the changes they are submitting and must be able to explain and justify those changes when requested by maintainers.
Issues Addressed:
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
Known Issues and TODO List:
How to Test AzerothCore PRs
When a PR is ready to be tested, it will be marked as [WAITING TO BE TESTED].
You can help by testing PRs and writing your feedback here on the PR's page on GitHub. Follow the instructions here:
http://www.azerothcore.org/wiki/How-to-test-a-PR
REMEMBER: when testing a PR that changes something generic (i.e. a part of code that handles more than one specific thing), the tester should not only check that the PR does its job (e.g. fixing spell XXX) but especially check that the PR does not cause any regression (i.e. introducing new bugs).
For example: if a PR fixes spell X by changing a part of code that handles spells X, Y, and Z, we should not only test X, but we should test Y and Z as well.