Renewed Request - Please Delete Parry from the game

[Aaliyahrose]

At the very least I would like that Parry on PLD would directly translate into Block...
Its pretty annoying that one uses Sheltron, and the next 10 seconds worth of autoattacks get all parried, so no Shield Swipe proc :/

Also, would be cool to have a "Parry Stance" in which neither GCDs nor Auto-Attacks or moving at all can go, but naturally reduces incoming damage, stackable with other DEF cooldowns and the more Parry you have, the longer it can last on, and endure.

PLD can Block without Sheltron already. It's about 6% or 9% stronger than parry if I'm not mistaken. It just depends on what kind of shield the PLD has that judges how often they block attacks. Depending on the strength of the shield the block rate is less.
I think the Shield types are:

Buckler - High Block Rate / Low Block Strength
Kite Shield - Medium Block Rate / Medium Block Strength
Tower Shield - Low Block Rate / High Block Strength

[Violette]

You could also conceivably stack them for Bismarck and Ravana, though I'm not sure how much elemental-aspected damage there is to those fights (never tried using elem. resist stuff).

They were important back in 1.xx for Ifrit/Garuda at the start.
A lot of bismarck's damage comes from physical (the platform change) and the adds, so useless there.

Ravana has a lot of physical as well (slashes, charges, etc).

RIP elemental materia.

[Mirch]

parry is cool

[Arkenne]

PLD can Block without Sheltron already.

hrm... nope thats not what I meant...

Tis true that Block "can" happen with every fisical attack the PLD takes from the front, however parry does also (and evasion, but lets ignore that).
One attack from the front has a % chance to be blocked, and a % chance to be parried.
But if the one attack is parried, it can't be blocked, and if said attack is blocked, it can't be parried (and evaded but Im disregarding that).

They both are competing against the other, and in the case of the PLD, you want the Block to happen instead of Parry.
So then it comes Sheltron into play. Since Sheltron makes it a 100% chance that the next attack is blocked, its nice and all but, parry takes priority (along with evasion but Im disregarding that).

For a hit to be blocked by Sheltron, it must first bypass the parry parameter, if parry happens, sheltron isn't used and has to wait till the next chance. Hence Sheltron isn't really a 100% block chance, rather a (100 - parry % - evasion %) % chance to happen. and if the other wins over in the duration... bye bye Sheltron, GG Shield Swipe.

So in terms of DPS, Parry is actually a DPS loss for the PLD, and in terms of tanking, Parry is in the way of Block, specially since both work under the same conditions.

So thats why I would wish for Parry to translate into a greater Block rate, nullifying the Parry parameter altogether for the PLD.
Or that Sheltron would nullify both Parry and Evasion chance until proc :/

[Ashkendor]

My post reduces more damage then parry does.

That's debatable. Your arguments are usually so full of holes that you could drive a herd of cattle through them.

Your posts cause more facepalming than parry does for sure, though.

[Fytayn]

So... I've been looking through Parry-related posts as I was wondering how it actually affected things.

All I see on here is "it's useless/useful due to [insert theorycraft/opinion/story here]"

I've seen all kinds of analysis and numbers regarding other stats but absolutely nothing about Parry beyond what people seem to be making up. And this isn't just here.

So, question to the assembled: has anyone actually figured out the numbers behind Parry since the 3.0 changes? Without anything resembling those we're all just guessing.

[Syzygian]

So... I've been looking through Parry-related posts as I was wondering how it actually affected things.

All I see on here is "it's useless/useful due to [insert theorycraft/opinion/story here]"

I've seen all kinds of analysis and numbers regarding other stats but absolutely nothing about Parry beyond what people seem to be making up. And this isn't just here.

So, question to the assembled: has anyone actually figured out the numbers behind Parry since the 3.0 changes? Without anything resembling those we're all just guessing.

There was a thread of some people trying to do objective research on scaling. iirc it does not scale the same as it did pre-3.0. But people hate/don't care about the stat so much that a lot less effort was put into math behind it this time around. I believe the same thread also suggested, based on testing, that WAR and DRK have higher base parry rates than PLD does, DRK even more so, (probably to balance with Wrath stacks having Parry). The big take-home from that was that PLD having a Shield was shaping up to not actually make much of a difference in passive mitigation between the other two tanks, as the tests suggested they had innately higher parry rates to compensate.

[Syzygian]

OH SHI--- (sorry for double post) --

Here it is.

[Nektulos-Tuor]

That's debatable. Your arguments are usually so full of holes that you could drive a herd of cattle through them.

Your posts cause more facepalming than parry does for sure, though.

I don't know, parry is full of holes itself.

[Stiggie]

They could make Parry a very interesting stat, I've heard everything from adding a chance to counter-attack to it, or just make auto-attack damage more of a threat. These are good suggestions, but it doesn't make it an interesting stat.

I think that the devs are actually very close to making it an interesting stat through replicating the mechanics of one move: Reprisal. What I would propose is an ability off the GCD, with no cooldown, that procs from a parry, that would give some sort of buff. You could even make them unique for each class, for example, PLD would get a mini-bulwark for X seconds or proc a small aoe heal, WAR could get a stack of whatever stance they are in, and DRK could gain a lifesteal or a short blood weapon(in grit) for X seconds. I'm not saying they'd have to do this, but it would make parry much more viable in the MT position.