Quote Originally Posted by Rongway View Post
Procs do not interrupt combos, so you could, for example, do something like this:

Cascade (no proc) > Fountain (proc Fountainfall) > Cascade (proc Reverse Cascade) > Reverse Cascade > Fountainfall > Fountain (proc Fountainfall)

which in terms of buttons looks something like this:



Here's what that same sequence would look like with button consolidation (excuse the numbers):


Knowing the devs, I'd wager they think this looks confusing and consequently consciously chose not to consolidate these buttons. I'm especially inclined to believe this once you take into account Flourish, which instantly procs all flourishes. In the unconsolidated version, it's much easier to tell whether or not you have any procs that will be wasted because there's a clear difference between dimmed buttons and active dashed outlined butons. In the consolidated version, you have to exert more cognitive effort because there are never dimmed buttons. Is the second dashed outlined button a proc or just the base second step in the combo? It would take longer to learn how to screen for Flourish with that system.
And how would they transform into the four dance steps?

Dancer is already one of the jobs with the fewest buttons, and already consolidates four of it's skills into other buttons.