Give Physical Ranged Dps knockback nullify ability

[Kabzy]

But when twelve jobs have ways of completely negating a mechanic, and of the remaining three, one has a gap closer, I think it's fair for BRD/MCH to claim they want it too.

By those standards, each of the twelve jobs should also get complete mobility and near 100% DPS uptime in all situations. Your own argument can be thrown back at you, BRD/MCH already have a huge advantage with mobility. Also it should be pointed out that not all jobs can negate all movement based mechanics. A PLD, for example, cannot use Tempered Will on both pushbacks on Exdeath.

[Bourne_Endeavor]

By those standards, each of the twelve jobs should also get complete mobility and near 100% DPS uptime in all situations. Your own argument can be thrown back at you, BRD/MCH already have a huge advantage with mobility. Also it should be pointed out that not all jobs can negate all movement based mechanics. A PLD, for example, cannot use Tempered Will on both pushbacks on Exdeath.

Those aren't the same standards though. If we're going to use the mobility standard, why did Surecast get changed? Casters have near 100% uptime yet weren't told to "suck it up." At this point, it isn't even about damage but more an annoyance. Is it necessary? No. At best it would be a QoL change.

[Dualgunner]

By those standards, each of the twelve jobs should also get complete mobility and near 100% DPS uptime in all situations. Your own argument can be thrown back at you, BRD/MCH already have a huge advantage with mobility. Also it should be pointed out that not all jobs can negate all movement based mechanics. A PLD, for example, cannot use Tempered Will on both pushbacks on Exdeath.

It'd be a different argument if say, only Dragoon and Black Mage could cheese it due to Jumps and AM.

"Everyone else has something, phys ranged should have something too" and "Only two jobs have something, everybody else should have that something" are completely different arguments and one can't be used to negate the other.

What I do know is our bard is the only person in my static who gets blown back by every vacuum wave, and the only person who has no direct answer for Tidal Wave. It's an annoyance for the whole party to have to accommodate for. Does it break the game? Not at all--but that doesn't mean it's not annoying.

[kikix12]

Those aren't the same standards though. If we're going to use the mobility standard, why did Surecast get changed? Casters have near 100% uptime yet weren't told to "suck it up." At this point, it isn't even about damage but more an annoyance. Is it necessary? No. At best it would be a QoL change.

Eh...casters have cast times, so they lose attacks if they have to dodge...Bards and machinists can attack on the move, whenever and wherever they appear to, even if they'd have to run in circles all the time. Casters, even red mages, cannot do that (unless we'll count the instant-cast spells that are very weak and tend to be costly...if the caster does have them).

There is no class that have anywhere near bards and machinists mobility. There's a knockback?! And?! Bards and machinists don't lose anything at all from actually going to the right point to make it irrelevant (alright, you cannot actually use skills during the sliding). Every other class does. If there's a knockback that pushes so far as to make the player out of range even on bard/machinist, then gap closers which are HALF of their range are just pitiful, so even Dark Knights lack any means of dealing with it.

All in all, other classes get actual performance from anti-knockback (and even then, except for Surecast, those skills have unnecessarily high cooldown). It's only quality of life skill for bards/machinists, with no actual change in anything (heck, if used at the wrong time, the short animation lock can actually lower their performance...by too little to be relevant).

[HyoMinPark]

snip

When you’re speaking from a damage standpoint, then fine. Don’t give it to BRD/MCH. But considering that twelve other jobs can just completely ignore an annoying mechanic, and BRD/MCH just have to deal with it...well, I’d appreciate the QoL change. I don’t really like having to beg the PLD in V4S to cover me; which most don’t even do. It’s an annoyance, and I’d like to have a chance to ignore said annoyance like nearly every other job can.

I mean, they changed Surecast to allow casters to continue casting while it’s active because casters complained about losing the GCD prior. QoL. Why can’t BRD/MCH have a QoL? Maybe they could make one of the Graze skills actually useful by adding a knockback nullification to it; since most of the Graze abilities are completely worthless in most, if not all, content.

[Soupa]

Give ranged dps a knockback enhancement so they'll fly twice as far as everyone else. Challenge mode engaged.

[Vivi_Bushido]

"Everyone else has something, phys ranged should have something too" and "Only two jobs have something, everybody else should have that something" are completely different arguments and one can't be used to negate the other.

What I do know is our bard is the only person in my static who gets blown back by every vacuum wave, and the only person who has no direct answer for Tidal Wave. It's an annoyance for the whole party to have to accommodate for. Does it break the game? Not at all--but that doesn't mean it's not annoying.

Agreed 100%

They're two completely different arguments and is purely a QoL add on, not a game changing feature.

[AkashiXI]

If he does Void Thunder III. If he doesn’t, then melee are in luck. BRD/MCH lose a GCD for each Vacuum Wave each time because you aren’t skipping that. Especially if you don’t have a PLD to use Cover/Tempered Will, which many I have to actually ask for that, and it’s only up for one Vacuum Wave.

It’s not like BRD/MCH do as much damage as a melee of the same/equal skill as them, so giving them a knockback nullifier isn’t going to automatically make them “OP”.

I don’t think Bard or Machinist need a knock back prevention tool, the situations are way too sparse to justify it. In terms of your example, both healers can rescue a range on each vacuum wave, and like you said, Paladin has cover. Even if both parties refuse to help you, our massive convenience of pew pew’ing outweighs our inability to prevent push back :V

[Vivi_Bushido]

I don’t think Bard or Machinist need a knock back prevention tool, the situations are way too sparse to justify it. In terms of your example, both healers can rescue a range on each vacuum wave, and like you said, Paladin has cover. Even if both parties refuse to help you, our massive convenience of pew pew’ing outweighs our inability to prevent push back :V

I see those at more inconveniences for those jobs tbh. It gives them extra responsibilities that range dps could solve with a single button press like any other job. In addition, healers would have to sacrifice their already extremely tight tool kit of cross role skills to babysit the range dps. And if there's two range dps, then one of them is out of luck. Giving range a knockback prevention would not only be a QoL for the range dps but also so the other jobs wouldn't have to hold their hand on annoying mechanics.

[Valkyrie_Lenneth]

Bring back bowcasters and then give them knockback prevention :P