Requesting Data for Parry RATE (not amount mitigated)

[Docfiord_Fowling]

...

I'm making an assumption here that the first 354 parry (baseline) do not scale the same as any additional parr; this was the case with skill speed as well. Also, it shouldn't hurt the results as you are examining the amount of rate added from the amount of parry added.

[Hundred]

If you have more evades then parries, something goofed (Blind on Flash from PLD?).
Enemies lower level then you are likely to have less accuracy and so sub 60 mobs will likely miss more.
Evades likely take priority over Parries as well so you would cause more hits to go through the evade check before the parry check (Can ACT tell if an evaded hit would be parried or is it just doing Parries/Swings?).

The closer a mob is to your level (ideally 60) the greater the likelihood its accuracy will cause it to hit more often and thus reduce the amount of evades.

[Habien]

If you have more evades then parries, something goofed (Blind on Flash from PLD?).
Enemies lower level then you are likely to have less accuracy and so sub 60 mobs will likely miss more.
Evades likely take priority over Parries as well so you would cause more hits to go through the evade check before the parry check (maybe this is why ACT is off? Can it tell if an evaded hit would be parried?).

The closer a mob is to your level (ideally 60) the greater the likelihood its accuracy will cause it to hit more often and thus reduce the amount of evades.

The parry % is off in ACT because it counts the #parries/#swings, rather than #parry/#hits. If miss/avoids take priority over block/parry, then finding the parry-% given the mob hit you might be more important.

[Tam_Hawkins]

If you have more evades then parries, something goofed (Blind on Flash from PLD?).
Enemies lower level then you are likely to have less accuracy and so sub 60 mobs will likely miss more.
Evades likely take priority over Parries as well so you would cause more hits to go through the evade check before the parry check (Can ACT tell if an evaded hit would be parried or is it just doing Parries/Swings?).

The closer a mob is to your level (ideally 60) the greater the likelihood its accuracy will cause it to hit more often and thus reduce the amount of evades.

Currently sitting at 701 swings, 75 misses, 142 parries, 20% parry PCT (22.5% Parries/hits)
with 734 parry and still getting slapped in the face.

I know that evade has priority over parry and i doubt the game still calculates parry if the hit is evaded or blocked also I have already calculated for the misses.
One question, were you in defiance while taking These numbers?
Alsomay I ask how you get to 734 parry?( base is 354 for Paladin at least, that would mean you got 380 parry in Addition wihcis quit a lot)

Edit: almost forgot, no Flash used of course, and Evasion was always somewhere between 10-15% until now (for lvl59mobs), as parry starts at 10% it is not uncommon to have more evasion

[Hundred]

One question, were you in defiance while taking These numbers?
Alsomay I ask how you get to 734 parry?( base is 354 for Paladin at least, that would mean you got 380 parry in Addition wihcis quit a lot)

No Im using a Drk for this.


I got 734 Parry by switching everything I saw didnt have Parry on it with stuff that had Parry on it (which caused me to forget the 190 gloves as I had the 170 on my Drks set). Realizing I had no Parry earring but some stray level 29 piece with +3 parry on it since I scrapped the Valerian I went and bought a pvp earring. Its actually not the most I could get given I had forgotten to sync my i190 gloves to my Drks equipset. Even still you can technically reach higher Parry then this if you *really* wanted to

My Drk's entire gear seat for this was
i180 Weapon + 74 Parry
i160 Helm (valerian) + 35
i148 Coat (Sharlayan) + 36
i170 Gloves + 39 (would have been +47 if I remembered my gordian gloves)
i142 waist + 23
i170 legs + 44
i148 boots + 32
i190 Necklace + 20
i55 pvp earring (lol) + 9
i170 bracelet +20
i115 ring +20
i136 ring + 23.

Adds up to 734. many of these pieces could have been replaced for more Parry (or remembering my gloves). Prototype Gordian Chest can't be gotten yet due to the week lock out, but is a straight upgrade of 18 Parry over the Body Piece I used for instance (or hell just using Ironworks piece for now).

With my gordian gloves and a valerian earring I could reach 759 with that set-up, if I put on augmented Ironworks chest instead I'd reach 770. Augmented ironwork ring is better then the i115 quest ring I used, blah blah.

If there was a full i190 set with Parry on it the stat weights would probably put it at 800+ Parry no problem but square doesn't release gear sets like that.

[Tam_Hawkins]

No Im using a Drk for this.


I got 734 Parry by switching everything I saw didnt have Parry on it with stuff that had Parry on it (which caused me to forget the 190 gloves as I had the 170 on my Drks set). Realizing I had no Parry earring but some stray level 29 piece with +3 parry on it since I scrapped the Valerian I went and bought a pvp earring. Its actually not the most I could get given I had forgotten to sync my i190 gloves to my Drks equipset. Even still you can technically reach higher Parry then this if you *really* wanted to

My Drk's entire gear seat for this was
i180 Weapon + 74 Parry
i160 Helm (valerian) + 35
i148 Coat (Sharlayan) + 36
i170 Gloves + 39 (would have been +47 if I remembered my gordian gloves)
i142 waist + 23
i170 legs + 44
i148 boots + 32
i190 Necklace + 20
i55 pvp earring (lol) + 9
i170 bracelet +20
i115 ring +20
i136 ring + 23.

Adds up to 734. several of these pieces could have been replaced for more Parry (or remembering my gloves). Prototype Gordian Chest can't be gotten yet due to the week lock out, but is a straight upgrade of 18 Parry over the Body Piece I used for instance (or hell just using Ironworks piece for now).

thanks for that^^
if we use your numbers and simple lock how much parry we get per Point (minus the 10% for the base stat)
we would be at 30,4 Points of parry per % which is quit a bit lower then what I got so maybe we don't have a linear scaling anymore (but ist to soon to be sure, just a thought) eitherway more testing is necessary i think.

[Hundred]

Final crap.
734 Parry.
Monster: Sphinx level 60
Hits: 1001.
Misses: 114
Swings: 1,115.
Parry: 221
Parrypct: 20%.
Parry% (Parry/hit): 22% (truncated)

[Disc]

Kalos our results are extremly different and like me you did not Count the misses nor did you use your shield so i do not think that there is anything wrong with how you did your Experiment. Do you think limiting our numbers to roughly 1000 hits (because i also Chose this amount of hits) is not enough?

There are a few possible factors. 1,000 is definitely too small of a sample size. I'm coming up on 4,000 & so far results don't change by more than 0.01% every 10 minutes, so that will probably be enough.

The job being used will also make a difference. I was originally going off previous assumptions that block rate is what caused PLD to have half the parry rate of WAR/DRK, but I'm still sitting at about half of what they report. It would be nice to have a collective over 10,000 hits at base parry for each tank.(no shield) Will also need to see the math behind the parry rates being reported as far as Swing/Hit/Miss/Parry/Block go.

If you have more evades then parries, something goofed (Blind on Flash from PLD?).
Enemies lower level then you are likely to have less accuracy and so sub 60 mobs will likely miss more.
Evades likely take priority over Parries as well so you would cause more hits to go through the evade check before the parry check (Can ACT tell if an evaded hit would be parried or is it just doing Parries/Swings?).

The closer a mob is to your level (ideally 60) the greater the likelihood its accuracy will cause it to hit more often and thus reduce the amount of evades.

Number of misses will not matter as long as your report Swing/Hit/Miss/Parry/Block & divide your parry by the number of hits to get the rate, assuming no shield equipped on PLDs.

[Tam_Hawkins]

There are a few possible factors. 1,000 is definitely too small of a sample size. I'm coming up on 4,000 & so far results don't change by more than 0.01% every 10 minutes, so that will probably be enough.

The job being used will also make a difference. I was originally going off previous assumptions that block rate is what caused PLD to have half the parry rate of WAR/DRK, but I'm still sitting at about half of what they report. It would be nice to have a collective over 10,000 hits at base parry for each tank.(no shield) Will also need to see the math behind the parry rates being reported as far as Swing/Hit/Miss/Parry/Block go.

Yeah i wanted to do 10000 first but run out of ptience... maybe tomorrow... (yeah MAYBE....)
I don't think shield changes that much (blockrate would Need to be 50% for that)
I will add the swing and hit numbers naxt time (first time doing this so had no idea how to parse them (i needed one hour already to figure out how to put evaded hits on the window,,,)

[Disc]

Parry rate hasn't changed in the last thousand hits, so just going to cut short of 10k hits and throw this up now.

Lv 60 Paladin - 354 Parry(Base)
Tsanahale: 6532 Swings, 6019 Hits, 513 Misses, 353 Parries, 0 Blocks(no shield)
(353 Parries / 6019 Hits) * 100 = 5.865% Base Parry Rate

Will throw on parry gear and find definitive results for +102. See if my chicken can handle healing multiple enemies to speed this up.