All in all the idea behind Enochian is okay, but there needs to be some pro/con balance in the implementation.
Right now the 2 biggest problems are that if either Enochian or AF/UI drop during your F4/B4 cast, you lose the cast. And that the rotation basically demands that you skim the very edge of the timers in order to output enough dps to warrant using the new spells... Versus just taking the 5% bonus and basically using the old rotation, replacing B1 w/ B4 as filler in the UI phase.
The source of this issue is that F4/B4 in no way help you maintain the buffs required to keep them going. This is understandable as SE wants us to continue using F1 during the Enochian rotation. The issue is that you need to fit 2 F4's and an F1 into 10 seconds. 2*3+2.5 = 8.5s, that seems fine in theory. Add in the 0.5s initial latency after switching into AF3 before you can cast F4, we now have 9s. Add in 100ms latency between casts and we have 9.3s out of a 10s timer... Watch any BLM executing the "perfect" Enochian rotation and you'll see how AF3 ends up with 0-1 seconds when it is refreshed. IE its being refreshed as it falls off.
There is a similar issue with B4 if you start trying to add Thunder into the UI phase.
The simplest solution is to add something which helps perpetuate AF/UI and Enochian across various abilities.
As Yoshida hinted at in the Live Letter, making the Thunder spells add ~3s to Enochian would allow us to readily incorporate them into the rotation.
Subsequently we could add a secondary effect to F4 which makes the next F1 instant cast with the original mana cost. This means you could throw as many as 3 F4's in a row, then instant cast F1 to refresh the AF3 timer... However you'd still be limited to 4 F4's per cycle due to mana constraints, so there is no dps increase under ideal conditions, however you can refresh AF3 much more readily, AND you are not as punished by movement since every F4 gives you an instant F1.


Reply With Quote





