AA not countering Mordo with heavy attack [Not A Bug]

Donn1Donn1 Member Posts: 48
edited January 2018 in Bugs and Known Issues
40h64c3fs4t8.png
7fsu2qfow8jx.png

Just encountered this in war, on a few occasions. Parried Mordo and used a heavy to counter his astral evade (as i have done ever since i started using AA) but this time, it didn't work and he applied degen.

Is it the node (node 42 - arc overload)?

I have always used this technique and never encountered this problem. As far as i am aware it is not the neurotoxins that counter the astral evade, but the quick succession of hits (similar to how drax counters Mordo).
Post edited by Kabam Wolf on

Comments

  • DiablosUltimateDiablosUltimate Member Posts: 1,021 ★★★
    It is definietly 2hits that counters astral evade, not neurotoxin, as it cleary states under Mordo skills that he resists any ability accuracy reduction effects.

    That said, you need to be in closest possible distance to Mordo for it to work
  • Donn1Donn1 Member Posts: 48
    DiablosUltimate wrote: »
    It is definietly 2hits that counters astral evade, not neurotoxin, as it cleary states under Mordo skills that he resists any ability accuracy reduction effects.

    That said, you need to be in closest possible distance to Mordo for it to work

    Thought so..thanks for clarifying.

    Well, i parried and then heavied - don't think i can get any closer than that! 😁
  • BreakoutBreakout Member Posts: 35 ★
    your mastery kicks in. you're getting unstopable after the auto evade
  • Donn1Donn1 Member Posts: 48
    Breakout wrote: »
    your mastery kicks in. you're getting unstopable after the auto evade

    That won't make a difference. Second screenshot shows it happening without the unstoppable. The unstoppable has happened numerous times when it's successfully prevented astral evade before.
  • Kabam WolfKabam Wolf Member Posts: 1,277 ★★★
    Hey @Donn1. Archangel ignoring Astral Evade with his Heavy was actually a Bug, and it has now been fixed. I'm sorry for any confusion that this caused for you! Since this is not a Bug, I'm going to go ahead and close out the thread. Thanks!
This discussion has been closed.