#FFXIVHEALERSTRIKE

[TheDustyOne]

It'll never not be funny when people talk about who the dev team listens to.

EN players will say that they should stop listening exclusively to JP.
JP players will say that the dev team listens to the west too much.

The answer is very likely that they don't listen to anyone except their internal team and their metrics.

I'm going with this; Samurai lost Kaiten despite having no complaints, Viper lost Noxious Gnash despite no one complaining about that, and I'm still trying to decipher where they got complaints about Dragoons Nastrond stacks. The only thing I can think of is that the complaints are from internal testers thinking that "someone might find this difficult, so lets fix it early" rather than just leaving the job be and letting people get used to it.

[Calysto]

Nice, with 7.1 there is less need for piety now ; what a relief !
First step in putting holy in line with the others AoEs too !
I can't wait to see what amazing upgrade they can bring to this thread next !

Keep up the good work here ^^
/cheer

edit :

I'm going with this; Samurai lost Kaiten despite having no complaints, Viper lost Noxious Gnash despite no one complaining about that, and I'm still trying to decipher where they got complaints about Dragoons Nastrond stacks. The only thing I can think of is that the complaints are from internal testers thinking that "someone might find this difficult, so lets fix it early" rather than just leaving the job be and letting people get used to it.

It all makes sense If they base it on their trust-bot tester AI , it probably can't do that many apm

[ForsakenRoe]

I'm going with this; Samurai lost Kaiten despite having no complaints, Viper lost Noxious Gnash despite no one complaining about that, and I'm still trying to decipher where they got complaints about Dragoons Nastrond stacks. The only thing I can think of is that the complaints are from internal testers thinking that "someone might find this difficult, so lets fix it early" rather than just leaving the job be and letting people get used to it.

My theory for DRG is that they had the idea of 'hey DRG is too busy, let's remove Spineshatter cos it's kinda low-excitement as an ability and contributes 2 APM to the opener/burst', which is fine on its own, but then they added Rise of the Dragon/Starcross and instantly invalidated that removal by adding 2 APM to the opener/burst again. So now they've gone and removed 2 Nastronds to get the APM to where it was meant to be in the first place.

If that's how it went down, the lack of foresight (that adding 2 new OGCD actions would impact APM) is hilarious. If it's not that, then it's just a very strange decision, given that it required buffing Nastrond/Stardiver/Starcross to make them even higher potency to compensate for the two lost Nastronds, which means more super-high potency skills that can be subject to Crit Variance. At least with DRG their burst window includes a Crit Rate increase to slightly alleviate that problem

[Maltothoris]

it also seems that they really banking on ultimate for the use of esuna cause I remember a certain user here saying along the lines of "Esuna will be most likely be needed to be used more" and now that we have both the new content, that isn't quite the case really. Only maybe in Jade Stoa if you get hit by the ground exaflares but that's really it. Not the new dungeon or the new alliance raid.

[Kes13a]

it also seems that they really banking on ultimate for the use of esuna cause I remember a certain user here saying along the lines of "Esuna will be most likely be needed to be used more" and now that we have both the new content, that isn't quite the case really. Only maybe in Jade Stoa if you get hit by the ground exaflares but that's really it. Not the new dungeon or the new alliance raid.

with the new alliance raid it would have made sense there since its now instant... and that raid is very busy, wouldnt have much time to stand in spot and cast it

[Maltothoris]

Also look at how prevalent that MTTT is starting to become. First we had M1S with raining cats and now we have the ice phase in ex3. Heck even the stack that tries to force the swap with the tethers can still easily be ignored with invulns and of course we have reject authority.

[BunnyQueen]

They need to go back and adjust all dungeons level sync, hard sync all stats, boost standard damage, make more damage unavoidable. Boom both tank and healer are more engaging.

[KageTokage]

It's awkward that I felt more satisfied healing Byakko unreal then any of the current savage fights simply because you're actually allowed to cover for mistakes due to virtually none of the mechanics being immediately lethal and you can potentially survive things like the expanding AoEs overlapping, too few people in stack markers, or the add being too healthy by layering mitigation and timing heals.

Granted, the fight is easier as a consequence but it made me actually feel like I was playing my role better.

[AmiableApkallu]

They need to go back and adjust all dungeons level sync, hard sync all stats, boost standard damage, make more damage unavoidable. Boom both tank and healer are more engaging.

It's not only the quantity of damage that could do with some tweaking. It's also the pacing.

Predictable damage can provide only so much engagement. Predictable means it eventually becomes rote.

Crit autos need to make a come back. Random chip damage to random party members. Non-fatal mechanics where the likely outcome is that people avoid some but not all of the outgoing damage. Etc.

[Aravell]

The thing is, "balance so every job is viable" is a giant lie. The reason some jobs are not viable in certain fights in the first place is because of the move towards rigidity over flexibility.

Back in HW, if we had extended movement phases, BRD can choose to drop Minuet or spam Feint for less of a damage loss than simply not attacking. Even as recently as in EW, standard BLM rotation was said to be garbage for TOP p6, so BLM players worked around it with alternate lines.

The reason we have jobs that suck in certain fights rests squarely on the fact that the dev team forced every job into only one correct way of playing, there's no flexibility, there's no creativity, the job either sucks for that fight or it doesn't, so they try and "solve" this problem of their own creation by making the jobs that suck more like the jobs that don't suck.