A QoL/Balance Shortlist for DPS (Tanks/Healers only as additional context)

[Grimoire-M]

I do not mean to disregard your opinions, but I want to be sure the complaints were made with full awareness of the places meant to address them. I've since underlined each in the above posts.

No worries, I did actually read them. That said, let's get to addressing my previous points so you can understand where I'm coming from. Because I sure as hell wasn't clear. Let's start with your Mana Shift changes.

Mana Shift has been buffed to anyone whom previously had a lower maximum MP than their target, e.g. from any caster onto a healer (or, say, a RDM onto a SMN/BLM), up to some additional 30% MP generation. This acts the more obvious 25% reduction in recast time, from 120s to 90s. The primary purpose of these buffs is towards providing a substitute for Refresh. Admittedly, Refresh itself maintains its previous power in this regard, but it has at least lost some double-Ranged value despite MCH being an equal recipient to its benefits.

The problem with this change has nothing to do with how it affects the target. I have few complaints there (imo it's not enough, but the idea is appreciated). The problem is you've ignored the cost to each caster, and that's the biggest issue here. BLM needs to use a Thundercloud proc during UI in order to use Mana Shift without clipping or a major damage loss, and that's basically unavoidable without changing T3 or B4 into instant-cast spells currently. And even with that, their AF/UI rotation artificially gates the cooldown for them, meaning they will never be on par with the other two using it on cooldown. It's sort of like MCH's heat problem, to give a comparable example.

Which gets us to RDM's problems with Mana Shift. Simply put, they cannot afford to use Mana Shift on cooldown and still Raise on demand without a Bard or Machinist in the party currently. Last I checked, it takes two Lucids to be able to Raise once with minimal cost and still sustain Mana Shifts on them. And that's assuming they don't die. If that happens, good luck affording anything. The lower cooldown only exacerbates this problem for them, and while I see you attempt to address this point seperately, we have to keep in mind that the MP boost on revival is a catch up mechanic, not something to consider overall.

Summoner, by contrast, can afford to hardcast Raise and still use this because they can sustain their own MP easily without even factoring in Lucid Dreaming or Energy Drain at all. I've died on SMN before and been able to still Mana Shift for full value almost immediately after being raised. This is partially due to Lucid and Mana Shift's current cooldowns matching one another, sure, but the real reason is because of how SMN was changed in 4.0 and 4.1. The 4.0 changes resulted in SMN barely using their MP on anything other than Ruin III due to the combination of the Tri-Disaster reset, removal of their third DoT spell and its higher cost, changing Shadowflare to an oGCD with no cost, and the addition of Lucid Dreaming to further sustain spamming it. 4.1 then merged Ruin I and III together, massively freeing up their MP pool, while the lower MP cost on resummoning pets makes it easy to recover even if they do die. All of those changes essentially removed all the barriers to their MP management to the point that they actually can break ahead solely off of Aetherflow with a low enough GCD. Lucid actually winds up paying for the Mana Shift and a Raise and then some on SMN specifically as a result of all of this. This is why I said it was only a buff to SMN. They're the only ones who can actually take advantage of the lower cooldown. If you want to significantly buff the skill, you first have to lower the cost to the caster relative to its output by significant margins in order for RDM to be able to use it more liberally, or remove it completely so BLM can use it during AF without a major DPS loss. If you don't start there, you can't even begin to speak of competing with Refresh.

And on that note, if the explicit goal is to compete with Refresh, I have to wonder why you aren't removing Refresh's AoE component and turning it into the MP equivalent of Goad and giving it to both the Ranged and Caster DPS respectively instead. If it's just for the Foes interaction, I'd actually argue that the mana spending on it should be removed, especially given the TP/MP consolidation that's coming anyways. It's a gimmicky interaction that doesn't need to stay just because it existed in ARR/HW at one point. If you want that kind of resource management, arguably you could make an independent song cooldown that can accompany the base song rotation, which is simply about keeping that buff up using the procs you get.

Speaking of resource management, let's talk BLM.

The exact MP will vary, but the %base MP will not. At present, many BLM spells almost to follow irrational (in the technical sense) number, as if they were originally set to a different product of factors or with inclusion of Piety effect on casters and have been gradually nudged to the arbitrary and convoluted fractions we see now. So long as the next product given for maximum MP maintains the same involved primes, the smoothed numbers and more sensible %MP counts should remain smooth in 5.x.

The problem with this is MP costs don't scale with anyone's base mana. They're based on their level 0 costs (which, yes, level 0 does exist) which is multiplied by a universal modifier that grows based on their level. This formula is different from their base MP growth formula, which unfortunately grows slower than the costs themselves and is what lead to the ARR/HW Piety breakpoints in the first place. BLM hasn't had the right numbers in place because the current formulas don't allow for that kind of granularity, which just tells me that it's a leftover from 1.0. SE has since 'fixed' the breakpoint issue by making Piety only affect healers and has repeatedly tuned BLM's MP costs down in order to support their ideal rotation, and I expect them to do so again next expansion in order to account for whatever new rotation they decide on. These MP cost changes are basically meaningless within that context, though I do support the idea you were going for. My personal hope is that they address some of BLM's clipping and mobility issues in general regardless, and there are plenty of ways to do that while retaining BLM's status as a turret DPS.

The nerfs to BLM would only be present in the most perfect of fight circumstances. In all others, it was a buff.

It was a buff that doesn't really alter their gameplay, which BLM does need some help with. Rgardless it was a nerf to their maximum DPS, and due to the nature of the class as a sustained DPS powerhouse, it doesn't really help them at their niche. I can agree that maybe BLM doesn't need that much damage, but I also think that their real problems have nothing to do with their raw DPS output in an ideal scenario. Instead they mostly have to do with how they have to push it, and how that impacts their fight-to-fight optimization. For example, a big thing you could do is reduce the cast times on Fire/Blizzard IV and Flare to match the GCD while tweaking their damage accordingly. Because currently it is a DPS increase to use these abilities in a specific manner that ensures you're never hard casting Fire IV if you can help it. This way you ensure that BLMs are only taking movement into consideration when using these abilities aside from solving clipping issues in their opener. That's the starting point in my opinion. What you do from there is honestly not as important. Numbers rarely bother me unless they explicitly have significant rotational impact, which is extremely easy to avoid on damage potencies.

That said, let's look at RDM again.

The changes to RDM are, on the whole, a total (rDPS + pDPS) buff.

Sure, they are. What bothers me about them has little to do with the fact you want to buff them. It's the gameplay that arises from it. I'll pull my quote up again for this.

Getting melee combos 6% faster, pushing RDM to use their oGCDs more for a minimal amount of gain and retuning Embolden to be backloaded instead of frontloaded is not gonna make up for losing all of that base damage either. Putting all of that focus on their spike window is not going to help them when they're not guaranteed to see it at specific times. They get one more GCD to flex for it. Big whoop.

I must say, I doubt that. RDM was not a low total DPS job even before 4.4 buffs. These are a huge boon to its rDPS. I pulled back on a couple of the potency reversions (namely melee-flare combo), but I honestly worry I may have to come back to it and nerf them again in order not to make RDM the dominant tDPS when played well. I will likely have to undo what I've undone.
The Corps-a-corps and Displacement changes were made not to force greater apm, but simply to compensate for the increased flexibility (and with it, average frequency) of the melee combo. Perhaps you'd prefer that the melee combo itself accelerated the cooldown timers in order to ensure their alignment?
The added flexibility should be up into the order of 40 seconds in what would otherwise have been ill-timed generation as forced by downtime, and several GCDs when taken in combination with Impulse and the melee combo B/W Mana cost reduction, not merely a single GCD.

RDM's overall mana generation without factoring in the melee combo and Verflare/Holy's contributions currently averages to a bit over 10 each GCD if managed optimally. In practice it doesn't vary much at all. Bumping their melee combo down to 75/75 only opens up one more GCD per rotation typically, which helps with desyncing somewhat, but doesn't change how it's used. Your Impulse trait will make Jolt II break ahead of using Verstone/fire after two dual casts, which only serves to tighten that timing up. I'm fine with that, but the combo cost change doesn't let you accelerate with Manafication much faster than you currently could, meaning those timings don't really change at all. Sure, being able to use Manafication mid combo lets you accelerate by another 20 mana every 2 minutes on top of that, which at best lets them break even with their normal mana generation rate with minimal loss, but given the length of that sequence in the first place, it's unlikely to gain more under raid buffs even when well timed, which at best is just going to be Battle Voice & Litany. To me, what RDM wants is a way to properly align their melee combo with raid buffs without having to sacrifice their sustained DPS. Thus, they need more meaningful ways to control their mana generation. Helping them accelerate is a good idea, sure, but a much more meaningful way to contribute to solving RDM's issues is to give them a way to slow down their mana generation, allowing them to align their melee combo at a more appropriate time rather than simply mashing it out at every opportunity.

Furthermore, you add another Slashing/Piercing condition and physical/magic overlap onto the melee combo specifically to compensate for some of these nerfs. Do you really want to do that? Really? You're creating the same problem BRD has with crit rate, in that you're giving RDM exclusive access to raid buff synergies the other two casters will never have access to. Contre Sixte and Fleche and the dashes are already treated as generic physical damage, and are the only abilities in RDM's kit treated as such. The melee combo itself is fine the way it is. The problem lies solely with RDM's mana generation and lack of sustained DPS, and is already locked to heavy physical comps due to how Embolden works, none of which are addressed by this. It's actually counter productive to your stated goals.

However, your oGCD changes bother me for a different reason. While they compensate for the damage nerfs in theory, they ignore some of the fight issues RDM already has with them. Displacement is already notoriously awful to use in certain fights and putting more weight on finding opportunities to use it is only going to be detrimental to their damage in the long run. In my opinion, none of the dashes should have potencies to begin with. Maybe just Corps-a-corps, but certainly not on Displacement. Shift the potency on that into Contre Sixte and Fleche, which don't have these issues. That way RDM can function in any given raid environment without getting randomly screwed out of damage because the arena is too small or the edges decided they're on fire. There's a reason Bard had the potency on Repelling Shot removed.

I don't get why you're trying to preserve Embolden's decay by flipping it into a growth effect either. If anything, it actually makes it harder to use for the average player. It could easily be bumped down to a 3% static boost to everyone's damage that's doubled for yourself for the the original duration/cooldown and provide equal benefit in a standard comp without creating weird timing issues in the opener or for subsequent use. You already aim to place the 10-6% window around the same time TA is up regardless. I agree that the rDPS boost of your current version might be too much, but I feel the way to approach fixing Embolden is to make it easier to use for players regardless of composition while nerfing its overall impact, and tune up from there if needed. To me, if you want that kind of damage ramp or decay, make it a personal only cooldown instead. Once it starts affecting the rest of the party you get timing tension that doesn't need to exist.

That, finally, brings us to our last caster DPS.

Which SMN issues have I glossed over, if you may be specific? I will correct what I can without creating further issues in the process.

Plenty, I'm afraid. We'll start with the biggest issue in the room. Pets. Are. Garbage. And unfortunately, I can say that you didn't actually accomplish anything in that regard other than the usual signposting we get about it.

Sic no longer prevents the manual casting of spells and abilities.

The problem with this Sic change is it doesn't actually do anything meaningful. The current Sic and Obey already don't work properly. All you're really doing is hiding the problem with Obey using Sic. Pets are unresponsive to the player for the same reason that Rescue feels garbage to use unless pre-planned. The engine and server prioritize animation fluidity over responsiveness, and part of that means they backload some of their mechanical work onto the server before playing their animations, rather than risk massive desyncing. Pets take one mini server tick (the same one Macros operate on incidentally, which corresponds roughly to 1 second inbetween each action check after inputting the command initially) in order to ensure that the command was properly registered. Rescue takes two, both double check each player's relative positions and attempt to properly root the target for the animation before it goes off. Sic just makes it so that these checks are done 'automatically' by the server for the pet oGCDs once they start attacking. Any manual input has to fit into one of the micro-ticks in order to execute properly, and that includes Enkindle and Devotion.

The reason Ifrit works so well on Obey or Sic is because its auto-spell is instant cast, leaving two mini-ticks inbetween for proper checks, allowing it to actually weave properly. That 1s on Wind Blade is enough to screw up Garuda's timings on Obey because she's in the middle of her Wind Blade animation for one of those mini-ticks and begins casting it on another, leaving her with only one guaranteed mini-tick check per one of her GCDs. And Embrace's 2s cast practically guarantees a clip on the fairies no matter what unless you use Sic, from what I've seen. The server unfortunately doesn't do pre-casting in the same way a player would force it to by mashing a button. If it fails, it tries to queue the action and waits another second or drops it entirely, with two exceptions. One of those is the auto spells, which appear to queue automatically and are likely the cause for those drops, but I can tell you it's nowhere near consistent. The other is movement. As long as the pet isn't moving, it can predictively queue a check to eventually ensure it goes off, but moving inbetween at any point breaks that queue, which I've been told can allow you to forcibly execute a command, via a combination of Place and Heel into whatever oGCD you want, or using a different oGCD then Embrace with Selene on SCH, though I personally find that awkward. I believe this is why the Egi auto-root themselves once they've landed an attack or heal and why they're so often not affected by knockback effects. This is done in order to facilitate this check for the auto spells specifically. The only exception I've seen to this is if the action itself requires the pet to be in melee range in order to execute it when they're not, in which case everything, even the auto spells, is simply halted until the pet is in range and that ability is executed. This applies to Crimson Cyclone, Inferno (once properly queued), Shockwave, Mountain Buster, and Landslide specifically, all of which are treated as melee range pet oGCDs.

The only way to fix those issues is via constant engine updates made to tweak these problems out, and I 100% agree that they should have been fixed ages ago. However, I have no qualms saying it's not gonna happen anytime soon. These issues have been known since ARR and they're still not fixed. For all intents and purposes, I think we should assume can't be fixed. However, they can be designed around in the meantime, and that's the real thing that bothers me. How do we do that then? Well, let's start with what works. Rouse.

Rouse is the only pet skill that isn't screwed over by the server checks. Why? Because it's a buff you apply to your pet. Pets can recieve and register buffs immediately, like a player would. If you want to fix pet responsiveness, you can use that effect to work around the problem with pet AI. Each pet oGCD can simply put a buff on the pet to command them to use the given action the next time they're able to, which the server is already checking for. It gets around the biggest problem pets have regarding their responsiveness, dropping inputs due to auto spells. Use that, and they no longer have that problem. Sure, they will still have a delay, but the player can now observe it, and that's enough for them to be able to work around it. That's the easiest way to ensure they're actually responsive.

And for the record, I'm fine with your button consolidation ideas. Maybe not with SMN specifically, but in general I agree. Which leaves this last nitpick.

Note also that SMN lost, in exchange for its QoL changes and greater pet reactiveness, the bug-gimmick of extra Wyrmwaves via cross-class skills.

I'll be honest, Wyrm Wave proccing off of oGCDs in general is a big problem to me. It's functionally easier to make it so he only considers your spells (or just the Ruin line, even) when making his attacks, and would go a long way to making him feel more fluid. The alternative would be to implement a pet hotbar, which I believe SE was trying to avoid in the first place.

The lack of a pet hotbar is why Bahamut feels so awful to use regardless of his oGCDs. He doesn't technically have an auto-spell, at least in terms of server checks, because of his 1.5s GCD timer doesn't sync up with them. Yet it is prioritized over certain kinds of movement like an auto-spell would be. However, he doesn't root himself once he's attacked something the way the Egi do. I think SE removed that function for his implementation specifically in order to avoid needing a hotbar at all. His current priority is to use Wyrm Wave if commanded, first and foremost, then to follow the player till he is in Heel range, then to use Akh Morn, assuming he remembers. If you keep queuing Wyrm Waves for him to use he stays in place. The moment he has a break he often barrels towards you, and the only way to make him stop if you want to use Enkindle Bahamut is to queue a Wyrm Wave immediately and move towards him and wait till he begins charging (there is an audio queue for this before he uses Akh Morn).

All of this could be fixed by rooting him in place once summoned or upon attacking, but the cost of doing so is SE would need to give him a pet hotbar so he could be Heeled and/or Placed, otherwise there would be complaints that he feels bad in dungeons. Or they could let him break Line of Sight rules, but that just creates an even bigger mess, tbh. I believe they did this as a compromise to avoid having to do any of that. Which is fine, in theory. In practice however, it feels like they really should've just implemented his pet hotbar if they wanted to keep this current iteration in tact. The reason they didn't is because he's only around for 21s out of every 2 minutes. He's not worth doing that for.

In my opinion, making him queue Wyrm Wave off of spells and altering his priority to first use Akh Morn if told to is the way he should've worked in the first place. That way Wyrm Wave would have been a cleaner implementation, while changing Enkindle Bahamut can be accomplished using the above pet command buff change I outlined above, even if the player can't see it on a menu, an aura on Bahamut himself would suffice.

This is the bare minimum SE can do to address SMN's issues without changing any buttons. From here, I'm spitballing based on preference.

And I'll get it out of the way fast. Heavensward SMN was the best overall implementation of the job to date. It was not the the most fluid to use, not well designed overall, and not well balanced, either, but what Heavensward added was still overall better for the job, relative to what Stormblood added. This came as a result of how ARR SMN overall felt incomplete. The a combination of things specifically added to SMNs kit in Heavensward fixed a ton of issues they had coming off of ARR. Booksmacking was a weird gimmick yet free damage that was absolutely significant. Setting up DoTs took a lot of time. Maintaining them was sometimes awkward, particularly when it came to optimizing Raging Strikes windows, and outside of that they didn't really have much to do. Pets still felt awkward to use, and their cooldowns did not feel all that impactful, but Contagion made Garuda an auto-include because she extended your snapshotted DoTs. And their AoE always kinda felt bad, because of the 4-target limit Bane had at the time. Even with the lack of fall off.

Heavensward solved every single one of these issues except for Contagion.

DWT became the centerpiece of the class, adding a cooldown that sped up and unified SMNs buttons around a single burst phase. The only problem with this was SE's intentions for the ability did not match the way players used it. It was supposed to be a Ruin III filler button only, but it wound up being better than that in terms of flow. 15s out of every minute oddly enough felt like the right amount of time for a burst phase like this too. Significant enough to matter, but also left enough downtime for you to care about it when it came up. Aethertrail and the old timers on Fester/Painflare added this neat if needless tension regarding its timer. You couldn't fit all three under Aetherflow, but even if you could, you would've had to save one in order to refresh the Aethertrail timer. Sometimes this didn't align with a fight, but the DPS loss of simply using DWT again in order to account for downtime in a fight wasn't that bad, either.

Tri-Disaster solved the issue of SMN taking time to set up their DoTs and its 1 minute cooldown was perfectly aligned with DWT and Contagion, letting you snapshot your DoTs under the window. But they didn't let you ignore your DoT spells either. You still had to use them once every single minute even with Contagion's extension, naturally creating their own a micro phase where you ramped down in preparation for your next Aetherflow refresh before you ramped up again.

Ruin III gave SMN more damage at no cost inside DWT and something to care about outside DWT, MP management. Initially this was 120 potency, so it was still worth weaving with Ruin II before it was buffed to 200 potency, which resulted in simply spamming it and eating the clips on Aetherflow wound up being better overall DPS for most players, only NA players with super high ping couldn't take full advantage of it, though using Swift cast let you get around that problem.

Painflare gave SMN something to help accelerate their opener and much needed AoE burst. You only ever got 1 or 2 of these per aetherflow, but it felt like something.

Bane had its target limit removed and a damage taper off added, that, to be frank, I don't think was actually working at the time. But man did it ever feel good to use. What made it grossly overpowered was the sheer amount of things you could fuel into DWT. This was the biggest headache SE had to deal with, because buffing SMN's DoTs would feed into their already massive AoE potential. A1/2S were their fights, hands down.

Deathflare was and still is just a big old nuke. It was the hardest hitting spell or ability at the time, and accomplished it's goal of being that 'big spike' send off to DWT that SMN needed at the time.

Their main pitfall at the time was in those nuances. Dumping MP into Ruin III wasn't obvious. Aethertrail's timer made managing it optimally clunky at times. and the fact that they had so many buttons to press in a short period of time in a very specific order every minute was reminiscent of the same problems MCH has now, but not nearly to the same extent as MCH. The payoff wasn't nearly as important, yet it was also incredibly easy to get rolling. Spur/Rouse contributed to the bloat problem massively, but Miasma II had its odd moments too, since extending it with Contagion was a DPS boost, and thus was worth it over the old Ruin III too iirc.

I agree that HW SMN needed button consolidation and specific changes to make using them easier back then, but not at the cost of their flow. Their overall flow was fantastic at the time, making their few problems actually less of an issue than they are now. When you look at that and what Stormblood did, I honestly feel what we got was a mixed bag. The Aetherflow lockouts were the worst change Stormblood made, easily, and every change made to Ruin III afterward was basically done to justify it. Bahamut is frustrating, the Tri-Disaster reset was completely unnecessary, and Devotion was not well implemented in the first place before being given the bandaid buff it didn't really need. While Spur was removed, Rouse still exists, and it also has its own lockout with Bahamut that also shouldn't exist in the first place. The lower cooldown on Fester/Painflare, Contagion change, DoT consolidation and the Shadowflare rework were good for balance but also removed some of SMN's base rotation in the process, and I've already noted what they and Lucid did to their MP management and how that destroyed what little there was left to care about in the single target rotation. The Tri-Bind change was more or less a patch over the Bane nerf that imo wasn't really necessary. More than anything else, however, the one thing that does not make sense to me is Bahamut. Bahamut should have been an extension of DWT, not a seperate phase that winds up replacing it entirely. Particularly when you factor in their clunky implementation and what SE did to make DWT work afterward, it's hard to justify keeping them seperated in the first place.

I made a poll and thread about the Aetherflow Lockouts specifically on the cusp of 4. being released, and it had a 60/40 Ratio in favor of removing them. In the thread most of the people in the 40 count that spoke up either cared more about Bahamut's addition and the micro-phase feel the lockouts created than how it used to work, as many of those people were either new to the class entirely, or had tried it previously in ARR/HW and simply dropped the class immediately rather than stick and learn the optimal rotation at the time (Which I personally attribute to all of the X minute personal cooldown stacking going on at the time, and not learning to track that stuff based on Aetherflow's cooldown and the Aethertrail Timer specifically being a major point of frustration, both problems that have since been fixed).

Given a choice, this the full list of things I would do to fix SMN:

- Aetherflow Gauge reworked. Aetherflow and Aethertrail are allowed to coexist again. Executing Aetherflow abilities still grants Aethertrail, surrounding each Aetherflow socket with a blue outline on the normal UI, and having three seperate nodes on the simplified UI to track Aethertrail.
- Fester and Painflare reworked. Now share a cooldown of 2s. (This just tightens up Aetherflow usage in the opener without causing any issues elsewhere).

- Dreadwyrm Trance reworked. Now replaces Rouse via a new trait, Trance Mastery I. Increases Magic Damage Dealt by 10% for 20s. Also applies Rouse to pet, increasing healing magic potency and damage dealt by pet by 40%. While roused, pet will be immune to Stun, Sleep, Bind, and Heavy. Costs 3 Aethertrail to use, and has a 20s cooldown. (No longer prevents the execution of Aetherflow abilities while under its effects, reduces the cast time of Ruin III, or increases the potency of Tri-Bind)

- Tri-Bind Reworked: Now called Tri-Ruin. Deals unaspected damage with a potency of 60, with an MP cost of 720, the same as Bio III. (No longer inflicts Bind, but now counts as a Ruin spell for the purposes of Ruination)
- Bane Reworked: Spreads any debuffs you've inflicted on a target to nearby enemies. Potency of your damage over time effects is reduced by 20% for the second enemy, 40% for the third, and 60% for all remaining enemies. (Now spreads Tri-Disaster's third debuff in addition to Bio/Miasma III. Maximum damage drop off has effectively been doubled without changing the curve at all)

- Summon Bahamut reworked. Now shares a cooldown with Dreadwyrm Trance. Increases magic damage dealt by 10% for 20s and summons Demi-Bahamut to fight by your side. Each time you use a spell on an enemy target, Demi-Bahamut will execute Wyrmwave on the same target. This action cannot be assigned to a hotbar. (Triggering from abilities removed. DWT's Damage bonus added. Deathflare, however, is not available during this period.)
- New Trait added: Trance Mastery II. Allows for the strengthening of Dreadwyrm Trance with Dreadwyrm Aether upon executing Deathflare during Dreadwyrm Trance, enabling the summoning of Demi-Bahamut. When your Dreadwyrm Aether is fully stored (2 units), Dreadwyrm Trance will change to Summon Bahamut. (Note: This results in Bahamut being summoned once every 3 minutes instead of 2.)
- Wyrm Wave potency increased to 200. (This is there mostly to compensate for the damage nerf inside Trance, not the nerf to how often you can use it, which is an appropriate nerf, imo. Notably, as a result of the trigger changes, this ability actually gains value from from spell speed without needing a direct potency boost).
- Enkindle Bahamut reworked. Shares a cooldown with Enkindle and replaces it during Dreadwyrm Trance. Cannot be assigned to a hotbar. (Sorry, less Akh Morns)
- Enhanced Enkindle reworked: Reduces Enkindle's cooldown to 1 minute. (Distributing the lost Akh Morn damage around to every DWT instead via this change, and removing the proc in the process, which really had no reason to exist in the first place.)
- Tri-Disaster reworked. Now afflicts target with Bio III and Miasma III. If used while not under the effects of Dreadwyrm Trance or Summon Bahamut, also inflicts Ruination, increasing the potency of Ruin spells used against the target by 10 for 15s.
Summon Bahamut Effect: Afflicts target with Vulnerability Up, increasing all damage dealt to the target by 3% for 15s.
Dreadwyrm Trance Effect: Afflicts target with an additional status effect depending on Egi you currently have out for 15s.
- Garuda: Increases target's magic damage taken by 10%.
- Ifrit: Increases target's physical damage taken by 5%.
- Titan: Decreases target's damage dealt by 5%.
(A lot to take in, but basically Tri-Disaster does something appropriate based on what Egi you have out when used at an ideal time. These effects can also be spread over multiple targets)
- Ruin I potency increased to 110.
- Ruin II potency reduced to 90. (Accounts for booksmacking at low levels and discourages overusing it for mobility. That's it).
- Ruin Mastery reworked. Ruin I now grants Further Ruin I, enabling the use of Ruin III/IV. Further Ruin stacks up to 3 times.
- Ruin III reworked. Now deals unaspected damage with a potency of 200. Costs one Further Ruin stack. This cost is ignored while under effect of Dreadwyrm Trance or Summon Bahamut. (Ruin III no longer replaces Ruin I)
- Ruin IV reworked. Now deals unaspected damage with a potency of 200. Costs two Further Ruin stacks. Cost ignored while under effect of Dreadwyrm Trance or Summon Bahamut. This cost is ignored while under effect of Dreadwyrm Trance or Summon Bahamut. (Ruin IV no longer replaces Ruin II)
- Enhanced Ruin II Reworked. Now called Ruin Mastery II. Grants a 15% chance that a pet action will trigger Further Ruin I. Ruin I now grants Further Ruin II. Ruin II now grants Further Ruin I. Maximum Further Ruin stacks increased to 6.

- Contagion reworked. Now deals wind damage with a potency of 100 and inflicts wind damage over time with a potency of 100 to target for 15s.
- Radiant Shield reworked. Creates a barrier around self and nearby party members for 15s. When barrier is stuck, deals fire damage over time to striker with a potency of 30 for 9s. (This is comparatively minor damage compared to the old version, but still has a notable advantage in certain AoE situations compared to Contagion. Contagion's significantly stronger in single target situations specifically in order to help combat the extra damage Ifrit provides via auto attacks).

Dissonance was indeed an overbuff considering the decreased Repertoire waste in Wanderer's Minuet. I've since tuned it back overnight since the original post. I'm under no impression that Grenado Shot or Wide Volley are strictly "needed". However, I don't feel that their removal was at all needed either. The reason given at the time was button bloat, but the game has since introduced key stacking, nullifying that reason.

Personally, I don't feel the way you're altering Bard even after these changes is all that meaningful to be honest. It's not for lack of forethought on your part either. There are things I like and things I dislike. Allowing WM to store PP stacks and making Bloodletter/Rain of Death affected by Skill Speed is a nice change for sure, but the cooldown doesn't really need to go on the former at all. You're gated by DoT ticks already and they sync up perfectly, and under optimal conditions you're not proccing more than you can handle very often. I appreciate the intent behind the Paeon changes but disagree with the execution. Arrow Helix sounds like an implementation nightmare and I would not wish it on any intern. Twin Bolt is fine but I question why you're doing this when Barrage exists and I don't really want to think about how that specific interaction would work. Ballad doesn't really need to be any more busy, again for the same reason. DoT ticks already gate its use just fine. Dissonance's numbers worry me a lot too when you factor in just how good Ballad is for AoE already. Overall the fact that you'd be pressing the same two buttons inbetween GCDs regardless of song ad-nauseum is what raises the biggest red flag to me. I get the point behind the consolidation but some of it is consolidation for consolidation's sake. Refulgent Arrow doesn't need to be moved to Heavy Shot either, you just need to upgrade the Heavy Shot proc so it instead reapplies Straight Shot's buff immediately and grants the current RA proc instead. RA is something the player has to decide when to use and shouldn't be moved onto your main filler button, and that buff solves the problem of putting it on Straight Shot without that much of a DPS increase to Bard overall.

And I don't think people realize just how good stacking crit rate is on Bard in terms of affecting their overall DPS. Just by the nature of the class stacking Crit creates a positive feedback loop of more procs which leads to more oGCD spam which in term gives you more chances to crit again for even more damage. Between your oGCDs and your GCDs, your GCDs do hit harder and more often, but the more crit you have the more your oGCDs are able close that gap, to the point that they can be worth almost half of your damage contribution if not equal for two of your three songs. AST and SCH are already considered the best two healers and if the former draws a naked Spear Bard is hands down the best class to throw it on. Unlike other raid buffs, these stack additively. And that works in Bard's favor in this case. If Chain/Litany are both already up on the boss giving them a Single Target Spear is morely likely to beat out spreading it than any other card on any other class. DRG and SCH's buffs both sync up with the potion timer in order to 30% Crit Chance for 45s every 6 minutes and 15% crit chance, which was more than you could get at the beginning of this expansion, and when you factor in snapshotting, that bonus is available for the majority of each Ballad afterward. I believe now with the current BiS gear you only require one of these two to push over the threshold where it's better to spam Pitch Perfect on cooldown in WM, while in Ballad you're already all but guaranteed to be spamming it repeatedly.

Removing Foes feels like a missed opportunity too, namely because adding a song specialized for AoE DPS specifically over single target DPS would actually change up your song rotation based on any significant AoE phase present in the fight that you could take advantage of. Ballad is your all-around good song, Paeon is filler when nothing else is better, WM is strictly single target DPS, so adding Foes as the go-to AoE song and toning down Ballad's AoE contributions while toning up Paeon makes perfect sense. Battle Voice, while handled better than Foes is currently, is unfortunately a flat out a mistake given the TP/MP merger coming in 5.0. Just make it into a standard, no nonsense raid cooldown and leave it at that.

All you're really doing in effect with the Wide Volley/Grenado Shot changes is creating a needless and somewhat hidden punishment mechanism. I'd be equally as fine with it if you wanted them to have the extended range period and simply replaced the original skills with them. My problem with it is they don't really add anything meaningful when it comes to their AoE rotations as it is. There are alternative ways you could actually add them back in that actually do something other than drain TP faster. For example, Grenado Shot could be added back in on MCH specifically by using a toggle effect to alter their Single Target combo into an AoE one. It doesn't save any buttons since you'd be consolidating the current Spread Shot in the process, but it does allow you to actually add it back in a meaningful manner, as well as adding a third AoE weaponskill to help with their burst. Wide Volley could easily be added back in while Quick Nock could be remade into an AoE version of Empyreal Arrow (Quick Nock has the better animation for being made into an oGCD, hence why I chose it over Wide Volley), existing independently from other weaponskills and having its own internal cooldown but gaining similar properties from its trait. That would help Bard's baseline proc management with minimal effect on their gameplay too, and arguably they might even need the personal damage boost after pulling them away from Crit or scaled procs altogether as described in my earlier post.

True, but, should I be seeking to decrease skill gap? It seems like every other good MCH's reason for maining MCH is that they can play it well when so few others can. I'd prefer to see changes of a much larger and more fundamental scale in 5.x, but for now such changes would be more controversial than appreciated, I fear.

Skill gap is, specifically? MCH may have warrant for such a claim, but in five years of daily forum lurking I've only once heard it opined that the ranged and caster roles are divided thematically or practically by their skill required. I will take it under consideration, but, again, it seems out of scope for a balance/QoL thread in mid-expansion. Wide Volley, Grenado Shot, the BLM MP changes, etc., may seem or even be superfluous, but they are also very, very simple to implement. A numbers change to make a significant influence on MCH skillgap may be similarly simple, code-wise, but I lack the expertise on my own to craft it, while the more fundamental changes I have confidence in the success of, if introduced, would not be so simple.

I'm just gonna say this, when it comes to MCH, it isn't about the skill gap. Clunkiness. Is. Bad. Period. People jumped ship from MCH because of how SE changed it in Stormblood, and while arguably it had a similar problem juggling so many cooldowns all at once in Heavensward, so did many of the other classes, and it was on a slow enough scale that it could be managed. MCH may be hard but it's not for the right reasons in Stormblood. The only meaningful long-term skill test added in Stormblood was immediately patched out of relevance in 4.1, destroying the job's optimization in the process. Everything else was done simply to speed up the job overall, to the point it winds up being a detriment due to specific abilities and their interaction. HW SMN had a similar mad-minute rotation with forced clipping and specific timings that had to be accounted for while dealing with the clunkiness of pets. It nearly commits every single fluidity and functional mistake that MCH does now in Stormblood, but it was in a far better state comparatively because it wasn't nearly as punishing. You could deal with mis-alignment and Contagion actually was bearable back then. And even back then it was considered clunky by players at the time, myself included. The difference is instead of needing to rework half the kit from the ground up again like MCH needs right now, it only needed two changes at the time; a way to weave Aetherflow in during DWT without clipping your GCD or a major DPS loss, and the removal of the timer on DWT. Everything else was gravy. MCH has heat generation problems. MCH's Overheat and Wildfire timers leave you little room to actually adapt. They have to deal with Flamethrower being the only oGCD that roots you in place while you use it that also requires you to actively use it in your full rotation. They have to deal with Rapidfire clipping. They have to make sure they're aligned with TA perfectly. And they have only 10 seconds in their most important burst window They have to deal with gear optimization no other class does because too much skill speed actually hurts their overall damage at certain breakpoints because of all of the above.

None of that addresses your changes at all, however. I'll rattle them off.

Turrets should be affected by every buff except magic damage. Hypercharge does not need to be a copy of Foes. Same reasons as outlined above. The current Hypercharge is fine. Bard needs to be toned down anyways. Overdrive does not need a nerf, which by the sounds of what you've described is your intent, in order to make the skill something you only use before any downtime. It should resummon the turret automatically after the debuff wears off, even I could see removing that penalty on it or removing the skill entirely before SE ever fixes snapshotting. Flamethrower will probably never get the changes you describe, because SE hates making anything tick at a rate higher than one second, and even with that I don't think the changes help with how Flamethrower is used. Right now it's the only thing that lets MCH enter overheat that's oGCD at all and I think one way you could solve the heat problem is by simply letting Flamethrower instantly put you in Overheat rather than all the awkward fiddling you did with its heat generation. Granularity does help but in a lot of ways in this case speed is the real issue.

I appreciate the extra turret commands you added, Gauss Barrel's rework into a trait is something everyone agrees on. The addition of Detonate can help in specific instances, and Rapid Fire's overall changes are good. Those are small things that can happen within a reasonable time frame. I would suggest reverting heat to the old system and adding heat reduction options to Gauss Round/Ricochet and potentially removing the heat generation from Clean Shot. Something still needs to be done about Overheat as well but personally I hope SE actually increases the duration of Wildfire and Overheat to make them easier to use. You do this to some extent but not enough imo. The window is already super tight and anything you can do to widen it more than the bare minimum to accomodate your Rapidfire change helps high ping players out a ton specifically.

I'd argue that Hot Shot should carry the piercing debuff instead of a damage bonus and grant 50 Heat (with ammo bypassing it as usual), which eliminates that DRG dependency and the heat bonus helps with most of MCH's problems in a much better way. Barrel Stabilizer doesn't really have a purpose outside of deaths or as a mid-cycle heat managment tool as a result of that. Overheat itself really needs to be changed to only begin its timer once you've used a weaponskill at 100 heat. Reaching 100 Heat in any manner, including using Flamethrower, still puts you in that Overheated state, meaning you can't use Cooldown to exit out of it, but the timer doesn't start until you use another weaponskill. It seems unnecessary, but it would also help alleviate the currrent skill speed issue a bit as well, and if don't want to mess with the current Heat mechanics at all, I'd recommend it over any of my other suggestions precisely because it and the Flamethrower change solve most of these problems.

I do have some thoughts on Monk specifically, but mostly under the general opinion that positionals need rethinking on melee DPS, and it's the class that needs the most work in that regard. What I'm suggesting is relatively minor, however. I'm tossing it out mostly because of mentioning Deep Meditation earlier, as I have a proposed rework for that trait, Meditation, and a couple weaponskills. The weaponskills in question are simply the Coeurl Form single target skills. Drop the positional requirements on those, and only those. My idea for Deep Meditation is to split up the Chakra Gauge into two halves, light and shadow. Making a flank attack would fill up the guage with Light Chakra, and back attacks would fill up with Shadow Chakra. This would be true regardless of the positional requirements of the attacks themselves, but for flexibility's sake, the positional requirements on the Coeurl Form skills have to be removed to facilitate this, bare minimum. With that in mind, Deep Meditation also alters Meditation, which now essentially grants 1.5 Chakra with each use, prioritizing whichever half is lower, and picking randomly between them if they're equal. This is a buff, but it also removes the scaling factor from MNK's crit rate from the equation.

[Shurrikhan]

The problem with this change has nothing to do with how it affects the target. I have few complaints there (imo it's not enough, but the idea is appreciated). The problem is you've ignored the cost to each caster, and that's the biggest issue here. BLM needs to use a Thundercloud proc during UI in order to use Mana Shift without clipping or a major damage loss, and that's basically unavoidable without changing T3 or B4 into instant-cast spells currently. And even with that, their AF/UI rotation artificially gates the cooldown for them, meaning they will never be on par with the other two using it on cooldown.

A caster of lesser MP now sees a % increase in Mana Shift effectiveness equal to the % difference in their maximum MP. Overtime, this does mean fewer necessary Mana Shift casts. Sure, a healer could mishandle their MP to ask their casters to drain themselves even further to further enable the healer, but overall, that is a buff which stretches to the caster as well. Yes, the caster is still penalized in that mana is shifted more than (or rather than) being created (though now there is some amount of something being generated from nothing), but without that I'd have to apply balance via a longer cooldown, which increases the chance of punishment for not holding MS for a rez, or some similar factor general or job-specific.

As BLM stands to lose no long-term throughput for using Mana Shift, as compared to those with combat-rez tools, I'm not sure the .5 seconds of clipping on BLM (now mitigated proportionately to one's GCD) is so detrimental as to require a change to Mana Shift as a whole either. I use Mana Shift within 5 seconds of its coming back on CD as is without issue. Sure, there's a space of clipping after B4 or T3, but I leave UI with full MP each time despite casting it and I doubt it wouldn't be worth casting even if I didn't.

And on that note, if the explicit goal is to compete with Refresh, I have to wonder why you aren't removing Refresh's AoE component and turning it into the MP equivalent of Goad and giving it to both the Ranged and Caster DPS respectively instead. If it's just for the Foes interaction, I'd actually argue that the mana spending on it should be removed, especially given the TP/MP consolidation that's coming anyways.

Because by "compete with Refresh" I mean that a composition that forgoes a Ranged should still be capable of similar effective mana generation per minute, or, more simply, that a composition without a Ranged should be feasible. That doesn't mean that a single caster should already be able to produce roughly the same amount of mana, as needed, to what a Ranged produces through Refresh, only that it should be sufficient via whatever composition replaces the Ranged, assuming everyone's playing well. It should compete with Refresh in that it should be able to be taken in place of it, not that it should necessarily have the same value.

I may well remove the MP interaction with Foe (now Battle Voice in these suggestions, and now on Hypercharge for MCH -- each with the purpose of offering more control to the rDPS timings). I don't like it. For now, I just hated that Bard gets to double-dip from double-Ranged while Machinist gets doubly shat on, and disliked that even if they were perfectly balanced you'd pretty well have to choose one or the other just due to their CD timings, which felt somehow wrong to me in that they are considered definitively "support" dps.

I'm not sure how I'd feel about single-target MP generation. Allowing for far broader changes, I'd like it, but so long as we've only one Ranged skill with access to MP generation functionality, I don't feel like I would. Bard, especially, feels like it ought to be affecting everyone with that kind of effect. That singing isn't some form of focused telepathy. Promotion, likewise, felt like an omnidirectional emission. And while Refresh feels, aesthetically, like a poor replacement for the original skills, I still want to consider its sources and what would be expected from as close as we get to "Support" jobs.

The problem with this is MP costs don't scale with anyone's base mana. They're based on their level 0 costs (which, yes, level 0 does exist) which is multiplied by a universal modifier that grows based on their level. This formula is different from their base MP growth formula, which unfortunately grows slower than the costs themselves and is what lead to the ARR/HW Piety breakpoints in the first place. BLM hasn't had the right numbers in place because the current formulas don't allow for that kind of granularity, which just tells me that it's a leftover from 1.0. SE has since 'fixed' the breakpoint issue by making Piety only affect healers and has repeatedly tuned BLM's MP costs down in order to support their ideal rotation, and I expect them to do so again next expansion in order to account for whatever new rotation they decide on. These MP cost changes are basically meaningless within that context, though I do support the idea you were going for.

I'm aware, but I think that would be the best solution. Consider there as being an Level 0 Max MP value. It must be large enough to allow for as many fractions as you will eventually need to differentiate your spells from each other with some remainder just less than two casts of your lowest cost requisite spell (e.g. Blizzard III). From there you apply a fractional (rounded from a factor rational enough to resolve to decimal-less values every 10 increments/levels) progression per level to both spell costs and the maximal MP.

My personal hope is that they address some of BLM's clipping and mobility issues in general regardless, and there are plenty of ways to do that while retaining BLM's status as a turret DPS.

Same hope, same belief. Though, I'm sure many would argue that the clipping is just a matter of skill-gap (every oGCD but TC should be within TC and TC should only ever follow F3) and just tell me to "get gud" for thinking as much. I'd like to eventually see animation breakpoints and layers so that we can clip a bit further and more naturally (in appearance), regardless of the job, but that's probably a pipedream of a very distant end.

Contre Sixte and Fleche and the dashes are already treated as generic physical damage, and are the only abilities in RDM's kit treated as such.

My apologies; I was not aware of this. In the current version of suggestions I... might(?) want to make them Piercing too, then.

Nonetheless, to answer your question as to whether Piercing belongs in the game at all beyond DRG itself -- I'm not certain. I've been testing the removal of Piercing on Bard and Machinist as is. It depends quite specifically on how much tDPS RDM's party, all else constant, would produce if paired with a DRG vs. other jobs. If Piercing stays as stale as it is now, I'd probably side with limiting it to DRG alone.

Displacement is already notoriously awful to use in certain fights and putting more weight on finding opportunities to use it is only going to be detrimental to their damage in the long run.

I've been asking around with anyone who can so much as ponder an educated guess as to XIV's code as to whether it might be possible to use a mid-KB immunity/cancel, e.g. being able to end Elusive Jump, Displacement, and the like early. Most favor the idea that with XIV's positional unresponsiveness, such would be impossible. The alternative then would be to allow for a few different extents of movement, as I ultimately want to do for all dashes as well. For instance, holding S/<stick back> when triggering Displacement would launch you further (e.g. to the current amount), but the base length would be shorter.

In my opinion, none of the dashes should have potencies to begin with. Maybe just Corps-a-corps, but certainly not on Displacement. Shift the potency on that into Contre Sixte and Fleche, which don't have these issues.

I may well resort to that. I personally love having some reward to go pinging back and forth about the field (which is why I miss Repelling Shot potency, even if I find its removal totally understandable), but perhaps there would be a way to limit its obligatory use while still seeing similarly high potential use... Short of that, yeah, leaving it as purely a (usually really good) escape tool would be simple and effective.

(If I seem to be ignoring the obvious solution here, it's not usually because it hasn't caught my attention yet, but just because there are some things I'm weirdly comprehensive in inspecting the contexts of. This one on the other hand... equal parts bias, forgetfulness, and pipedreaming.)

I don't get why you're trying to preserve Embolden's decay by flipping it into a growth effect either. If anything, it actually makes it harder to use for the average player.

Simply put, because I enjoy that "timing tension", as do most people I've ever raided with. It would seem a disservice to the game, imo, to remove its sort of poster (or, problem) child.

Looking over any given average opener, likewise, it doesn't seem like it'd be any harder for those managing 50th percentile or better in Extreme trials or harder content. You... pop it at the start, and then basically on cooldown from there. It just happens to also sync better with your own actions. Frontloaded, aligning with TA means wasting recast time. Backloaded, it doesn't.

I like that kind of consideration and my slightest hint of an intent to trim anything like that -- strawmanned more often than not, as I do enjoy it as well -- usually lands me in very hot water.

I'll be honest, Wyrm Wave proccing off of oGCDs in general is a big problem to me. It's functionally easier to make it so he only considers your spells (or just the Ruin line, even) when making his attacks, and would go a long way to making him feel more fluid. The alternative would be to implement a pet hotbar, which I believe SE was trying to avoid in the first place.

Same story here. I will literally hear my SMN getting giddy over comms with "I've got Virus!!" when his oGCDs (purely incidental party survival tools included) are ready to go for Summon Bahamut.

Pets. Are. Garbage. And unfortunately, I can say that you didn't actually accomplish anything in that regard other than the usual signposting we get about it.

I don't doubt it. But I don't feel like I know the insides of XIV's code well enough to point out exactly which fixes should be made to make pets more responsive. Which is why I left it at "mutatis mutandi, pets be less shitty" for the time being. Obviously, Summon Bahamut himself needs far more work. He needs the standard controls and scripting, including hotbar (not to say those controls shouldn't then be improved upon; they must be). I've just been delaying to see what I can put together. Pet spell/ability/movement queuing is the most obvious general issue, but I wish I knew why they thought it okay to have it operate as it does right now. It's so bad that it feels like there has to be some absolute necessary reason... even if there's probably not. Back in ARR I'd made a plethora of suggestions offering small bits of mini-AI, increased pet movement speed only to hear "that's too complicated". I'd like to smooth them out a bit while still allowing them to be comprehensive. Sadly, most of the tools I'm used to relying on from WoW (like continuous generation or degeneration) just aren't possible in this game, and having over five times as long a delay between server polls and even less client trust certainly doesn't help. Pets are one of those areas where I wouldn't mind the risk of the occasional hacker making them damage-immune or allowing them to teleport around the arena -- as it's obvious enough in PvP for instant reporting and irrelevant in PvE so long as it doesn't actually affect their damage -- if it meant responsive checks.

Heavensward SMN was the best overall implementation of the job to date.

Their main pitfall at the time was in those nuances.

I agree that HW SMN needed button consolidation and specific changes to make using them easier back then, but not at the cost of their flow.

Agreed on all counts.

Need to head out for a bit. Will edit in the rest when I get back.

[Shurrikhan]

Given a choice, this the full list of things I would do to fix SMN:

- Aetherflow Gauge reworked. Aetherflow and Aethertrail are allowed to coexist again. Executing Aetherflow abilities still grants Aethertrail, surrounding each Aetherflow socket with a blue outline on the normal UI, and having three seperate nodes on the simplified UI to track Aethertrail.

Had been arguing for this myself for a long time, including on some threads we've both frequented. Though, iirc, I think we disagreed on how that'd best mesh with other SMN mechanics, especially DWT itself.

- Fester and Painflare reworked. Now share a cooldown of 2s. (This just tightens up Aetherflow usage in the opener without causing any issues elsewhere).

Not sure how I feel about this. The separate cooldowns gave it a sense of options in rushing expenditure, if necessary, at cost of ST/AoE potency that I actually enjoyed. I'd mostly just like to see Bane revised and also placed on a 5s CD. ...And ideally for all 3 to scale with Speed...

- Dreadwyrm Trance reworked. Now replaces Rouse via a new trait, Trance Mastery I. Increases Magic Damage Dealt by 10% for 20s. Also applies Rouse to pet, increasing healing magic potency and damage dealt by pet by 40%. While roused, pet will be immune to Stun, Sleep, Bind, and Heavy. Costs 3 Aethertrail to use, and has a 20s cooldown. (No longer prevents the execution of Aetherflow abilities while under its effects, reduces the cast time of Ruin III, or increases the potency of Tri-Bind)

I don't see why this would have any noticeable disbenefits, but it does feel like one of the less obvious or necessary consolidation choices. I'm sure this will make sense with further notes though?

- Tri-Bind Reworked: Now called Tri-Ruin. Deals unaspected damage with a potency of 60, with an MP cost of 720, the same as Bio III. (No longer inflicts Bind, but now counts as a Ruin spell for the purposes of Ruination)

The name seems a bit off, but sure, I guess? Generally, I'd like to see more CC returned to the game (along with the ability to make use of it) rather than more taken from it, but Tri-bind has always been lackluster at best to me.

- Bane Reworked: Spreads any debuffs you've inflicted on a target to nearby enemies. Potency of your damage over time effects is reduced by 20% for the second enemy, 40% for the third, and 60% for all remaining enemies. (Now spreads Tri-Disaster's third debuff in addition to Bio/Miasma III. Maximum damage drop off has effectively been doubled without changing the curve at all)

How has it been doubled? TR has only 10 potency less than TB, while Ruination spread increases that back to the full 70. Would the added 10 potency be applied before or after drop-off? At minimum, that seems like it would be equal to TB (70/56/42/28...), and if applies after: greater (70/58/46/34). Wait... what about Corruption/Radiant Flames, as well, now that they're DoTs? It does say any now, but would those be counted as yours?

- Summon Bahamut reworked. Now shares a cooldown with Dreadwyrm Trance. Increases magic damage dealt by 10% for 20s and summons Demi-Bahamut to fight by your side. Each time you use a spell on an enemy target, Demi-Bahamut will execute Wyrmwave on the same target. This action cannot be assigned to a hotbar. (Triggering from abilities removed. DWT's Damage bonus added. Deathflare, however, is not available during this period.)

Okay. I'm still worried about the loss of guaranteed instant casts, though...

- New Trait added: Trance Mastery II. Allows for the strengthening of Dreadwyrm Trance with Dreadwyrm Aether upon executing Deathflare during Dreadwyrm Trance, enabling the summoning of Demi-Bahamut. When your Dreadwyrm Aether is fully stored (2 units), Dreadwyrm Trance will change to Summon Bahamut. (Note: This results in Bahamut being summoned once every 3 minutes instead of 2.)

- That seems fine for the most part, but I don't like the even further increased resource risk from death.

- Wyrm Wave potency increased to 200. (This is there mostly to compensate for the damage nerf inside Trance, not the nerf to how often you can use it, which is an appropriate nerf, imo. Notably, as a result of the trigger changes, this ability actually gains value from from spell speed without needing a direct potency boost).

Fair enough.

- Enkindle Bahamut reworked. Shares a cooldown with Enkindle and replaces it during Dreadwyrm Trance. Cannot be assigned to a hotbar. (Sorry, less Akh Morns)

Hmm... Not sure how I feel about never seeing Inferno or Aerial Blast ever again. I think most Summoners would prefer this, though. Bigger boom. Though, it does seem like it would end up awfully redundant with Deathflare...

- Enhanced Enkindle reworked: Reduces Enkindle's cooldown to 1 minute. (Distributing the lost Akh Morn damage around to every DWT instead via this change, and removing the proc in the process, which really had no reason to exist in the first place.)

Yeah, I wasn't a fan of the proc.

- Tri-Disaster reworked. Now afflicts target with Bio III and Miasma III. If used while not under the effects of Dreadwyrm Trance or Summon Bahamut, also inflicts Ruination, increasing the potency of Ruin spells used against the target by 10 for 15s.

See, this, too, feels just a bit... off, to me. TD made sense when it applied... three debuffs. Now that there aren't three DoTs, it almost feels like it wants a third, pet-dependent effect at all times. Not sure what to make of it except that something feels lacking.

Summon Bahamut Effect: Afflicts target with Vulnerability Up, increasing all damage dealt to the target by 3% for 15s.

Do we really need more rDPS moments that aren't really noticeable or at all worth adjusting for?

Dreadwyrm Trance Effect: Afflicts target with an additional status effect depending on Egi you currently have out for 15s.
- Garuda: Increases target's magic damage taken by 10%.
- Ifrit: Increases target's physical damage taken by 5%.
- Titan: Decreases target's damage dealt by 5%.

I kind of like where you're going with this, but the thematics don't really seem to make sense, and it just moves the composition dependence from the (admittedly far clunkier, if they can't be fixed) pet skills to DWT, where that connection feels a real stretch. I do love the Bane implications, though, as that would be solidly within "any of your effects" now. I guess you could just say I've never been a fan of SMN as an rDPS bot and would prefer more visible utilities alongside more personal potency.

- Ruin I potency increased to 110.
- Ruin II potency reduced to 90. (Accounts for booksmacking at low levels and discourages overusing it for mobility. That's it).

Seems fair, though I suspect it will garner some hatred from others.

- Ruin Mastery reworked. Ruin I now grants Further Ruin I, enabling the use of Ruin III/IV. Further Ruin stacks up to 3 times.
- Ruin III reworked. Now deals unaspected damage with a potency of 200. Costs one Further Ruin stack. This cost is ignored while under effect of Dreadwyrm Trance or Summon Bahamut. (Ruin III no longer replaces Ruin I)
- Ruin IV reworked. Now deals unaspected damage with a potency of 200. Costs two Further Ruin stacks. Cost ignored while under effect of Dreadwyrm Trance or Summon Bahamut. This cost is ignored while under effect of Dreadwyrm Trance or Summon Bahamut. (Ruin IV no longer replaces Ruin II)
- Enhanced Ruin II Reworked. Now called Ruin Mastery II. Grants a 15% chance that a pet action will trigger Further Ruin I. Ruin I now grants Further Ruin II. Ruin II now grants Further Ruin I. Maximum Further Ruin stacks increased to 6.

I think I like this, though I'd want to see it for myself. I'm not too sold on taking so many keys for what don't appear distinct, either. And consuming 90-110 potency in the form of an FR stack just for an instant cast via R4 as compared to R3 seems a bit... much. I feel like this is an improvement, but not quite there?

- Contagion reworked. Now deals wind damage with a potency of 100 and inflicts wind damage over time with a potency of 100 to target for 15s.
- Radiant Shield reworked. Creates a barrier around self and nearby party members for 15s. When barrier is stuck, deals fire damage over time to striker with a potency of 30 for 9s. (This is comparatively minor damage compared to the old version, but still has a notable advantage in certain AoE situations compared to Contagion. Contagion's significantly stronger in single target situations specifically in order to help combat the extra damage Ifrit provides via auto attacks).

Does it matter that they compete over AoE / ST, though? You'll just go with whatever the composition requires, I would think? Actually, if the healers can DPS at all, wouldn't you just be stuck with Garuda at all times, given the doubly effective debuff over DWT for Magic, compared to Physical?

__________________________________________________________________________________________________________________________________________________

Personally, I don't feel the way you're altering Bard even after these changes is all that meaningful to be honest. It's not for lack of forethought on your part either. There are things I like and things I dislike. Allowing WM to store PP stacks and making Bloodletter/Rain of Death affected by Skill Speed is a nice change for sure, but the cooldown doesn't really need to go on the former at all.

You've said this before, I think? What cooldown are you referring to, though? PP has no cooldown. Or do you mean the removal of the cooldown isn't necessary? If so, again, the it's just because it helps with EA and the last 2.9 seconds of WM.

Arrow Helix sounds like an implementation nightmare and I would not wish it on any intern.

Once I finish calculations I should be able to simplify it.

Twin Bolt is fine but I question why you're doing this when Barrage exists and I don't really want to think about how that specific interaction would work.

It's stated. If you Barrage (preemptive), the original skill hits 2 extra times. If you AH after, the original hits an extra single time (postactive). As for why, I just wanted something that felt like it was offering pace and control. Being able to chain-DoT in the oGCD space or get off an extra RA or, at the very worst, get off an extra HS to trigger an RA just felt like a very efficient way to offer that. I'd gone through about four other versions prior to this, including being able to draw from Sidewinder, Barrage, or a returned Flaming Arrow (revised, for synergy with weaponskills) at partial power despite their being on CD (or, without triggering their CD). This one... felt best.

Ballad doesn't really need to be any more busy, again for the same reason.

Fair enough. I just wanted to make it more balanced against WM, which will always have the advantage of less waste, without making it more WM. I figured, it if it's going to be wasteful, why not use that as it's own gimmick, rather than merely a shortcoming?

Dissonance's numbers worry me a lot too when you factor in just how good Ballad is for AoE already.

Yeah... it might well be a bit overkill at the moment. For now I just wanted to make it so that Bard AoE wasn't entirely limited to one song. With this, WM is the slight, slight best, with MB and AP both on its tail.

Overall the fact that you'd be pressing the same two buttons inbetween GCDs regardless of song ad-nauseum is what raises the biggest red flag to me. I get the point behind the consolidation but some of it is consolidation for consolidation's sake.

I think I get your concern, but at the same time, I'm not really seeing the cause for it. I don't see what's wrong with their being an ST and AoE variant of each song's spenders. It seems to increase cohesion and the depth of the core mechanic to me.

Refulgent Arrow doesn't need to be moved to Heavy Shot either, you just need to upgrade the Heavy Shot proc so it instead reapplies Straight Shot's buff immediately and grants the current RA proc instead. RA is something the player has to decide when to use and shouldn't be moved onto your main filler button, and that buff solves the problem of putting it on Straight Shot without that much of a DPS increase to Bard overall.

But then Straight Shot would be a non-button besides the 3rd GCD. Thereafter, it'd just be maintained by spamming HS.

I'd be fine with RA being a chosen nuke skill, but so long as the mechanic works anything like its present form the only way to delay it is to waste further chances to proc of it. Compared to that, sacrificing 10 potency to Straight Shot (decoupled from RA), down from the effective 30, seems rather sane. Ideally I'd want to rework all of that so that the Crit buff from Straight Shot is something you more than maintain -- that you gamble around and prep and spend in a sort of balance of Rate vs. Depth -- and that RA can use as a full spender skill, but I can't get create yet a system for that that would be simple, deeply capable of nuance, and cohesive. Not until we can get potency-to-percentile and roll-over mechanics.

And I don't think people realize just how good stacking crit rate is on Bard in terms of affecting their overall DPS.

I mean, there are certainly scary Google Sheets tables enough detailing the impact of all-else-equal Crit to Det exchanges.
Just by the nature of the class stacking Crit creates a positive feedback loop of more procs which leads to more oGCD spam which in term gives you more chances to crit again for even more damage. Between your oGCDs and your GCDs, your GCDs do hit harder and more often, but the more crit you have the more your oGCDs are able close that gap, to the point that they can be worth almost half of your damage contribution if not equal for two of your three songs. AST and SCH are already considered the best two healers and if the former draws a naked Spear Bard is hands down the best class to throw it on. Unlike other raid buffs, these stack additively. And that works in Bard's favor in this case. If Chain/Litany are both already up on the boss giving them a Single Target Spear is more likely to beat out spreading it than any other card on any other class. DRG and SCH's buffs both sync up with the potion timer in order to 30% Crit Chance for 45s every 6 minutes and 15% crit chance, which was more than you could get at the beginning of this expansion, and when you factor in snapshotting, that bonus is available for the majority of each Ballad afterward. I believe now with the current BiS gear you only require one of these two to push over the threshold where it's better to spam Pitch Perfect on cooldown in WM, while in Ballad you're already all but guaranteed to be spamming it repeatedly.

Removing Foes feels like a missed opportunity too, namely because adding a song specialized for AoE DPS specifically over single target DPS would actually change up your song rotation based on any significant AoE phase present in the fight that you could take advantage of. Ballad is your all-around good song, Paeon is filler when nothing else is better, WM is strictly single target DPS, so adding Foes as the go-to AoE song and toning down Ballad's AoE contributions while toning up Paeon makes perfect sense.

Wait, so, you want a Foe Requiem that isn't a rDPS buff but instead some sort of AoE song or AoE augmentative bonus song? Could you describe this in a bit more detail?

Battle Voice, while handled better than Foes is currently, is unfortunately a flat out a mistake given the TP/MP merger coming in 5.0. Just make it into a standard, no nonsense raid cooldown and leave it at that.

While I hope we eventually see a more granular job resource that could play into this, true, such a suggestion will not survive the merger. Of course, we've been given very little information on what else may or may not apart from the obvious removal or replacement of Tactician, Goad, and Invigorate.

All you're really doing in effect with the Wide Volley/Grenado Shot changes is creating a needless and somewhat hidden punishment mechanism.

Yet people were glad for the option to AoE from afar despite its added cost in Heavensward. Given that it has literally no cost to implement now that we have stacked actions, I just didn't see the reason why not to return that functionality. Of course, if SE decides that Ranged don't have to be forced to be more expensive than melee or limited to the same ranges melee are then I can just replace them outright, though I'd still prefer the option of seeing both animations (and, heck, weaponskill names) based on proximity. Wide Volley looks awkward at point blank range, as does grenading yourself.

I'd be equally as fine with it if you wanted them to have the extended range period and simply replaced the original skills with them. My problem with it is they don't really add anything meaningful when it comes to their AoE rotations as it is.

That's fine by my. I don't want Bard to feel obliged to run back and forth from melee to max range between QN-WD-RoD as they did in 2.0.

There are alternative ways you could actually add them back in that actually do something other than drain TP faster.

I'm sure there are. I just hadn't come up with any entirely satisfying concepts; the old examples have all turned into examples of what not to do.

For example, Grenado Shot could be added back in on MCH specifically by using a toggle effect to alter their Single Target combo into an AoE one.

But I've just added that to Wildfire, and it seems to make more sense there. This is yet another area though where if I could do all I wanted... anything that looks like it could be an AoE would be and ST Shots across multiple targets would each be prepping Spread Shot against the same.

Wide Volley could easily be added back in while Quick Nock could be remade into an AoE version of Empyreal Arrow (Quick Nock has the better animation for being made into an oGCD, hence why I chose it over Wide Volley), existing independently from other weaponskills and having its own internal cooldown but gaining similar properties from its trait. That would help Bard's baseline proc management with minimal effect on their gameplay too.

What similar properties? And why have yet another oGCD pair, on the same timer as the original oGCD pair? And if the concern with the others is that it'd have minimal effect on their gameplay, then why is this minimal effect a good thing? I'm guessing you mean a mass-proc for instant max Repertoire stacks, as per EA-Arrow Helix? If so then you'd definitely want the Pitch Perfect CD removed, no, as not to waste it when DoTs are up?

I'm just gonna say this, when it comes to MCH, it isn't about the skill gap. Clunkiness. Is. Bad. Period.

Agreed. No matter how something "contributes" to skillgap and nuance, if it's outright clunky, it's bad.

People jumped ship from MCH because of how SE changed it in Stormblood, and while arguably it had a similar problem juggling so many cooldowns all at once in Heavensward, so did many of the other classes, and it was on a slow enough scale that it could be managed. MCH may be hard but it's not for the right reasons in Stormblood.

Again, agreed. I quite enjoyed it in HW, if a little less than Bow Mage.

Turrets should be affected by every buff except magic damage.

Agreed. I just opted to use an aura-copy from the Machinist himself because the turret disappears instantly upon your death anyways, but would have to remain out for the full duration of buffs once received to benefit full from them, where an aura-copy could be replaced.

Overdrive does not need a nerf, which by the sounds of what you've described is your intent, in order to make the skill something you only use before any downtime.

It's a buff, not a nerf... mostly. It just makes it so you don't waste buffs with Overdrive, but neither do you get the full effect of a buff for the 30 seconds worth of damage Overdrive deals off the last second of that buff. It admittedly takes the skill out of the decision somewhat, but mostly works towards increased flexibility and situational burst.

It should resummon the turret automatically after the debuff wears off, even I could see removing that penalty on it or removing the skill entirely before SE ever fixes snapshotting.

Shoot, I forgot to include that. I'm not sure what you mean by the latter clause, though. If you mean the suggestion above is impossible because of the necessity of snapshotting, note that this would still be (ratio'ed) snapshotting. 9 second left on TA would have affect 30 seconds of damage by an average of 3%. So, Overdrive's total damage would be 3% higher with 9 seconds of TA. It just also wouldn't be shit without TA, because it would now benefit from the MCH traits and anything else the MCH has on him. But alas, I may revert that too in order to maintain that skillgap element. I mostly just don't like what the interaction does to AoE on B-OD. On ST it's mostly fine.

Hypercharge does not need to be a copy of Foes. Same reasons as outlined above. The current Hypercharge is fine. Bard needs to be toned down anyways.

Bard's only parsing less than a percent tDPS over what it probably should be doing. My reasons are as described above: if possible, I'd prefer "Support" DPS not be forced into 90/120 compositions. I'd rather the unique parts of the Bard and MCH toolkits each have room to grow, rather than the decision being made solely by their CD timings.

Flamethrower will probably never get the changes you describe, because SE hates making anything tick at a rate higher than one second,

Sadly true.

and even with that I don't think the changes help with how Flamethrower is used. Right now it's the only thing that lets MCH enter overheat that's oGCD at all and I think one way you could solve the heat problem is by simply letting Flamethrower instantly put you in Overheat rather than all the awkward fiddling you did with its heat generation. Granularity does help but in a lot of ways in this case speed is the real issue.

Could you expound on this. It sounds as if there's something an oGCD can offer to Overheat more than just it's extra weaponskill within the OH window? I figured I'd just have Heat "100/100" but not actually Overheat until the first weaponskill thereafter to solve that more easily.

I would suggest reverting heat to the old system and adding heat reduction options to Gauss Round/Ricochet and potentially removing the heat generation from Clean Shot.

I'm probably going to revert to a faster heat generation system soon. I'm thinking of removing Hot Shot as a maintenance buff and instead moving into the position of a pure Heat generator. But that process would involve an almost from-scratch rework of the Heat system.

Something still needs to be done about Overheat as well but personally I hope SE actually increases the duration of Wildfire and Overheat to make them easier to use. You do this to some extent but not enough imo. The window is already super tight and anything you can do to widen it more than the bare minimum to accommodate your Rapidfire change helps high ping players out a ton specifically.

My main concern is simply that with the suggested change, you're looking at (from a base 2.5 GCD) 9.5 seconds to complete 5 GCDs of actions. At, say, a 10.5 seconds total duration (appears to be 10 seconds, making it just a pleasant surprise when the last one counts -- fair enough), you've 2 to 3 clip-spaces. At a 2.4 GCD, you've ended at 9.12 seconds, with space for the 3 clips to fit even at ~120 ms more ping. By the time you extend that to 12 seconds, though, now you're looking at another possible weaponskill within the effect, but at a far, far tighter fit. Give enough space for anyone to take advantage of and it can become obligatory. So, I'm still trying to figure out the perfect amount. And I'm not above tricking the player to make something feel better, just as GL has often done in the past, vanishing completely for a full second just to be reapplied at 3 stacks when the snapshotted effect finally reveals itself, or as AF/UI will do to a lesser degree now.

I'd argue that Hot Shot should carry the piercing debuff instead of a damage bonus and grant 50 Heat (with ammo bypassing it as usual), which eliminates that DRG dependency and the heat bonus helps with most of MCH's problems in a much better way.

50 Heat seems mechanics-destructive, but I like the idea of using it as a piercer. I guess if that were the case, Straight Shot would turn into Bard's? At that point, though, Bard would be the one enabling both MCH and DRG, lol...

Barrel Stabilizer doesn't really have a purpose outside of deaths or as a mid-cycle heat managment tool as a result of that.

Ehh, it seems decently useful to me. Rapidly returning to 30 additional potency per standard shot is awfully nice. I'm not sure what exactly I want from it yet, but I think I can make something quite useful out of it without making the system feel dependent on it.

Overheat itself really needs to be changed to only begin its timer once you've used a weaponskill at 100 heat. Reaching 100 Heat in any manner, including using Flamethrower, still puts you in that Overheated state, meaning you can't use Cooldown to exit out of it, but the timer doesn't start until you use another weaponskill. It seems unnecessary, but it would also help alleviate the currrent skill speed issue a bit as well, and if don't want to mess with the current Heat mechanics at all, I'd recommend it over any of my other suggestions precisely because it and the Flamethrower change solve most of these problems.

Heh, there we go. Agreed. And nah, that doesn't seem unnecessary or overcomplicated at all. It's a solid change, I think.

I do have some thoughts on Monk specifically, but mostly under the general opinion that positionals need rethinking on melee DPS, and it's the class that needs the most work in that regard. What I'm suggesting is relatively minor, however. I'm tossing it out mostly because of mentioning Deep Meditation earlier, as I have a proposed rework for that trait, Meditation, and a couple weaponskills. The weaponskills in question are simply the Coeurl Form single target skills. Drop the positional requirements on those, and only those.

I've got to admit, I don't much like the idea of dropping any positional requirements on Monk... I like my position-weaving, even mid colors-wheel in Suzaku.

My idea for Deep Meditation is to split up the Chakra Gauge into two halves, light and shadow. Making a flank attack would fill up the guage with Light Chakra, and back attacks would fill up with Shadow Chakra.

Oh, well in that case... It's not how I'd approach Light/Dark Chakra (which I've been raving about since the SB Monk Quests), but... hmm. Hmmm.

This would be true regardless of the positional requirements of the attacks themselves, but for flexibility's sake, the positional requirements on the Coeurl Form skills have to be removed to facilitate this, bare minimum. With that in mind, Deep Meditation also alters Meditation, which now essentially grants 1.5 Chakra with each use, prioritizing whichever half is lower, and picking randomly between them if they're equal. This is a buff, but it also removes the scaling factor from MNK's crit rate from the equation.

So let me review:
- Crit Scaling is gone. With it, RNG is gone.
- Instead it requires more hits per # of Chakra necessary for a move to compensate for the at-least-doubled bonus-potency generation rate?
- Meditation plays on this RDM-ness by feeding the less developed half. I don't wholly get what you mean by 1.5 Chakra, though, unless... each strike gives 2 Chakra and Meditation gives 3 or it's a 50% chance of a 2nd Chakra?

If a balance is required between Light and Dark, I'll be honest: I'll hate this. If not, I'd probably love it. But no matter how I think about it it does seems a bit restrictive without offering any additional nuance.

I'm still working on a rendition of Monk for the "Your job in 12 buttons or less" that centers around exactly this (Light/Dark Chakra) in addition to the elements and a significant reboot of the positionals. I'll be able to give a more vivid illustration of any of my own hopes/opinions once I finish.