-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(ICC/Sindragosa): add a cooldown to proccing Unchained Magic #18901
fix(ICC/Sindragosa): add a cooldown to proccing Unchained Magic #18901
Conversation
From what I can tell, it does seem they're only supposed to apply a stack on the initial cast, so one stack seems to be correct. |
Tested d73da98 |
I'm positive there is a database table that handles ICD on procs |
https://www.azerothcore.org/wiki/spell_proc#cooldown table is empty https://www.azerothcore.org/wiki/spell_proc_event#cooldown
potential fix, will try it out later |
…othcore#18901) * add cooldown to proc * convert to spell and aurascript pair macro * remove no longer needed validate override * set cooldown with Cooldown field in table spell_proc_event
…othcore#18901) * add cooldown to proc * convert to spell and aurascript pair macro * remove no longer needed validate override * set cooldown with Cooldown field in table spell_proc_event
Changes Proposed:
This PR proposes changes to:
first commit contains the logic changes: 25b6102
Issues Addressed:
SOURCE:
The changes have been validated through:
a OG wrath PTR video shows the effect, debuffs are shows on the right
4:21 shadowbolt -> agony, delay ~1second, 2 stacks
https://youtu.be/ezuDqODdADA?si=fj_1bPlF5LagoOia&t=261
6:11 shadowbolt -> agony, delay <1 sec, 1 stack
https://youtu.be/ezuDqODdADA?si=i85-7vyBFM9rTn_M&t=370
Tests Performed:
This PR has been:
How to Test the Changes:
learn healing touch, rejuv
learn shadowbolt, corruption
tp to sindy's room
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.