
Originally Posted by
Xenon_S
Reposting this in a few places in an attempt to get traction, maybe
Kaiten is not a button bloat issue in the keybinding sense
In the slides, the JP text uses the word "操作量”, which is more equivalent to action bloat, in the sense that it is an extra action to press before iaijutsus.
However, in this vein, Kaiten isn't an action bloat issue either, and removing kaiten does NOT alleviate this issue (which doesn't really exists in the first place imo)
In removing Kaiten, the kenki will just be spent on Shinten instead, which still takes up an oGCD slot, and is objectively less interesting.
Granted, I'm not saying pressing Kaiten is some 200 IQ move, but it is still an active decision to be made, whether to spam Shinten or conserve Kenki for Kaiten.
Which is funny because, going from 4.0 to 5.0, they added Tsubame Gaeshi and the gutted Hagakure to discourage Shinten spam, and now we are going back to it.
The only time Kaiten action bloat is a minor issue is when, during a 2min burst window, you are setting up Midare Setsugekka -> Kaeshi Setsugekka -> Sen GCD -> Higanbana -> Ogi Namikiri with 1 stack of meditation. In which after Higanbana you will reach 3 stack meditation, forcing a Shoha cast, and also having to Kaiten the Ogi Namikiri. Higanbana being a cast means you cannot double weave (without clipping) during that slot thus you have to introduce another GCD to weave the Kaiten, or modify the sequence of the skills.
This can be alleviated in so many ways that does not require the removal of Kaiten.
For example, letting mediation go up to 5 stacks (with Shoha being usable at 3) as to have some buffer zone. This even adds some more optimization depth as you can choose where to place your Shoha.
Or simply make it so that Ogi Namikiri does not require Kaiten, as we got the "sword twirling powerup" with Ikishoten already.
IMO, the decision to remove Kaiten is a bad solution to an irrelevant problem, and this isn't even an agrument regarding the aesthetics and class fantasy of the skill.
For all the transparency and communication the devs do, job balancing isn't part of them.