Is the evade rate correct? I've noticed that there's an extremely high chance to evade/block/parry critical strikes like Perforate Artery.

I do not recall this being the case on live, and only once very rarely managed to get an evade on a PA on my ranger vs. assassins. I tested this in duels with another shadowblade and the two of us were evading each other's critical strikes at a really high rate (four in a row once).

What's with this? How are assassins supposed to be viable vs. archer classes in melee if we can't land our hardest hits? I had a scout actually block my PA, then evaded my both my mainhand and offhand attacks immediately afterward, slam me and volley me to death - and I hardly landed one attack even after purge.

Edit: And don't tell me viper. I don't want this post turning into another whine about how overpowered viper is. I don't have it, and I don't want it. I want to be able to win my fights in melee and with skill, not just buying an RA to win.

IMO all defense stats in this game are borked out of control.

On my warden toon I am thinking about spec'ing out of parry. Why? Because my natural unspec'd block rate with my lowly medium shield is so insane that parry seems like overkill. I'd heard other people make the same complaints/questions. Sickest tanks in the game (again IMO only) are BMs, especially shield wielding ones, defense out the wazoo.

I lump this into the same problem with resists against casters in PvE. I hate playing casters here because getting resisted 30% of the time against yellows sucks. Haven't played a caster here in RvR so I don't know if it applies, but casters even in as low as Brae have no problem killing me as I never resist (maybe all RvR resists were transferred to PvE? )

I do think that the rates are higher than they were on live - everyone specced scouts with 42 shield, for obvious reasons, but their block rate here since the block rate "fix" was implemented has been rather... er, insane.

What I'm actually getting at though is that I don't believe PA should almost ever be blocked/evaded/parried (my understanding is that the actual rate of evading one on live is very low). PAs are special attacks and I don't think they should be getting an ordinary evade rate. Vs. evade classes you almost can't land one at all. An assassin simply can't win against a friar, for example, unless they land PA, and on Uthgard the Friar will evade many PAs just like they were any other attack. This doesn't seem live-like at all.

It should not be possible to block/parry/evade a from stealth opener (assuming it was pulled off correctly).


I have a feeling, but haven't tested, that unspeccable shield skills (like wardens have) and evade1 are not capping at 5% (without any benefit of stat modifiers) as they would on live, but I haven't done any testing to prove this is the case.

moved to support

Foremost, it would be interesting to know which impacts the combination of wielded weapon and weaponskill has on a specific type of defense on this server.

Example: According to the formulas, how does high weapon skill increase your chance to get through the enemies shield, and what difference does it make if you wield 2 weapons in comparison to a 2handed weapons.

Btw .. the unspeccable shield skill that supporters have is definitely not capped at 5%. Duelling with my Valewalker against a buffed Bard showed unreasonably high block rates. Against someone who is able to spec shield skill it becomes nearly impossible

PA/backstab on live cannot be parried/evaded/blocked. A failed one can be parried/evaded/blocked.

keitz wrote:PA/backstab on live cannot be parried/evaded/blocked. A failed one can be parried/evaded/blocked.

a fix has been made in the changelog should be fixed now so no further discussion is needed..

if there is more issues please feel free to open another topic

reopened

i have also noticed that sometimes my PA would be evaded/blocked/parried

and even on my friar i would evade them sometimes

but the change log seems to have fixed that

toaky wrote:but the change log seems to have fixed that

Are you sure? I posted this after the changelog message (16.01). What prompted it was someone evading a PA, yet again (not a missed PA, mind you, one that would have hit).

keitz wrote:PA/backstab on live cannot be parried/evaded/blocked. A failed one can be parried/evaded/blocked.

Who told you that? it's rare but it happened on Live , at least to me a couple of times. if you play a shield class u have the same chances to block a PA like you would block any hit.. question is..how many times playing daoc u get PA ed? not too many doing rvr..but go on a pvp server on live where you will have the chance to fight stealthers at every 1 min and a half.
No right minded stealther should PA a shield tank imo..they could get blocked:P.

ya i never seen any info about CS stealth styles bypassing defenses like evade/parry/block. If you choose to PA , your also choosing to deal with the chance to have it evaded/parryed/ or blocked. If you dont like that chance, do a BS instead. Same goes with anyone, if you want to get past defenses, you need not be infront of them. Unless you can find proof on the herald or else where. Im suprised such a topic with no proof, gets a bug fix so soon. I wonder why.

Eclipsed wrote:ya i never seen any info about CS stealth styles bypassing defenses like evade/parry/block. If you choose to PA , your also choosing to deal with the chance to have it evaded/parryed/ or blocked. If you dont like that chance, do a BS instead. Same goes with anyone, if you want to get past defenses, you need not be infront of them. Unless you can find proof on the herald or else where.

Wrong. Critical strikes are special attacks. PA, for example, is a fixed amount of damage and you can PA with an Alchemist's Billhook and do the same amount of damage as anything else.

PA is only rarely supposed to be evaded, not evaded at the rate that ordinary attacks are.

And backstab does not get around that mechanism either. Evade for assassins is a 360 degree mechanism.


Edit:

Eclipsed wrote:Im suprised such a topic with no proof, gets a bug fix so soon. I wonder why.

IT DID NOT GET FIXED. The post was closed in error due to an unrelated patch note.