1.) Gyoten for a long time has not been a potency loss since they have been matching potency-per-gauge (PPG) with Shinten. Gyoten also still costs 10 kenki, all they did was reduce the CD from 10s to 5s - i.e. made it more available
2.) Onslaught was a situational damage loss and on occasion even a damage gain vs non-IR Fell Cleave, the potency-per-gauge difference I did the math a long time ago, feel free to check it.
Basically it boils down to double-digit potency differences over the course of a fight, which in comparison to potency/minute or potency/10min is actually a tiny difference.
I wouldn't go for a copy of the outlier, as you respond below you know I have more than one way to go about things, but I'm just pointing out that your argument of "increasing availability of gap closers/mobility tools will likely lead to a change to encounter design where all jobs need to be given equivalents or similar" (that's how I understood it) doesn't hold a lot of water because we already *have* cases of precedence where one job or another has a big advantage in mobility/range over others, yet encounter design and by proxy job design isn't being flipped on its head because of it.
WAR's current Onslaught is also more or less just 2 x Onslaught per minute in recharges, giving a bit of leeway before the 2min burst where you want to throw in the odd Onslaught to prevent overcap - it's not that much more mobile, but I'm not gonna die on this hill tbh.
Nerfing capacity and neutering jobs that are outliers is exactly why we have the flavourless job design that we have evolved into now ever since the Shadowbringers design flip. Having 1-3 jobs better at dashes while others be better at ranged attacks (or mobile casting in terms of Casters/Healers) isn't something that should be neutered, but instead embraced.
You're incorrect on that one - I did give example referencing the PvP DRK equivalent of Plunge. You literally responded to it.
That said, my suggestion to have both of them comes from trying to appease both the side that "dashes shouldn't do damage, they should be for utility", hence keeping Shadowstride for a pure mobility tool but also the side that wants Plunge back, which is a satisfying button visually but could be made more interesting. The exact numbers to tweak and settling for how much mobility DRK is supposed to have is a completely different ballgame that I haven't explored - all I am stating is that we should NOT have current Shadowstride + 6.5 Plunge at the exact same time.




Reply With Quote

