Quote Originally Posted by Raikai View Post
I feel that the problem right now is some jobs having redundant conditional buttons.

They seem to be looking into that in Endwalker, yeah, but I'm kinda puzzled why for example, Scholar's Summon Seraph button won't turn into Consolation, if the latter is only available when the Seraph is on the field?... Tracking charges doesn't even make sense since the Seraph's recast timer is 120s and each Consolation charge replenishes at 30s.

Machinist's Hypercharge could also turn into Heat Blast since, again, the latter is only available during the former.

Maybe there are more examples of those in other jobs too...
There are. On BLM alone there are arguably... 4. Fire IV and Blizzard IV can't be simultaneously used, and can only be used after Enochian, for which key there is no use after having initiated Enochian (at least until somehow failing to maintain it). Between the Ley Lines can only be used after Ley Lines has been set, and there are no further uses for the latter's key after its initial press.

And that's not even including the intentional button-inefficiency that are our "combos". On DRG there are only at most 4 GCD decisions to be made even in the most decision-flush moments: ST-Buff-DoT, ST-Direct, ST-Ranged, and AoE. Because of how combos work in general, though, even those choices will only be present once per combo cycle (outside of ST-Ranged, which is wholly frontloaded and modular).

The example has been given before, but there'd be no loss to actual decision making even if you were to have the damn thing auto-battle until given a command to switch to AoE combos, to throw a Piercing Talon, or to rush to repeat the last 5-step ST combo (for a grand total of 3 buttons for all possible viable decisions to be made, without one necessarily having to press a damn thing for raid content). That's not to say I want an auto-battling DRG; quite the opposite. I just find the current keyflow incredibly wasteful.