
Originally Posted by
Kirsten_Rev
I suspect SE has targeted for jobs to have a rough number of actions available to them. They consolidate as necessary to make sure the number of actions don't grow beyond some upper bound they've got in mind (likely anchored primarily around the controller experience), but they also want to make sure the number doesn't drop too low, and is balanced with other jobs.
This make sense from a design perspective. It also makes sense from an experience perspective, as there is an inverse relationship between the pace of a game and how many actions can and should be available at any given time. FFXIV has a fairly long GCD as modern MMOs go, and its fights and rotations are heavily scripted; this means there needs to be a decent number of actions to keep the engagement and challenge up. It might be frustrating for someone who would prefer more, ah, 'streamlined' combat, but everyone has different feelings here. After all, for a lot of people, the sentence I emphasized above would have 'cannot' swapped to 'should not'. Imagine what a job like, say, RDM would change to, then? The melee single-target combo would be broken down to a single button. Theoretically Veraero / Verthunder could be swapped to a single button based on whatever element is lowest on the gauge. Certainly Jolt II and Impactful would be merged (IIRC this is shifting for Shadowbringers anyway). And of course, as the OP mentioned, Verflare and Verholy would swap in for Verthunder and Veraero, respectively, when available. For Stormblood, this would result in a job that already feels simplistic - 24 primary Job actions - being reduced to 18 primary job actions, with a primary combo consisting of four buttons. For some people, that would be great; for me, it would be coma-inducing.
All this to say, we all have our ideal 'comfort zone' in terms of the action count. Going too much above that is an issue, but so is going too far below it. SE has to maintain a rough middle ground for everyone, which means that their goal isn't to streamline as much as possible - it's to roughly align job action counts with a predetermined target that they consider optimal. That's likely the core reason why action consolidation of the type discussed in this thread isn't happening.