-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
fix(Scripts/BlackTemple): Adjust order of damage calculations for Shared Rule. #19849
fix(Scripts/BlackTemple): Adjust order of damage calculations for Shared Rule. #19849
Conversation
another problem is. because can't kill the 4 boss, I use .die kill all, but the instance can't out of combat.
also when time is 120s, the spell can get by magic class also 120s, so there is 100% after 120s, the magic will no buff and might die , so I changed to also when the SPELL_BLESSING_OF_SPELL_WARDING at the magic boss, the magic class cant get buff form the boss, might need cant do the buff to the magic boss this my fix before half a year |
This PR should make the council killable, so your first fix should no longer be needed. |
I know, but cant out of combat seem still will happen. |
and my fix only on my branch not pull to master branch, but it does solve the uncontrollable problems of not being able to get out of combat and mages not being able to steal buffs in time or not being able to steal buffs because boss protect spell. |
Tested |
For the record, this could be the reason why you can't leave combat, because the fight doesn't actually end properly. These creatures are supposed to be killed by script, their death isn't what actually causes the encounter to end. |
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
SOURCE:
The changes:
Tests Performed:
This PR has been:
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.