[fixed]Serra Paladin AI can't prevent damage to AI
Posted: 05 Jun 2017, 13:11
Describe the Bug:
1- AI can't activate Serra Paladin's ability to prevent damage to creatures. AI activate values in ct_all are not all put as it should for prevent damage cards.Only the before combat value is put (after 2nd ability to give vigilance). fixed in dev 778ccb5 version.
Note: I tested and when the values are inserted AI can prevent damage to creatures
Still can't prevent damage to AI player at least.
2- Also please look at AI Serra Paladin vigilance ability because it seems to often activate it on Serra Paladin itself which doesn't make sense unless an effect forces AI to attack with it.
[b]Which card did behave improperly?
Serra Paladin AI part.
Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Manalink 2016/08/27: Eldritch Moon v2, duel
What exactly should be the correct behavior/interaction?
1- Serra Paladin: AI can activate prevent 1 damage ability to creatures or players.
2- AI uses better the vigilance ability and prefers to target another creature unless AI needs to tap Serra Paladin to avoid being forced to attack with it.
Are any other cards possibly affected by this bug?
-
Note: I tested and when the values are inserted AI can prevent damage to creatures
Still can't prevent damage to AI player at least.
2- Also please look at AI Serra Paladin vigilance ability because it seems to often activate it on Serra Paladin itself which doesn't make sense unless an effect forces AI to attack with it.
[b]Which card did behave improperly?
Serra Paladin AI part.
Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Manalink 2016/08/27: Eldritch Moon v2, duel
What exactly should be the correct behavior/interaction?
1- Serra Paladin: AI can activate prevent 1 damage ability to creatures or players.
2- AI uses better the vigilance ability and prefers to target another creature unless AI needs to tap Serra Paladin to avoid being forced to attack with it.
Are any other cards possibly affected by this bug?
-