Does its word explain why one would conflate wholly different contexts?
Seriously, you'd find more relevance towards existing (real) jobs' PvE kits in a design decision from Blue Mage as evidence than in XIV's PvP. PvP has been a thing unto itself since Stormblood.
"There may be an odd quirk of coding by which it's actually harder to copy-over a past design for stacked actions for specific combos without also doing the extra work of removing the existing, separate actions" would actually be a more reasonable warning against consolidation than "It was included as a small part of PvP's sweeping changes towards simplification, so anything that uses it would doubtless face the same lack of options as PvE."
The latter treats a tool as having inherent motive and context; it doesn't. Combo consolidation would do for PvE only exactly what the precise buttonflows of having consolidated combos would do for PvE. It does not necessitate it's being a non-option. It does not necessitate sweeping changes towards simplification.
________________________
As for Gnashing Fang itself, I'd agree that we should regain the option to separate it, even if I can understand why SE didn't much feel it made sense for one job's equivalent of Goring Blade/Storm's Eye to take up three times as many unique keys as the others'.
A small note, though: Gnashing Fang has never been a combo as codified by the game any more than, say, Forked/Fleeting. It's only ever been a series of skills that provide 10s buffs which unlock others in that series. As such, one could already just key-swipe across them (WT->JS->GF) to queue the next among whichever of the trio was possible rather than ever needing to track one's step in that series or hit a particular button per that step.



Reply With Quote


