
Originally Posted by
Hazusu
My point is that the rotation was so much simpler back then that you didn't need to stare at the buffs and debuffs with a reasonable amount of time on the job. Remembering to alternate your 1s and 2s was very easy, and the most taxing part on your mental stack was remembering to fit demolish after two True Strikes, but even that was a normal ask. For comparison, the old DRG filler rotation was 10 GCDs long; MNK's was 12 . At even a somewhat moderate level of playing MNK, you likely did not need to stare at your buffs. ...
The problem is you are thinking about how log it takes to get back to the start and treating it like a rotation, however, since Monk doesn't follow the rotation like normal jobs, it isn't a fair comparison.
Monk only has 1 'combo' (using that term loosely here), and that is Opo-Opo > Raptor > Coeurl. Each of these has 2 attacks which you use based on what buffs you have. This gives you 8 possible permutations for possible combos, you just need to use the right ones.
However, on the topic of '36 GCD combo strings', you wouldn't even get a chance to go through the whole thing anyway. 36 GCDs, at 2 seconds per GCD, is 72 seconds, which takes you through PB phases, which is going to misalign you from the '36 GCD string' you want to follow anyway.
Again, this is just you thinking about the job wrong. Rather than following a set GCD pattern, you need to adjust on the fly, think ahead, just like old Monk. Which also ties in with Dragoon, I don't think you memorise the full 10 GCD rotation, you, in your head, think Chaotic Spring combo, Heaven's Thrust combo and muscle memory takes it from there.
As an aside, here is the full 36 GCDs in number form, 1 is buff, 2 is spend:
111
222
122
212
121
222
112
222
121
212
122
222
I have similarly highlighted the differentGCD strings that appear more than once. In total, of the 8 possible permutations, only 6 different ones are actually used, missing 211 and 221. This doesn't mean they will never be used as the PB windows can scramble this as I have previously mentioned, which again highlights the importance of adapting to the situation rather than just following a static GCD loop.