SAM buffs warranted? Genuine question

[Taranok]

Dunno why we're buffing jobs based on an ultimate that's now technically not "on patch" anymore.

It wasn't just bad in ultimates. Samurai was being hammered in P5-8S as well. The class does not do well with frequent boss jumping.

[Shurrikhan]

It wasn't just bad in ultimates. Samurai was being hammered in P5-8S as well. The class does not do well with frequent boss jumping.

That feels like more of a reason to have Meditate refresh Haste/Damage buffs and to instead reduce the cost of one's next Shoha by up to 3 stacks (as opposed to granting 3 stacks, so that it doesn't waste whatever stacks one enters the jump with), and to faintly siphon combo opener/bridge ppgcd towards oGCDs / CDs instead, rather than just applying flat potency buffs.

[Taranok]

That feels like more of a reason to have Meditate refresh Haste/Damage buffs and to instead reduce the cost of one's next Shoha by up to 3 stacks (as opposed to granting 3 stacks, so that it doesn't waste whatever stacks one enters the jump with), and to faintly siphon combo opener/bridge ppgcd towards oGCDs / CDs instead, rather than just applying flat potency buffs.

My personal philosophy is that when you start adding mechanics to extend/maintain other mechanics of the class, you've fundamentally designed the game in such a way as to make that original mechanic at odds with the game itself, and should consider removing those original mechanics instead of adding code to maintain them.

Examples of this include Ninja's Huton/Huraijin/Armor Crush, Black Mage's Astral Fire/Umbral Ice/Transpose/Umbral Soul, Samurai's Fugetsu/Fuka/Meikyo Shisui, Bard's DoTs and trap jaws. Dragoon used to have this with eyes and BotD before they finally nipped it in the bud. Monk still has it and it causes some problems with Perfect Balance and Disciplined Fist. Basically, at a certain point, the original mechanic starts to lose its meaning and really grinds on the class as a whole. A lot of players want to maintain these mechanics, and it's understandable why, but it's also important to realize when it's just detracting from the experience and taking too many resources to maintain, especially button slots.

[Shurrikhan]

My personal philosophy is that when you start adding mechanics to extend/maintain other mechanics of the class, you've fundamentally designed the game in such a way as to make that original mechanic at odds with the game itself, and should consider removing those original mechanics instead of adding code to maintain them.

Let's start with the extreme of that more general point, since I don't think the example we were working from before (Meditate) at all meets that description of a self-conflicting mechanic. (If anything, it was the obvious oversights in the later-added Meditation Stacks from Iaijutsu casts that are/have been the problem.)

If you strip away a job's compensatory tools like Meditate/Meditation/Soulsow, designed to narrow the gaps between ideal and non-ideal encounters, you're not just arriving at the same capacities by different means, but instead arriving at altogether different capacities. In that situation, either fight design must be constrained as to prevent advantage from the one type of job over the other (as per further homogeneity of encounters), or you essentially halve the competitive job options available to each fight (reduced diversity in flavors/perspectives per encounter).

Fight has significant downtime? SAM (no Meditate, insignificant CD burst), RPR (no Soulsow), and BLM (no Xeno) can screw off. Fight has no virtually downtime? Drop NIN, SMN, DRK, etc.

Examples of this include Ninja's Huton/Huraijin/Armor Crush, Black Mage's Astral Fire/Umbral Ice/Transpose/Umbral Soul, Samurai's Fugetsu/Fuka/Meikyo Shisui, Bard's DoTs and trap jaws. Dragoon used to have this with eyes and BotD before they finally nipped it in the bud. Monk still has it and it causes some problems with Perfect Balance and Disciplined Fist. Basically, at a certain point, the original mechanic starts to lose its meaning and really grinds on the class as a whole. A lot of players want to maintain these mechanics, and it's understandable why, but it's also important to realize when it's just detracting from the experience and taking too many resources to maintain, especially button slots.

The examples are a mixed bunch to me. I guess, to put it simply, I want each button added to have an outsized impact, and to ultimately offer up more choices and more/deeper considerations than it replaces; else, it's wasteful.

For that reason, I'd agree, for instance, that Huton stopped making sense the moment they introduced Armor Crush and, above all, the Hide resets... while Huraijin seems like a meta-commentary joke. I'd have been happy to just see Huton remain as it was in ARR but with a bit more flexibility on the Suiton timing (such as via a second mudra charge) as to actually offer the choice between an early or late reapplication. Removing Huton outright, on the other hand, I'd only be okay with if we got a similar means of deciding between both timings and burst vs. sustain.

Black Mage's AF/UI was totally fine right up until Umbral Soul. AF/UI's duration now feels a bit long to me relative to the current F4 cast times, and I miss the additional options permitted by ARR's doubled quick-cast (could queue a second fire spell to benefit from UI's haste), but it's otherwise fine. It just needs to see Umbral Soul consolidated... or replaced by a [conditional / secondary-CD-gated] Transpose buff instead, as not to make the other (and more fluid/interesting/responsive) tool largely redundant. I especially don't care for the Umbral Soul spam during extended downtime, and would happily have Enochian/Glossia progress instead just freeze while out of AF/UI and forgo the spam, but that doesn't require axing the whole AF/UI mechanic.

Bard's DoTs, likewise, were fine until Iron Jaws was introduced as something always available (as compared to, say, a dynamic ability with multiple charges, available from a single song, with the songs themselves being far more flexibly timed) and any palpable/gameplay-affecting benefits of multi-DoTing were removed.

Dragoon's original incarnation of BotD wasn't a problem so much as just... not immediately obvious. Heck, it was the most nuance we've seen from that mechanic, even if closely rivaled by back-to-back LotDs for exploiting cleave in certain fights. I'm fine with it as is, too, but I don't see how its former state would be considered an "issue".

There is zero issue between Perfect Balance and Disciplined Fist. Each makes the other more rewarding by having PB set up rotational strings in which DF is better optimized. If anything, the problem with Disciplined Fist is simply that True Strike's bonus over Twin Snakes is so pitiful that one loses former rotational choice. Simply siphon over 20 potency each from Twin Snakes and Dragon Kick to True Strike, though, and that issue would be fixed; we'd have our old rotational flexibility back.

Skills that I do think are problematic, though, would be things that exist just to make a given gauge seem more prominent, without actually producing any greater depth or nuance, such as Barrel Stabilizer, Amplifier, etc. Ikishoten now probably falls into that category, too, though it didn't even just an expansion ago (when it conflicted with banking for the old 50-gauge Guren/Senei and was available frequently enough to make one more mindful of one's Kenki, much like Stormblood Hagakure).

[Taranok]

Let's start with the extreme of that more general point, since I don't think the example we were working from before (Meditate) at all meets that description of a self-conflicting mechanic. (If anything, it was the obvious oversights in the later-added Meditation Stacks from Iaijutsu casts that are/have been the problem.)

If you strip away a job's compensatory tools like Meditate/Meditation/Soulsow, designed to narrow the gaps between ideal and non-ideal encounters, you're not just arriving at the same capacities by different means, but instead arriving at altogether different capacities. In that situation, either fight design must be constrained as to prevent advantage from the one type of job over the other (as per further homogeneity of encounters), or you essentially halve the competitive job options available to each fight (reduced diversity in flavors/perspectives per encounter).

So, first of all, Soulsow is legitimately a garbage ability. This is the third time this garbage piece of crap has been added to the game. The first time was Chakra in Heavensward. Second time was Shoha in ShB, third time is Soulsow. What makes it garbage? You only can use it during downtime, meaning it is a button that exists on your bar that, in any non-ultimate fight, gives you a best case and staggering three uses of the ability. Effectively and often giving it a 5+ minute implied cooldown on that type of fight. A fight with 0 downtime gives you one use and it's gone. To even bring up this garbage bin excuse of an ability grossly misunderstands the point I was making as well as the design of that ability.

Second of all, I'm not even talking about downtime options here, but rather what mechanics should be afforded a downtime option. That is, I don't care about meditate giving you rage bar or stacks towards shoha. But rather meditate being used to extend your personal buffs, as you directly posited. Downtime building is fine. Classes like BLM (assuming it's not a cutscene) can generate xenoglossy, while classes like SAM can meditate. That's fine, it's not even part of my discussion or thought. Though if we're being critical for the sake of it, for the same reason that Soulsow being effectively a 5+ minute cooldown, buttons like meditate probably shouldn't need to exist anyways because it's an entire button slot when some classes literally don't have to do anything to get the same benefit. This isn't about job disparity, it's about efficient use of button space to either declutter classes with bar bloat problem.

Fight has significant downtime? SAM (no Meditate, insignificant CD burst), RPR (no Soulsow), and BLM (no Xeno) can screw off. Fight has no virtually downtime? Drop NIN, SMN, DRK, etc.


The examples are a mixed bunch to me. I guess, to put it simply, I want each button added to have an outsized impact, and to ultimately offer up more choices and more/deeper considerations than it replaces; else, it's wasteful.

Yes, exactly, every button should be important. When you can go entire fights without using a button, or barely using it, that button better slay god or the devs should consider outright removing it. A perfect example is something like Huraijin or Soulsow, which may as well not exist if a fight has no downtime. A weird example would be Transpose and Umbral Soul. Though both can be used in incredibly gimmicky rotations by exploiting BLM's generally awful structuring, but that's another topic unto itself.

For that reason, I'd agree, for instance, that Huton stopped making sense the moment they introduced Armor Crush and, above all, the Hide resets... while Huraijin seems like a meta-commentary joke. I'd have been happy to just see Huton remain as it was in ARR but with a bit more flexibility on the Suiton timing (such as via a second mudra charge) as to actually offer the choice between an early or late reapplication. Removing Huton outright, on the other hand, I'd only be okay with if we got a similar means of deciding between both timings and burst vs. sustain.

Personally, I think Heavensward ninja was the best Ninja ever was, and everything after it is a step backwards. Too much business, not enough substance. It had 1 major flaw (ping dependency,) but otherwise was smooth. But as the class has definitely moved away, it slowly just destroyed the original thing. However, on that second point, let's look at it.

What might we do with Huton? First, we should look at the obvious. Huton represents the only combo in the entire game that is never used in combat, that isn't also fuma shuriken itself, which is kind of used on TCJ anyways. There are only 7 possible mudra combos at the moment. X, X-1, X-2, X-3, X-X-1, X-X-2, X-X-3. The devs went out of their way to make sure the garbage bin option, X-3, was used in Shadowbringers for multi-shuriken shenanigans. So the most obvious thing would be to look at the class and try to make the X-X-1 combo used somewhere else. So, what might we do, where might we do it? If we really want to take a step back in time, we can look at ARR's ninja design. Your 1-2-3 melee combo had no positionals. Cool, let's make Ninja a positionless class. Not because we need to, but to add some real choice with ninjas. We don't need to, it could also just be a 24/7 backstab simulator as well. We can get rid of armor crush, as well, since under this supposition, we're looking at a ninja that just permanently has huton active, like monk's Greased Lightning.

From this framework, what might we do? Well, the most obvious location is looking at the skill TCJ itself. Meisui exists to give TCJ's suiton a use. To spend it. So if we no longer make TCJ give you a suiton, we can remove Meisui, a button that may as well press itself after you cast TCJ. So what is this button doing? We could do a 4-step mudra combo. It was teased all the way back in stormblood. At level 72 or so, give a trait to upgrade TCJ, and make it so that your 3-2-1 combo makes your next mudra used do an empowered effect. 3-2-1-3 would be some slaying god tier single target attack, 3-2-1-2 would be a doton that looks like an exploding volcano or something. 3-2-1-1 gives you mega-bunny, which is a DPS loss disaster recovery option where your bunny whacks the boss, in case you mess up, to make sure it's not a critical damage loss. If the fourth step did 2000 potency, the megabunny would do 1500.

By doing this, you can potentially reclaim 3 bar spaces (meisui, armor crush, huraijin,) 1 dead mudra space (huton->empowered four step mudras,) and expand on the theme of the class in an exciting way (4 step mudras.) This is more what I'm getting at. I'm not saying this needs to be done. I'm not even strictly saying it should be done exactly like this. But rather that there's a lot of real estate tied up in bad abilities to facilitate this design that literally dates back to ARR.

Black Mage's AF/UI was totally fine right up until Umbral Soul. AF/UI's duration now feels a bit long to me relative to the current F4 cast times, and I miss the additional options permitted by ARR's doubled quick-cast (could queue a second fire spell to benefit from UI's haste), but it's otherwise fine. It just needs to see Umbral Soul consolidated... or replaced by a [conditional / secondary-CD-gated] Transpose buff instead, as not to make the other (and more fluid/interesting/responsive) tool largely redundant. I especially don't care for the Umbral Soul spam during extended downtime, and would happily have Enochian/Glossia progress instead just freeze while out of AF/UI and forgo the spam, but that doesn't require axing the whole AF/UI mechanic.

So, AF/UI was never truly a fine mechanic. It's a very interesting study in bad design that has just been stretched and mutated into oblivion. The class was designed around a concept. Press X button, it stacks a thing, you do more damage. You run out of mana, press Y button, it rapidly regenerates mana at the cost of per-second damage during that moment. It was always designed this way. Transpose was a mostly dead skill used to recover mana after a fight ended or if a boss jumped, because you were forced to lose AF/UI timers during this downtime. It's a tale as old as time within ARR job design.

The difference is, for AF/UI, the devs decided to add fire 4 in heavensward. AF/UI was turned into a structuring mechanic off of a mechanic that was designed to drop and designed to basically have permanent uptime during a boss fight. The class was originally designed without AF/UI structuring the mechanic, and it was shoehorned into the class as a structuring mechanic. If we deep dive the mechanic itself, there are a ton of abilities that this weird pseudo-structure requires to maintain itself. Fire 1, used about once every 30-40 seconds, to refresh the timers (now done with paradox.) Fire 3, used for procs, which are also a core class mechanic that is about as vestigial as a dog's dewclaw by this point in the class design, but is used once or twice every 30-40 seconds. Blizzard 3, which is used once every 30-40 seconds. Transpose, to get back into mana generation, and umbral soul, to maintain stacks during downtime. This is specifically ignoring non-standard rotations. All of those abilities are required to maintain the timers. F3, B3, F1, B1(lul,) Transpose, Umbral Soul. All of those abilities are used, in a standard rotation without procs for fire 3, exactly once every 30-40 seconds, if not less than even that. This is before factoring in B4 (once every 30-40s), Thunder 3 (once-ish every 30-40 seconds, once every 30 is ideal,) and a whole host of other abilities on the class that are basically: "Use once every 30 seconds." Now, given the class is mostly fire 4 spam, some of these use once every 30s are whatever and add nice texture to what would be a boring class. But when the class literally has as many buttons as Samurai, there is legitimately an argument something is wrong here.

So, considering that AF/UI represents a massive amount of BLM's skill floor, the mechanic was shoehorned in as a structural mechanic, and it eats up so many buttons just for the maintenance of the ability, it perfectly encapsulates the problem I'm trying to underscore here. An old mechanic dating back 5 years (10 in the case of BLM,) that is eating up a ton of bar space and bespoke resources. At a certain point, you need to look at the class design and think: Why the hell is this mechanic here?

Bard's DoTs, likewise, were fine until Iron Jaws was introduced as something always available (as compared to, say, a dynamic ability with multiple charges, available from a single song, with the songs themselves being far more flexibly timed) and any palpable/gameplay-affecting benefits of multi-DoTing were removed.

Honestly, Bard's DoTs have never been fine. Or rather, more precisely, DoTs are a bad game mechanic outright. To expound on this particular point, what is a DoT? DoTs are a fixed amount of damage with less crit variance that take a long time to do their damage. So, what makes a DoT interesting? By itself, nothing. It is boring and bad damage. It can act to shake up an otherwise stale rotation, but that is about all it actually does. A DoT ticking for damage isn't exciting. There's rarely animations for ticks. You almost never see the damage yourself beyond the initial and sometimes awesome animation (Scourge, my beloved!) Aside from that, the DoT itself is boring. Unless you're world of warcraft. In WoW, you can extend DoTs. DoTs can tick faster with more haste. You can use buttons to cause DoTs to tick twice as often, or to globally extend DoTs much like Summoner's old Contagion. When the class is less tied to a burst meta, you can have options like this. WoW also has animations for DoTs I think, and can make the act of watching DoTs tick interesting.

Unfortunately, FFXIV has none of these, so DoTs are just delayed damage. The best-designed DoTs are Warrior's Storm's Eye and Reaper's Of Death. And I'm only tolerant of WAR because the class has nothing otherwise, whereas Reaper's could be removed and the class wouldn't lose anything meaningful.

It's 3 buttons for a class that is primarily designed around RNG mechanics. It stands out as just a weird choice. It was fine in ARR and even HW when Bard was a vastly simpler class, but modern Bard where it takes 45 seconds for a mere combined 750 potency, of which you will probably clip 5 seconds or 2 ticks of it without top tier play, it strikes as a largely orphaned mechanic at this point.

Dragoon's original incarnation of BotD wasn't a problem so much as just... not immediately obvious. Heck, it was the most nuance we've seen from that mechanic, even if closely rivaled by back-to-back LotDs for exploiting cleave in certain fights. I'm fine with it as is, too, but I don't see how its former state would be considered an "issue".

BotD is more one of those things where in Stormblood, you could, and did, lose stacks due to boss downtime. They had to make mechanics to extend it. Also it was nuanced even in Stormblood, where you had to reapply BotD before using LotD as the timer was directly tied to how much time you had left before bursting.

There is zero issue between Perfect Balance and Disciplined Fist. Each makes the other more rewarding by having PB set up rotational strings in which DF is better optimized. If anything, the problem with Disciplined Fist is simply that True Strike's bonus over Twin Snakes is so pitiful that one loses former rotational choice. Simply siphon over 20 potency each from Twin Snakes and Dragon Kick to True Strike, though, and that issue would be fixed; we'd have our old rotational flexibility back.

If you follow the 'natural,' rotation, that is you use the class and push buttons on cooldown without saving things, ideally in the highest to lowest potency order, then if you try using perfect balance on a purple combo after you did a bootshine-true strike-anything, you will go into perfect balance, and during your burst, Disciplined Fist will fall off before you can fire off your purple combo for elixir field. We can argue whether this is a good or a bad thing, but considering it is a skill floor issue, and not a skill ceiling one, it shouldn't behave this way. Considering the devs have often smoothed this out for most classes, it definitely is a problem.

Skills that I do think are problematic, though, would be things that exist just to make a given gauge seem more prominent, without actually producing any greater depth or nuance, such as Barrel Stabilizer, Amplifier, etc. Ikishoten now probably falls into that category, too, though it didn't even just an expansion ago (when it conflicted with banking for the old 50-gauge Guren/Senei and was available frequently enough to make one more mindful of one's Kenki, much like Stormblood Hagakure).

So, on the topic of abilities like that, I look at it another way. If you use X oGCD, and immediately follow up with Y oGCD, there's a problem. I'll use machinist for my example.

You want to Barrel Stabilizer, and then wildfire, and then hypercharge. It's not strictly always this exact order due to heat overcapping and people thinking 5 heat is a problem, but it's there. That's 3 buttons, 2 of which are dedicated 2m burst on top of yet-more 2m burst (Queen, mostly,) and is a very odd choice. Wildfire is just: "Better hypercharge." Literally. That's all it is. So if we take Wildfire, and just automatically launch you into overcharge, it's already better as is. If we take Barrel Stabilizer, and use it to upgrade Wildfire by, say, changing Heat Blast into a different ability, we can combine 2 buttons into 1 and delete another oGCD from the rotation by skipping the middle man. We can even ignore giving heat because Wildfire just straight up can put you into hypercharge.

For SAM, I'd take Guren and Senei, upgrade Guren into Senei but make them both hybrid ST/AoE skills. Then take Ikishoten, upgrade it into Guren, upgrade it into Senei, and just reduce the kenki it gives you by 25 due to using an empowered attack. I would then take that combined mess of 3 buttons and have it, when used, it turns into ogi namakure. By doing this, you delete exactly 1 oGCD from your 2m burst for literally the same damage and 3 less buttons bloating your bars, while also dropping the skill floor and, strangely enough, raising the skill ceiling, because you can actually store more kenki going into your 2m burst, adding some interesting, if not terribly important, burst potential to your 2m cycle. It's not a lot of extra damage, but anyone who truly wants to maximize the class would appreciate going into 2m burst with 60-75 kenki and being able to blast just that little bit harder. Whereas people like me can spend down and only miss party buffs for about a combined 750 potency of potentially stored damage.

I digress. There's a lot to digest here, so it takes a lot of time to go over.

[Shurrikhan]

So, first of all, Soulsow is legitimately a garbage ability.

I'd agree if and only we likewise removed downtime potency generation from everyone else. Otherwise, we return to the dilemma mentioned before, wherein encounters cannot support as many different means because each is also devoted to different capacities, meaning that a fight cannot support all jobs (despite this being a game that's pretty darn unfriendly to progressing across multiple gear classes simultaneously).

This is the third time this garbage piece of crap has been added to the game. The first time was Chakra in Heavensward.

No. Chakra filled three purposes:
1. potency recovery, complementing TK, for having to wind up for 7 GCDs each brief fight (since PB was, at the time, on a 3-minute cooldown),
2. a half-GCD modular tool, and
3. Monk's version of a ranged [or, not-range-limited] GCD that could be used in more situations (and initially at far greater ppgcd) than any other melee's ranged GCD.

None of those things apply to Soulsow, which is far more alike to SAM's Meditate -- likewise an explicitly downtime tool -- or MNK's Anatman (except that that one's not worth crap).

Yes, exactly, every button should be important. When you can go entire fights without using a button, or barely using it, that button better slay god or the devs should consider outright removing it. A perfect example is something like Huraijin or Soulsow, which may as well not exist if a fight has no downtime.

But that's the thing: fights do frequently have enough downtime that lacking those tools would then widen fight-specific imbalances (either by balancing more uptime-dependent jobs around high-uptime fights and having them suffer outside of those ideal situations or overtuning them to compensate for the less ideal) or would further constrain the balance of their potencies towards CDs despite being flavored as more continuous fighters.

Now, if you wanted to make that somehow passive (each half-GCD's time that a Monk is not under the global recast time = +1 Chakra; standing still for 2s grants a RPR buff that causes his next Soul Slice / Soul Scythe to hit for triple damage after standing still for another 3s), etc.... sure, whatever -- prune the unnecessary buttons. But I don't think there's anything necessarily wrong with an explicit downtime skill so long as we're unwilling to constrain fight design around highly varied damage profiles. I'm cool with either one; you just can't have Job A noticeably suffer in Savage/Ultimate Encounter X (especially, as a result of those removals) and then pretend that people will nonetheless regularly take Job A.

[Ninja] Personally, I think Heavensward ninja was the best Ninja ever was, and everything after it is a step backwards.

I would largely agree, outside of Armor Crush, which axed a mechanic of previously greater depth. The only thing that made it even a net-neutral addition (ignoring the added button cost) was its positional element, which synergized well with the flexibility of a buff of long maximum duration.
(Those longer durations, however, are not usually in themselves a good thing. Storm's Eye was made worse/duller, imo, for having been changed to the up-to-60s Surging Tempest.)

Personally, I would have much rather seen almost any other use for Armor Crush, though, and left Huton as a 70s Ninjutsu alone, with some accordant QoL/regularity buffs to Ninjutsu's cooling that eased TA timing without overly devaluing Fuma. Naturally, fixing the game's queuing and removing its round-trip-ping punishment upon uptime would be essential, though, since we'd be keeping oGCD Ninjutsu.

fuma shuriken itself

And there's the other funny thing: before they deemphasized NIN's combo ppgcd and dropped the more modular/mobile Mutilate, Fuma actually had an occasional purpose under SkS thresholds depending on one's Shadowfang/Ninjutsu sync: it was the option that cost zero uptime from clipping and could thereby help perfect Shadowfang uptime (wasting neither ticks nor opportunities for ticks).

Your 1-2-3 melee combo had no positionals

Aeolian Edge already gained a positional back in ARR. Dancing Edge, which was far from being a filler spam, was the one without it.

So if we no longer make TCJ give you a suiton, we can remove Meisui, a button that may as well press itself after you cast TCJ. So what is this button doing? We could do a 4-step mudra combo. It was teased all the way back in stormblood. At level 72 or so, give a trait to upgrade TCJ, and make it so that your 3-2-1 combo makes your next mudra used do an empowered effect. 3-2-1-3 would be some slaying god tier single target attack, 3-2-1-2 would be a doton that looks like an exploding volcano or something. 3-2-1-1 gives you mega-bunny, which is a DPS loss disaster recovery option where your bunny whacks the boss, in case you mess up, to make sure it's not a critical damage loss. If the fourth step did 2000 potency, the megabunny would do 1500.

...???

Seriously, what? Why would you want any of that. We use our 1-2-3 combo often enough that every Ninjutsu would be buffed, meaning, effectively, that none of them are; we don't even make use of all the Ninjutsu we have now, so we certainly don't need a 4-step mudra just to summon a mega-bunny, let alone as recovery option for if we overshoot the 3-step we actually wanted(???). And why the hell would we want a 2000 base potency Ninjutsu? That potency has to come from somewhere else, which then just means we're all the more at the mercy of those individually huge hits.

[Dragoon] BotD is more one of those things where in Stormblood, you could, and did, lose stacks due to boss downtime.

BotD doesn't have stacks... If you mean Eyes, then that's what Sonic Thrust was for on the likes of Neo Exdeath (serving two purposes at once, just fine). Since you weren't directly spending BotD by Stormblood, there were incredibly few cases short of lengthy cutscenes where you'd be forced to drop it.

Also it was nuanced even in Stormblood, where you had to reapply BotD before using LotD as the timer was directly tied to how much time you had left before bursting.

Not by comparison to how BotD worked in HW, no. By Stormblood, you simply hit BotD just before your 3rd-combo-step as not to waste duration, since most raid buffs were 4th GCD or later anyways back then, and then you popped LotD cyclically following your first. It wasn't even worth considering deeper SkS thresholds for additional Geirskoguls per BotD cast, nor to let HT or PB drop in favor of an extra Full Thrust+WT/F&C in banking for another round of cleave. You didn't have to be aware of upcoming downtime. It turned a risk-reward mechanic into just an uptime bonus gating an otherwise plain burst cycle.

Which again is... fine...? But if nuance from a mechanic that need not apologize itself is what you're looking for... the original approach was already there.

Honestly, Bard's DoTs have never been fine. Or rather, more precisely, DoTs are a bad game mechanic outright.

There's nothing wrong with DoTs. It's literally just one step's more complexity than a GCD-granted buff. If the latter is fine, DoTs cannot help but also be fine.

Both GCD-granted buffs and DoTs are essentially soft-CDs. The difference is that DoTs essentially have as many simultaneously-cooling charges as there are enemies worth DoTing.

Replace an instant-cast DoT that has some direct damage with an instant-cast potency buff to further GCDs and some direct damage in itself, and both can become your healer's soft-CD mobility tool. The difference is simply that one scales with target count up to the point that it's eclipsed by raw AoE, while the other does not.

The best-designed DoTs are Warrior's Storm's Eye and Reaper's Of Death.

GCD-granted DoTs are just GCD-granted Buffs+1, complexity-wise. There is nothing wrong with them, and even the likes of Dia at least supports more contextual complexity than Death's Design or Surging Tempest.

I'm all for doing more with DoTs, just as we could with buffs, CDR, or pretty much anything else. But there is no fundamental issue here.

Now, if you want to get rid of Iron Jaws (or at least pigeon-hole it behind a situational CD) and return Bard's DoTs to, say, most a 21-second duration so we could stop just keyswipe spamming Refulgent->Burst... I'm right there with you. But 45s seconds being stupidly long is not a DoT issue; it's an issue of an overly stretched-out duration.

[Monk] If you follow the 'natural,' rotation, that is you use the class and push buttons on cooldown without saving things, ideally in the highest to lowest potency order, then if you try using perfect balance on a purple combo after you did a bootshine-true strike-anything, you will go into perfect balance, and during your burst, Disciplined Fist will fall off before you can fire off your purple combo for elixir field.

Are you... playing at zero skill speed? This literally does not happen to me. Per minute, I clip roughly half my Disciplined Fists at ~3 seconds left and the other half at about a quarter-second left.

Moreover, the fact that your buff may fall off is not even an issue in itself; on the contrary, that being occasionally/situationally optimal increases the variety of rotational strings available to a job, alongside its overall skill ceiling.

For instance, back to ARR, it was very normal to let Dragon Kick fall off just after Snap Punch and Twin Snakes just after Dragon Kick to trade the total of 28 bonus potency in exchange for getting out an extra True Strike (50 potency over Twin) and Bootshine (some 65 relative potency over Dragon), so long as there was less than potency in non-GCD damage to be dealt over the time those buffs had dropped than a 10th that bonus (which, was frankly, almost always the case, minus Steel Peak, 2 AAs, and Howling Fist all somehow occurring in those brief gaps). This gave us more to track (both upcoming AAs and oGCDs) and more rotational variance and ultimately a higher skill ceiling for the job. That's a good thing, not some massive "problem" just because your buff icon briefly faded from view.

All the better, imo, was when it was even more situational via the likes of old RoF and timing TK-recoveries to minimize DK/Twin duration clipping and opportunity costs (of using them over BS/True).

Things do not need to be as simple as basic checklists like "Maintain Buff X (regardless of what actual bonus potency it'd generate or the opportunity costs it'd occur over the precise given span of time)". Bending those expectations in favor of more precise engagement/interaction is a good thing.

So, on the topic of abilities like that, I look at it another way. If you use X oGCD, and immediately follow up with Y oGCD, there's a problem.

I agree, so long as that is the only realistic outcome and it produces no noticeable gameplay impact in preparing for that outcome. I've referred to those often as "bundles" and have not shied away from hating on them... constantly. That's why I mentioned Barrel Stabilizer (but also, notably, not 5.x Ikishouten).

For SAM, I'd take Guren and Senei, upgrade Guren into Senei but make them both hybrid ST/AoE skills.

I'd be fine with that, but only because I don't find "Is the number of enemies greater than 1?" to be a compelling mechanic to solve. Insofar as button bloat goes, just having Ogi Namikiri replace Ikishouten while Namikiri Ready is active would be enough. SAM isn't particularly button-bloated as is.

Or even, just have Guren automatically convert to Senei if it detects no other enemy would-be in the line of attack. Voila; unless we somehow favored focus damage over total damage, you'd only need the one button. Do the same for Foul -> Xeno, (and perhaps Enlightenment -> TFC), etc. Doesn't ultimately change balance any, because everyone's doing the same anyhow, but hey -- the new animations look nice.

Then take Ikishoten, upgrade it into Guren, upgrade it into Senei... raising the skill ceiling, because you can actually store more kenki going into your 2m burst

...???

That's... not raising the skill ceiling. Less often caring about upcoming abilities or the threat of overcap (since, having removed the 50 Kenki from Ikishouten, you needn't be as conscious of the marginal cap)... is a reduction of the skill ceiling. The action, after all, is in the deliberate spending, not in just letting your Kenki bank higher and higher from having fewer reasons to be mindful of it or to optimize priority conflicts.

And you already hit 90-95 Kenki every 2 minute cycle. That's not new. You can already double-Shinten at the start of buffs, Ikishouten with just that single GCD's delay on the second use per fight (obviously, continued thereafter) to recap without having wasted the Kenki, and ultimately spend nearly 200 Kenki under raid buffs, precisely because Ikishouten grants that extra Kenki.