Parry vs Well timed block

UndividedPuma

So I’ve been playing with Blade for a bit now, and I’m trying to figure out why a well timed block does not always equal a parry. I’ve had many instances of triggering a bleed with Blades well timed block but no parry stun? Isn’t a well timed block a parry if you have the mastery?? Is this a bug?

HugsForEveryone

UndividedPuma wrote: »

So I’ve been playing with Blade for a bit now, and I’m trying to figure out why a well timed block does not always equal a parry. I’ve had many instances of triggering a bleed with Blades well timed block but no parry stun? Isn’t a well timed block a parry if you have the mastery?? Is this a bug?

Blade and nebula are both having this issue I believe one of the mods addressed it by saying the well timed block mechanic and the parry mechanics were off by a few fractions of a second there’s a thread about it somewhere on the forums you gotta search for it though

Horror_punk

"Well timed block" is the dictionary meaning of parry
But apparently PARRY is broken guys and they making huge cash of this bug, story quests of Act 5.3 will eats up all pots and units because champs can't parry opponents and block damage is insane in those quests
Opponents are having 6k attack and higher

UndividedPuma

Yeah I’ve felt like parry was off. It was made pretty clear when I was using Blade and now that you mention it, it did happen with Nebula. Passed the shock to the opponent but no parry.

ForumGuy

It's because parry is bugged. Don't expect a fix soon though. Just enjoy that new content with the thor quests to distract us.

D_S_

Pretty much

CRE4TOR

Mephesto is having the same issues on this as nebula and blade. A parry and well timed block are the same thing, so if one happens, the other should too.

Mephesto’s aura of incineration doesn’t always proc on a parry, and procs on a block but doesn’t cause parry.... kind of funny, but it shouldn’t be bugged like this.

D_S_

Parry is worse after 16.0 update. But kabam will never acknowledge it