Collectible Card Game Headquarters

Describe the Bug:
1- Skullscorch AI "shouldn't have the option" to loose life when AI will loose the game taking 4 damage because AI has 4 or less life if AI can't prevent the damage.I saw in 3 different games AI with less than 4 life deciding to take 4 damage and at least 1 of those games AI could have won it if decided to discard 2 cards.
2- AI in several games with no cards to discard always selected to take damage.(in all games this was the worst choice)
Which card did behave improperly ?
Skullscorch (AI having 4 or less life)

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
Manalink 2014/12/20: Commanding 2014 Urzas,duel

What exactly should be the correct behavior/interaction ?
1- Skullscorch AI doesn't decide to take 4 damage when AI has 4 or less life.(ideally takes damage only if AI can prevent the damage)
2- AI when doesn't have cards in hand to discard in most cases should not choose to take 4 damage.(can we give a lot more ai value not to take damage to discard? is this possible? )
Are any other cards possibly affected by this bug ?
-
SAVEGAME CORRUPTED

The part about taking damage with no cards in hand is confirmed, but I could never get it to kill itself in over 20 tests.

1- Please try with a deck that has valuable cards in AI's hand and not only lands and ornithopters.(maybe that is the reason why doesn't take 4 damage)
2- Please try to check if AI has no cards in hand and 4 or less life and hit with a Skullscorch or 12 life and hit it with 3 Skullscorch.

1) In all tests AI was using a random deck. Don't remember which (although at least 3 were used as I tried multiple games).

2) Tested with AI having 3 life and various number of cards (never chose loose life). Then tested with AI having 5 life and various number of cards (still always chose discard). Then tested with AI having 22 life and various number of cards, and AI chose to loose life.

3) Not saying it never happens, but this is why I hate testing AI actions. I can't control it, and in my tests it never happened.

Thanks for all your effort BAgate it could be a specific card in my games that led AI choose foolishly.

Fixed in a955f0c