6.2.6 Champion Bug

While attempting the Champion fight in 6.2.6 again as it has plagued me for some time, I went in with a few champions that worked well to get me to the last phase the last time I fought him. One champion in particular, Spider-Gwen, was quite useful in preventing the Champion’s unstoppable buff from triggering with her slow debuff on her heavy attack. Now normally, this prevents the buff from triggering at all, however, on this previous attempt that was not the case. It still acted as if the unstoppable buff was not there so I could hit the Champion. However, on this particular fight, the regen associated with the unstoppable buff being triggered was still active making a great part of the strategy null and void. Is this how the interaction is intended or has the slow debuff been working incorrectly for the past few years?

Comments

  • aidenvbatenburgaidenvbatenburg Member Posts: 4
    For reference:

  • This content has been removed.
  • xAdnannnnxAdnannnn Member Posts: 1
    ok now that is bugged
  • aidenvbatenburgaidenvbatenburg Member Posts: 4
    xAdnannnn said:

    ok now that is bugged

    Yeah and the worst part is I brought him to Phase 2 for experimental purposes and the unstoppable buff still stuns you when you hit him even though the unstoppable buff isn’t supposed to trigger. Gives me no motivation to actually attempt to try the fight again or spend revives if basic mechanics that have been in place for years don’t even work.
    If you simply look at the durations of the buffs and debuffs you can see the unstoppable triggered while the slow was active.


  • edited November 2021
    This content has been removed.
  • TerraTerra Member Posts: 8,465 ★★★★★
    edited November 2021
    Zan0 said:

    Not bugged and working as intended.
    Champion has increased unstoppable AA

    This, yeah. Read his abilities and nodes.
    SpiderGwens slow only prevents it by 100%, any nodes increasing AA will still make it procc
  • This content has been removed.
  • This content has been removed.
Sign In or Register to comment.