So yesterday, ever observant, Shakugan, noticed that there appeared to be some bizarre behavior with Whirling Dragon Punch. Now, I know what you’re saying, “Wow, Babs, shit being broken for Windwalker… how original?”. However, I’m here to tell you that this new bug is a good bug and one that should be embraced. My name is Babylonius and Welcome to my TED Talk.
What’s going on?
This is the situation that started it all last night. Now, nothing may appear amiss, until you realize that Whirling Dragon Punch did 21 hits of damage but had “-” casts (that means zero). Well obviously this is a little weird, so further investigation was done and in his infinite wisdom, Shakugan put together a video to illustrate it.
If you look closely, you can see that the CombatLog (left) shows damage events from Whirling Dragon Punch, but if you watch his actionbars, he never actually presses it. This is indeed very weird. This was further confirmed by everyone’s favorite person, Mik, by verifying that this is the case on PTR like Shakugan showed above, by finding Whirling Dragon Punch damage events without ever pressing the actual Whirling Dragon Punch button:
A little more testing and it appears that these damage events are getting triggered any time the Whirling Dragon Punch buff falls off. This is the same buff that was put in place to (unsuccessfully) make sure that Whirling Dragon Punch would be usable when Fists of Fury and Rising Sun Kick were on cooldown. This means that if Fists of Fury and Rising Sun Kick are both on cooldown then the instant one of them comes off CD, there will be Whirling Dragon Punch damage events. If you use that ability, the Whirling Dragon Punch buff will return, and disappear the next time Rising Sun Kick or Fists of Fury comes off CD. You can, theoretically, get these damage events every time Rising Sun Kick or Fists of Fury come off cooldown, as long as the other one is still on cooldown. Its not something that would be easy, or really possible, to abuse, but its a fun little chunk of damage.
It is possible that it has something to do with this new line that was added to Whirling Dragon Punch‘s spell data at some point, which is most likely just them trying to find a way to fix it, but we don’t know for sure;
Why is this good?
So this was mentioned to me last night before I fell asleep, and upon waking up this morning, I actually felt really good about what its doing for a variety of reasons. So here is my Pro and Con list:
- You cannot be in a situation where Whirling Dragon Punch should be castable but isn’t (bug fix)
- You cannot abuse the end of Storm, Earth, and Fire to try and eek out more Whirling Dragon Punch damage (bug fix)
- You’re not in a situation where Blackout Kick not reducing Whirling Dragon Punch makes things line up all wonky.
- You can’t get killed by using Whirling Dragon Punch at the wrong time and getting knocked up.
- Makes it very easy to make baseline and replace with something else
- Adds some skill element to always keeping them desynced
- Adds consistent sustained AOE and ST pressure
- Keeps Rising Sun Kick relevant during AOE
- One less button to press
- Takes away the “skill shot” of using it at the end of Storm, Earth, and Fire
- Would make an active talent a passive without further changes
- Removes burst potential
- Cannot avoid knockbacks
- Storm, Earth, and Fire reduces its damage… because of course it does
Personally, the Pros outweigh the Cons, but I know that I am not always in the majority for how I like Windwalker to play, so for me the loss of one active button isn’t a bad thing. It does also open up the potential for moving Whirling Dragon Punch to baseline and opening up that talent slot. Obviously the continued barrier of Storm, Earth, and Fire not working with it the right way is annoying, but that’s a problem they’ve solved before just by making it so they do copy it or it doesn’t get reduced.
I think having a further benefit to keeping things on cooldown is a great thing. I think having a reason to use Rising Sun Kick consistently inside AOE is a great thing. I think the bugs that now become irrelevant is a great thing. I think giving Windwalkers more consistent AOE pressure is a good thing. However, the more I thought about all this, the more clearly I saw the perfect way that this should work.
What would be perfect?
So my ideal world has two options; (1) Whirling Dragon Punch keeps this functionality and replaces Rushing Jade Wind in its talent row, OR (2) Rushing Jade Wind gains this functionality as a passive and Whirling Dragon Punch is no more.
I think this the best case scenario because right now Rushing Jade Wind is an awful spell that will never be used. It is also currently the only “active” ability in its row, and it feels horrible to use. By making Rushing Jade Wind activate any time Rising Sun Kick and Fists of Fury are on CD for the duration that they’re on CD, or just as one time proc whenever both are on CD, it makes it a passive ability that comes from your active play. It would then be paired with Hit Combo which is the definition of a passive that adds nothing to your kit, and Dance of Chi-Ji which is a passive proc that has an active way to use it. I think this gives a really good discrepancy in how you want to do your damage, and since they all would affect single target and AOE, they would all be reasonably easy to balance between each other.
By moving Whirling Dragon Punch in this form down one row lower or replacing the awful Rushing Jade Wind with this functionality, it would free up a talent slot for something like TEB or Strike of the Windlord in the top row. This could also be made the way that you trigger Strike of the Windlord and put that in the spot where Rushing Jade Wind is so that you have one single target proc, one passive, and one AOE proc in the same row. There are a dozen ways to utilize this, but the big point is that this passive function actually feels like a really great fit to the Windwalker martial arts and wind theme. It something that would reward good play of keeping things on cooldowns, without being very punishing for mistakes.
Honestly, I’d be super happy if it was a baseline function of the spec, although I will admit that I could just be looking for the sweet release from any of these bugs. Is this Stockholm syndrome?