fix(Scripts/Zuldrak) Npc: Blightguard; Spell: Scourge Disguise and related things #21536
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.
Thanks to TrinityCore for the provided spawn locations!
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
Also this mobs should: have invisibility and remove Scourge Disguise aura from player on attack
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
.additem 38699 // Choker
.go xyz 6278.02 -1933.10 239.60 571
Use Choker
NPC around you should became friendly, except Blightguards.
Approach Blightguards, they should attack you and remove your Disguise aura.
.additem 38699 // Choker
.go xyz 6278.02 -1933.10 239.60 571
Use Choker
Wait 3-5 minutes. Now you should see that spell is going to end, and it will be actually removed.
.additem 38699 // Choker
.go xyz 6278.02 -1933.10 239.60 571
Use Choker
.quest add 12664 // dark horizon quest
.go creature id 28666 // Gorebag
Talk to NPC, take a ride, see that you have only 1 active aura of "Scourge Disguise" after ride is over.
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.