autokilled after routing an ashen angel. bug?

[Endoperez]

Very mysterious. First the AA hits TO, deals some damage, and then TO damages the AA without attack roll.
I don't think the "dmg256" line means that that much damage is dealt, because on the next line, there's "dmg 11 eff 256". Note the extra space after 'dmg' in the latter. I think the AA died due to Holy Avenger being triggered, but I don't know why the TO died as well. Or perhaps, why the TO didn't die when he was supposed to.

[Omnirizon]

But the AA had routed before any of that even happened. my TO hit the the AA and had him down to 4/35 HP, while my TO was still at 68/68. According to the replay, the AA actually became enslaved on that last hit (the little red cross bleep). You can see where it says "army rout for independents, no units left" or something. Then in the next line, instead of routing, the AA takes another swing, actually manages to inflict damage (but not near enough to kill), and causes holy avenger to proc. More weirdness ensues.

[Ironhawk]

Omni - didnt you say in the game thread the the Ashen Angel became Enslaved by the Tart Chains? If so, I wonder if you enslaved it, and then unwittingly killed it with your Holy Avenger attack? This in turn cause some kind of wierd routing to kick in?

[Omnirizon]

It had already routed, but then attacked me causing the Holy Avenger to proc.

The unusual behavior started before the Holy Avenger. and at any rate, the HA didn't damage it anyway; it resisted it.

[Endoperez]

The Ashen Angel didn't rout, but I don't think that's what this bug is about. It could be that Ashen Angels don't rout, or that this is one case where units would only rout the next turn. The "XXX army is routing" message is probably triggered whenever one of the global routing rules is called for, even if there aren't any units that would, actually, rout in the battle.

Also, I think sometimes it takes a turn before all squads actually rout.