Please stop removing Damage Over Time effects from every job, add more complexity

[Shurrikhan]

When you try and bring everything together and take into account every detail, it isn't a simple question to ask. However, since the initial comment was just, which one has more positionals, then all that matters is, is this GCD a positional or not, forgoing any deeper questions that might arise by digging deeper.

Fair enough. It just felt like a question best taken in spirit than by the letter. Else you end up with an answer that's equally useless, such as in noting that BLM has the least average raw potency of any job (because raw potency doesn't factor in Astral Fire's whopping 80% damage bonus).

Anything that a player tries to highlight as 'rotational complexity' really isn't. This game is completely scripted down to the GCD. The challenge is never the execution, because MMOs hands down have the lowest mechanical skill ceiling of any game genre outside of turn-based strategy games.

Are we really making the case here that there's zero increase in execution complexity in going from, say, a WHM's or DNC's dummy rotation to a NIN's?

The challenge is the puzzle that you have to solve on each new fight on the optimal sequence of button presses and positioning. And that's where the real fun is.

But since Shadowbringers, only some 2 to 5 jobs even make alterations to their "sequences of button-presses" based on the given fight. Positioning, sure, but that's largely it. And if the difference between having to make fight-specific alterations or not isn't "complexity" anyways... then what puzzle is there?

If there is an actual difference in how long it takes to get that sequence down and/or whether one actually "solves the puzzle" to varies that sequence with different fights, that is what most people would call "complexity." Does that make particular job here all that complex? In any sort of absolute terms, no, but there are certainly differences.

And looking up which rotation to use for each fight at a given GCD probably still isn't going to be often failed or made a significant bottleneck... as just actually still doing that rotation perfectly while everything else is going off. The (difficulty of) execution does make a difference.