-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Kil'Jaeden Ability Timers #22130
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
base: master
Are you sure you want to change the base?
Kil'Jaeden Ability Timers #22130
Conversation
…instead of every 40 seconds.
…on to happen every 20 seconds, instead of every 40 seconds.
Sorry, I forgot to .gitignore this
If this proves correct, the ternary IF no longer serves a purpose in that statement |
I agree. I'll change that and test the fight another time to make sure everything looks okay. |
Testing the boss fight more and everything seems to be working well. He doesn't cast Fire Bloom so much toward the end of the fight, because he is busy with a channeled spell. But it does get cast consistently around every 20 seconds. Apologies for the 5 commits for the small change. |
Yes, the current skills of Kil'jaeden are quite weak. He is the easiest boss in the Sunwell because the timing intervals of some channeled abilities have not been taken into account. |
First Fire Bloom is happening too early in P3 and P4, it's ~37s after the phase start , it should be ~48s at least (sometimes even +60s) If Fire Bloom gets delayed the next one will be casted too early such as 14s , the shortest timer between 2 Fire Bloom i have seen in videos is 17s. Videos for reference: Video1 , Video2 , Video3 , Video4 , Video5 , Video6 , Video7 |
I am going off my DBM addon to see how the fight is going along with expectations. Phases 3-5 seem right on target. Phase 2, it appears I may be pushing his shield ability to not trigger when expected. Phase 1 seems normal. DBM still shows the flame ability as if it were a 40 second interval, but the original bug report provided evidence it should be 20 seconds. It's still loading in, but here's a video of the fight with the current script. I think everything is good. Although I don't think phase 5 ever happened? |
i think , you are changing the repeat timer with latest changes instead of the initial timer, it's why Fire Bloom "doesn't happen" in p5 as if it skips the first initial timer , it will have to wait 70s to repeat it? Also for the timers , keep in mind there is always a delay by ~28s at the start of P3,P4 and P5, (caused by Shadow Spike) |
I meant that, oddly enough, my fight doesn't seem to ever get to phase 5. At least according to the deadly boss mods announcements. Edit - it seems that phase 5 IS phase 4. It's just a naming scheme I didn't recognize. Phase 1 starts with the hands before the boss emerges, and phase 2 is when the boss begins the fight. |
In this video from retail's TBC classic, this player is hit with Fire Bloom during phase 3 at 3:37 and you can see it cast again at 4:00, and is a 23 second delay In this timestamp from same player is hit with Fire Bloom at 6:45 mark. Kil'jaeden casts firebloom around 7:08 after that. This is in phase 4 of 5, and is a 23 second delay Phase 5, for this specific group at least, I can only see firebloom being cast a single time. I have the same effect during my testing with my alteration of setting a "cooldown" of 70 seconds with my edit of the Fire Bloom timer. I tried to edit my timers to match this 23 second delay, but it resulted in him casting the fire bloom every 18ish seconds - which is too early. I'll try 25 to 27 and see how it works. Setting the timers to 20 (phase 2), 25 (phases 3/4), and 40 (phase 5) gets me a pretty consistent cast of Fire Bloom every 20 seconds for phase 2, 3, and 4, and every 50ish seconds for phase 5. I am not sure why the timer seems to have a negative affect for phase 3/4, but I think the way it works out ingame is pretty good. |
…or phases 2-4 and 50 second intervals for phase 5.
/* Phase names for reference | ||
PHASE_DECEIVERS = 1, | ||
PHASE_NORMAL = 2, | ||
PHASE_DARKNESS = 3, | ||
PHASE_ARMAGEDDON = 4, | ||
PHASE_SACRIFICE = 5, | ||
*/ |
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 comment block isn't necessary for the final PR, given that the phases are already enumerated elsewhere in the file.
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.
You're right. I'll take it out.
Changes Proposed:
This PR proposes changes to:
Issues Addressed:
chromiecraft/chromiecraft#8037
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.