A job that deals has a third the throughput of the second-worst job could be said to have "no" throughput. In that same sense, Enochian, as a button, was "not used" (with any frequency sufficient to warrant a button of its own) except by poorer players.
Automatic, if the button is otherwise to be spent on an only once-per-instance button, is preferable. Even combat pots offered more nuanced and meaningful use.
Out of daily posts, sorry.
Simply this:
- You've misconstrued what was at its most extreme an obvious case of mild exaggeration. (A skill used once per instance is one that goes practically unused. "Not needing to be reapplied" was also explicitly mentioned previously -- multiple times, iirc.)
- Turning Enochian into a trait was a good thing, and fits far better principles of button design that did having it as a separate action. (I'd even go so far as to say it was only ever made an action, instead of a trait, to better hype job trailers -- since the average player, especially back then, was shortsighted enough to think getting 5 new "actions" inherently more exciting than getting 5 new "actions or traits".)
Due to tanks having reason, at least in 8-man content, to switch their stance off, there is at least some small point in having a tank stance button. There was none, however, for Enochian. The only punishment added to someone losing Enochian except in under 27 seconds from having used it before was that it'd require a half-second of weave time due to its animation.
Enochian's punishment, moreover, was ill-aimed. It could only worsen the experience for the few players we least wanted to constrain while existing as a non-mechanic for everyone else. Imagine a fee, for instance, for making little money per day; though applied to other systems of the game, such would make about as much sense as Enochian having a cooldown, requiring weave-space, and needing its own button. There wasn't a single thing good about it outside of button fetishism.
You seem to be conflating my position with other camps. I do like pressing buttons at the rhythms, densities, and ranges enjoyable to me, but that range (or total button count) is only a part of the equation, and my preference falls between certain counts rather than simply seeing more buttons as better (especially if the same affordances could be managed with fewer keys).And I thought you like pressing buttons