Champ immunities are just status effects?

We've had situations where AAR from Apoc causes immune to champs to be affected by bleed and poison. This would mean immunity is an effect champs gain at the start of the fight that remove/purifies debuffs when applied instantly. Maybe. That's just a hunch. BUT...

With Strikers there's a new bug that , when you enter a fight with auto fight and the AI uses the striker as soon as the fight starts, all your status effects are removed. Poison from suicides? Gone. Bleed from suicides? Gone. Hercules's feats of strength? Gone.

When auto fight is on, suicides are gone. But not when it is not

Here are two champ immunities being bypassed. And they both have Auto fight on

Comments

Lpoo

Thanks for pointing this out.. this is weird

DNA3000

We've had situations where AAR from Apoc causes immune to champs to be affected by bleed and poison. This would mean immunity is an effect champs gain at the start of the fight that remove/purifies debuffs when applied instantly. Maybe.

From what I understand, it is a bit more complicated than this, but you're mostly correct. The actual nuts and bolts of how this works is a bit more Rube Goldbergian, but immunity is a kind of status effect "flag" that tells the game how effects interact with the champion, and champion immunities are just abilities that the game applies to the champions before the start of the fight whose effects are basically permanent immunity effects. These effects are themselves supposed to be immune to purify, so they can't be removed by anything that ordinarily removes effects during a fight (they are also unaffected by ability accuracy modifications because the ability only triggers once, before the fight, to confer the immunity - they do not "trigger" when an attack lands to purify the debuff).

The problem with Strikers is that they are still somewhat experimental (which is why they were introduced in this side quest before being used more widely) and there's still some conceptual and implementation work to do for them. In particular, the current *concept* of the striker is not that your champ gains an ability that happens to look like the striker, it is more like your champ "tags in" another champ for a brief moment. So during the striker animation, the champ that is attacking should be the striker, not "you." But that opens a serious can of worms over what effects should carry over to the striker, which effects should the striker return to the original champ, and what effects should go away during the striker and which are supposed to come back.

It is interesting that autofight has an impact on this: I suspect it probably has to do with the implementation treating strikers differently when the computer uses them against the player than when the player uses them against the computer, and this has carried over into auto-fight.