-
-
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/Zulaman) Multiple fixes to Jan'alai #21257
Conversation
fix spacing
Remove commented spawbombs test
clang-format
clang-format round 2
Fix formatting
Honestly still not quite happy with SpawnBombs(). Was going for something like a circle spreading from the center and that area being the potential for random bomb with the max circle being the arena and max time the 5 seconds... Maybe I'll keep poking at it but does certainly look more blizzlike then before. |
Jan'alai still stay in the middle until the bombs explodes. |
I see what you mean, I made another commit to make him start attacking 1s before boom |
I believe it should be 3s at least before the bombs explode (so L341 from 8s down to 6s?) but everything else seems to be working fine :) |
Watched the youtubes again... Agreed, made the commit for da boom |
|
Im tired lol |
|
||
FireWall(); | ||
SpawnBombs(); | ||
me->AddUnitState(UNIT_STATE_NOT_MOVE); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This includes UNIT_STATE_DIED
.
UNIT_STATE_NOT_MOVE = UNIT_STATE_ROOT | UNIT_STATE_STUNNED | UNIT_STATE_DIED | UNIT_STATE_DISTRACTED,
Also check if this is cleared in Reset as Reset() clears taskscheduler and the ClearUnitState
may never run
I see these are similar instructions as flamebreathing above but me->AttackStop();
could be missing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm yeah let me make sure, also probably better way to get him to stop moving. Let me check
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added the me->ClearUnitState(UNIT_STATE_NOT_MOVE); to Reset() and tested .die both without doing bombs and while in UNIT_STATE_NOT_MOVE. both seem to reset. Didn't test before adding the UNIT_STATE_NOT_MOVE to Reset() but assuming could be bug in future if I didn't.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tried stuff like me->StopMoving() but for whatever reason those other methods just wouldn't work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was this marked as resolved? This is a hack and won't be merged as is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, don't wan't to mess anything else up, I'll just close
Should be max threat not random
Ready for review |
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
SOURCE:
The changes have been validated through:
Tests Performed:
This PR has been:
How to Test the Changes:
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.