Book of Heroes

Riposte bug in PvP

Riposte is advertised as:
"immediately complete your current attack after dodging an enemy attack"

So my question is, when my riposte hits why does the opponent get a chance to 'defend' it?

That's happened quite a few times now. Any explanation?
I ask you this 'Why not?"

What in the tooltip information says that your attack will guaranteed hit the opponent? The cast time will complete immediately but that is it. If you were at 0.2 sec of a 2.0 sec cast then those 1.8 sec are given to you removed and the cast is complete.

If it said something like 'after dodge immediately hit your opponent with your current attack' then I would be asking the very same question.
So his hit completes and before my riposte hits he gets a chance to hit the defend button? Then riposte doesn't "immediately complete my current action." Does it?
Also, if that's the case then why don't we get a chance to hit the defend button on a justis backswing.
ABOH_O_Shinote wrote:I ask you this 'Why not?"

What in the tooltip information says that your attack will guaranteed hit the opponent? The cast time will complete immediately but that is it. If you were at 0.2 sec of a 2.0 sec cast then those 1.8 sec are given to you removed and the cast is complete.

If it said something like 'after dodge immediately hit your opponent with your current attack' then I would be asking the very same question.


Crzy is talking about 'defend' action. Re-read his thread.
I swear I read dodge not defend.

But with clarification you are referring to people's ability to use the defend ability on activation if your riposte then yes.

JasmynthTheEldest

Fri Jul 26, 2013 5:42 am
The Immediate part is from *your* perspective. Immediately after completing any action, in PvP or not, you can (must) select your next.
So the sequence is: Opponent attacks - you dodge/riposte procs - opponent selects next action - your action completes - (if they are a SW and dodge this, riposte will proc for them) - you select next action (if they are SW and riposted, their action completes) - etc.
The problem isn't with the immediate (from your perspective); it's with the proc ANNOUNCING on the dodge so your opponent is aware of the incoming blow. Better they are aware of your dodge but not sure if they are about to get riposted or not.

Think of it this way: it's coded so the sequence is ALWAYS: timer completes for one character - attacks goes out - attack land or misses - damage is applied - effects are applied (or resisted [I believe this is when Riposte and Backswing proc]) - new action is selected - turn completes and hands over sequence to timers again -
(at this point, if Riposte proced, the timer on your attack has gone to zero and your attack now goes out).

I did once get into a Riposte proc double with another SW; I dodged his, riposted out, which he dodged, and riposted back. That was was some mighty Kung-Fu. Just having it happen was almost enough to make up for the fact that he essentially tore out my heart and showed it to me... I imagine triples and higher are possible; I imagine some have happened, but not to me.

Btw, the most awesome part of riposte for me is when it triggers while I'm defending: I love getting in a reflexive strike a few hundredths of a second before an attack comes in, selecting a 0.5 second defend vs it, and then dodging it and suddenly, my defend is over and I can go back on the offensive! Instead if a "free attack" it becomes a "free defend" because I can
immediately (from my perspective) stop defending once I no longer need to!
Hopper is right, there is a problem with riposte in PvP.

If riposte hits then my action should be completed and I get to chose my next move.

At the moment it just reduces my timer to 0.00 giving the other player a chance to get an action in usually defence.

I don't have a complaint if a player blocks or dodge whatever is being riposted but they should not have a chance to use defence before it can hit.

This needs to be fixed.

japster

ModeratorFri Jul 26, 2013 8:29 am
It may or may not be a bug. Jasmynth's mechanic explanation makes sense as well.

But definitely devs should take this into account as part of balance. Also, riposte instantly ends a defend if it procs...bug or intended? Regardless, definitely another balance issue to be taken into consideration.