I have seen this a few times, the warrior attacks before armour up and the looses, where if he had armour up before the attack I would had survived. Also you loose more life this way I believe. Of course this is only inthe situations where it would armour up anyway just after the attack.

Happened to me twice already, and is not the optimal move if you could survive if it change the order of armour up and attacking?

Can someone look into the order, calculation before attacking, so you do not loose because of this error?

I hope this bug helps, I tried searching and didn't find similiar topic of this problem.

I don't know how to code this correctly or how which actions to take are calculated.

If attacking a minion with a weapon is on the action list (or what you call it) as well as armour up, then do armour up before attacking. Like switching the order between attacking with weapon and armour up, if that makes sense?

Thank you for replying and I hope this could be done.

In almost every case armor has higher value than life points with a warrior, so always armor up before attacking would be the wrong thing.
You see a lot of top players attacking and armor up after that. This is because of cards like shield slam, alextrasa and heal stuff.

I don't think the AI has some kind of suicide mechanism and the attack first was a missplay in this case, which should be fixed with an aditional check to only perform attacks if this doesn't kill you.

The interesting information is what AI did you use and did you run out of time when these actions were performed?
There is some kind of security mechanism when calculation takes longer than available turn time, which would perform any action (even if it's not the best) rather than doing nothing.

If your missplay happened when running out of time you need to reduce your AI parameters, if not we need the additional check.
Please report back.

As I remember it didn't run out of time, but it killed itself rather than with armour up (would be enough with your suggestion on checking on suicide). I used maximum calculation on board number and enemy turn.
I used default deckrules and default AI (no other AI used). It didn't happen often but I noticed it twice when I run a warrior deck.