Monthly EQ Classic Ultron & Fatigue bug
Dexman1349
Member Posts: 3,060 ★★★★★
According to the buff description, "Each time the Defender Passively Evades an attack, a Fatigue Debuff is placed on the Attacker..."
However, when I fight against him with Domino and use strictly a Parry-heavy to deliberately prevent any evades, he still inflicts debuffs. He didn't evade and never had the chance to do it. Yet I still end up with 3+ Fatigue debuffs on me. Am I missing something?
If this is simply a case of him always "evading" every 7 seconds, even if my stun prevented the actual evade, then why not just have the buff description say that a Fatigue debuff is inflicted every 7 seconds?
However, when I fight against him with Domino and use strictly a Parry-heavy to deliberately prevent any evades, he still inflicts debuffs. He didn't evade and never had the chance to do it. Yet I still end up with 3+ Fatigue debuffs on me. Am I missing something?
If this is simply a case of him always "evading" every 7 seconds, even if my stun prevented the actual evade, then why not just have the buff description say that a Fatigue debuff is inflicted every 7 seconds?
3
Comments
Meaning he evades in the background and not on screen 🤣
Just trolling. It is broken AF. Nobody should evade Ghost's critical hits.
The parry-heavy method also inflicts fatigue on Star Lord.
Ultron is stunned. Did not evade. Could not evade. And I have 4 debuffs on me. Such a PITA.
So in the example of Ultron (Classic) in the new Event Quest, he gains effectively 'evade charges' every so often when he doesn't already have one. Then, the next time he is attacked, the game goes 'oh yeah we should try to make him evade' but True Strike, Slow, Stun or other abilities goes 'nope' but the node has gone 'okay the Defender tried to evade so lets put a Fatigue debuff on the Attacker now'. It might fail, but the point is that the defender TRIED and that's what triggered the Spry node.
It's really confusing me. I'll use Captain American and just heavy spam while the parry is still active and he will still get the fatigues.
Would be nice if the node description was accurate as to what exactly is happening, because as it sits now you're essentially cursed with a Fatigue every 7 seconds regardless (unless you just stand there and never try to hit him).