I find it hard to believe Retaliation is working as intended…
WARRIOR VS. WARRIOR
-Retaliation counterattacks themselves will trigger infinite other Retaliation counterattacks, and also at infinite rates
I never touch the warrior or even target him. Infinite counterattack feedback loops occur simply when the enemy Warrior uses Mortal Strike while we both have Retaliation active.
Retaliation: “Instantly counterattack any enemy that strikes you in melee”, but a Retaliation counterattack counts as “an enemy that strikes you in melee.” And seemingly with no internal CD or inner workings whatsoever.
This is the respective combat log for anyone who cares enough.
How can this be intentional??
1 Like
Psure this is how it always worked and it makes sense how it can create an infinite feedback loop in a mirror
Retal itself was designed w/ no icd
Not just mirror comps, but any 1v1 Warrior duel (in arena) is capable of doing ~30k dmg in well under one second. I haven’t found one video or any forum post talking about this Retal bug prior to WotLK Classic Beta.
Every video I have seen show two Warriors beating into each other when they pop Retal & that makes more sense regarding infinite feedback loops because they are both melee attacking.
However, in my situation, I never targeted or even hit the enemy Warrior (other than what my Retal did). We both pop Retal, he casts one single Mortal Strike. Our Retal counterattacks begin their loop, & all either of us can do is pray to RNG? There is 100% guaranteed something definitely wrong with this.
The problem here is that Retal counterattacks are instantly, and infinitely looping off of themselves (until 0 stacks or death). Originally, you needed to have someone melee attacking you for Retal to work. But now since WotLK apparently, Retaliation counterattacks count as a “melee attack”, even if I didn’t hit the Warrior or target him to begin with.
1 Like
I understand it is warrior vs warrior obviously
Do you have any link to an old video where two warriors popped retal and didn’t have this interaction occur
Sorry for that I’m just trying to make everything as clear as possible because this really confuses me.
I’ve been looking for one all day, & just now found a video from Swifty in OG TBC:
Start video at 4:22
This interaction is not similar to current WotLK Classic at all.
The second they both Retal, infinite feedback loops should instantly drop both of their Retal stacks to 0, but they aren’t. They both have Retal up & once the other Warrior begins Bladestorming is when the heavy damage comes in. But that makes sense because they are melee attacking each other non-stop through the Retaliation.
Their Retaliation counterattacks are not proccing each other’s Retaliation counterattacks. Or if they are, it’s limited to not feedback loop infinitely & instantly until 0 stacks or death. But that is how it works in LK Classic right now. Don’t get me wrong, they do take a lot of damage very quickly in this clip, but it is very technically different from the OP video. It is also nothing compared to how this interaction behaves in current LK Classic as far as the damage output.
1 Like
Still scratching my head on this one anyone else got more information as to what is going on here? @Blizzard
I noticed the same thing in arena this past week. This absolutely feels like a bug. I went from 70% hp to zero when I popped retaliation, and then the other warrior popped it. He took damage, but no where near what I took. I thought perhaps it was because he popped it second, I wasn’t sure, so in another fight the warrior popped retaliation, so then I popped it and hit him with mortal strike, and I still ended up taking the brunt of the dmg.
This has to be a bug! At this point, I just avoid using retaliation altogether in mirror fights. I hope Blizzard can address this, however, I feel like they rarely pay attention to these forums anymore.
1 Like
UPDATE: Since Blizzard (and most people) refuse to acknowledge this as a bug, here are two examples of this feedback loop being exploited:
Have fun and try this in-game because this is definitely working as intended 
