fix(Scripts/Spell): Priest shadowfiend attack and Shadowfiend Death proc #20987
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes Proposed:
This PR proposes changes to:
removes petAI hack and move auras/proc handling to DB/spellscript
note that when targeting a neutral mob and cast shadowfiend. It does not attack. If right-click, and then summon, it does attack.
SUMMON_PROP_FLAG_ASSIST_COMBAT_SUMMON
is not set. Feral Spirits, Treants, Fire Elemental have the same behavior. I think this is correct behavior for a guardianIssues Addressed:
SOURCE:
The changes have been validated through:
cp Priest: Implement missing glyphs and move existing to spell cmangos/mangos-wotlk@3b1dfe0
Tests Performed:
This PR has been:
How to Test the Changes:
regression:
Known Issues and TODO List:
unused spell 41967 3s. Server-side spell that applies 57989 after 3 seconds? To prevent insta death from giving mana?
https://wowgaming.altervista.org/aowow/?spell=41967
SUMMON_PROP_FLAG_SAVE_PET_AUTOCAST
cmangos/mangos-wotlk@ca466c3How 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.
Licence consent:
In the spirit of collaboration with other projects in the emulation scene, we encourage all new PRs to authorize sharing on GPLv2- based projects.
Further information, here: #19868