-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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/Naxxramas): Razuvious' Death Knight Understudy RP #18918
fix(Scripts/Naxxramas): Razuvious' Death Knight Understudy RP #18918
Conversation
Pausing his patrol to walk up to an add is broken / incomplete and resuming pathing is broken. I can stop him with |
763a1f0
to
8ac863a
Compare
vid with sped up timer: https://youtu.be/lYJGwxtcm78 currently relies on loading path after doing RP. This moves Razu back to wp 0 of his path. Instead, he should continue where he left off |
Closing for now. Will PR Understudy animation separately At this time, MotionMaster does not allow for this type of movement interaction:
from acore discord support https://discord.com/channels/217589275766685707/1249809406229745774 |
Changes Proposed:
This PR proposes changes to:
Adds Out of Combat RP to Razuvious and his Death Knight Understudies.
Issues Addressed:
SOURCE:
The changes have been validated through:
razu_rp.mp4
retail VOD: full 18 min recording https://www.youtube.com/watch?v=O7NDubkjbWg
Tests Performed:
This PR has been:
How to Test the Changes:
.go c 128312
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.