CheMClarc wrote:DjClericalStorm wrote:Pls explain further as to why won't an action completed by Riposte consume a WM's Arcane Shield?
Riposte is not an active ability and was not designed to remove the WM's Arcane Shield nor any other ability. Riposte was designed to help Shadow Walker's be quick on their feet while in combat and help push the timers of their longer abilities if they had a high rate of dodge.
Perhaps I'm not understanding this correctly, but shouldn't the real fix then be that a riposte out of a defend will not consume an Arcane Shield? Or was riposte itself knocking down the shield before the following attack triggered?
Maybe this is a better way of asking: If I'm issuing say a Piercing Strike now and it ripostes, will that riposted Piercing Strike consume the Arcane Shield? Or does the WM now get his Arcane Shield for two attacks really? (Because we all know that WM has the advantage over SW already, and this would really hurt a SW's chances against any WM).
Pappas_BoL wrote:Perhaps I'm not understanding this correctly, but shouldn't the real fix then be that a riposte out of a defend will not consume an Arcane Shield? Or was riposte itself knocking down the shield before the following attack triggered?
Maybe this is a better way of asking: If I'm issuing say a Piercing Strike now and it ripostes, will that riposted Piercing Strike consume the Arcane Shield? Or does the WM now get his Arcane Shield for two attacks really? (Because we all know that WM has the advantage over SW already, and this would really hurt a SW's chances against any WM).
If Piercing Strike triggers Riposte and the Mage you are fighting already has Arcane Shield up, the Shadow Walker will have to deal with the Arcane Shield. Both the Arcane Shield and Riposte abilities are passive procs that can trigger base on how many points you have in them and the actions both players take. Sometimes that situation will happen.
Illánnà_ wrote:OMFG! You didn't give us an option to stop the damn shaking? What, did you forget about that shit? Is that supposed to be part of the game where you promote a disadvantage to the user by giving them a headache? Give me a f...king break and shut that shit off!
Agree 100%. Well said. Very articulate and poised.

Casc
Pvp pisses me off cant hardley win anymore its either crummy luck super smite or snap incinerate for 20k hp.... Total bs
CheMClarc wrote:Pappas_BoL wrote:Perhaps I'm not understanding this correctly, but shouldn't the real fix then be that a riposte out of a defend will not consume an Arcane Shield? Or was riposte itself knocking down the shield before the following attack triggered?
Maybe this is a better way of asking: If I'm issuing say a Piercing Strike now and it ripostes, will that riposted Piercing Strike consume the Arcane Shield? Or does the WM now get his Arcane Shield for two attacks really? (Because we all know that WM has the advantage over SW already, and this would really hurt a SW's chances against any WM).
If Piercing Strike triggers Riposte and the Mage you are fighting already has Arcane Shield up, the Shadow Walker will have to deal with the Arcane Shield. Both the Arcane Shield and Riposte abilities are passive procs that can trigger base on how many points you have in them and the actions both players take. Sometimes that situation will happen.
I don't think many people were even aware this 'bug' existed. I never saw it in over 300 fights (ofc not all of those against WM or WM with shield). Maybe some other PvP issues could be fixed?
What about when I defend a justicar attack, I dodge said attack, riposte which nullifies my defend at 0.00, then backswing hits full-on?
What about having.. Defend an attack, dodge and riposte, then backswing hits the defend, so my defend mitigates backswing damage?
So.. Defend > dodge > backswing > riposte
Calculate the backswing BEFORE the nullified defend. Even if riposte is calculated before backswing as long as it defends.
Personally I feel backswing should be 50% (weak against walkers? Still have a good backswing chance). 75% is much too often. My dodge is at around 51 something percent, which would mean if not defending, each attack is a 37.5% chance for/of a backswing counting the main attacks, too?
Ilyana wrote:
I don't think many people were even aware this 'bug' existed. I never saw it in over 300 fights (ofc not all of those against WM or WM with shield). Maybe some other PvP issues could be fixed?
I don't even really pay attention when I PvP (purely farming) and I knew of the bug.
While I appreciate the idea of the auto-raids, it looks like the feature is a failure. Every SV, CV. and KV one I saw was failing miserably tonight. Maybe just one per every raid tier so there may be sufficient numbers. On KV, I'd recommend CK because it is a shorter raid. On CV, either KFS or VG due to essence. Advantage of KFS is ChV level players will contribute. VG is better for the people who can't handle KFS onslaught yet.
Deadlift wrote:What about when I defend a justicar attack, I dodge said attack, riposte which nullifies my defend at 0.00, then backswing hits full-on?
What about having.. Defend an attack, dodge and riposte, then backswing hits the defend, so my defend mitigates backswing damage?
So.. Defend > dodge > backswing > riposte
Calculate the backswing BEFORE the nullified defend. Even if riposte is calculated before backswing as long as it defends.
Personally I feel backswing should be 50% (weak against walkers? Still have a good backswing chance). 75% is much too often. My dodge is at around 51 something percent, which would mean if not defending, each attack is a 37.5% chance for/of a backswing counting the main attacks, too?
Please review one of your Replays that shows this interaction. You will notice that the Defend icon is still up for your character until you pick you next move. You actually defend the Backswing but you may feel like it doesn't work because of other Justicar passives that are boosting their damage in the fight.