Open GoogleCodeExporter opened 9 years ago
Original comment by wagic.la...@gmail.com
on 8 Nov 2009 at 6:47
Original comment by wagic.la...@gmail.com
on 10 Dec 2009 at 10:31
this might have been fixed when i changed cantregenerate to cantregen. Found
out the parser was reading cantregenerate AS regenerate, might be possible the
Ai "badability" flag might also have been reading cantregenerate the same way,
thinking "regenerate" was a bad thing.
anyone care to do extensive testing?
Original comment by omegabla...@gmail.com
on 21 Aug 2010 at 2:34
Hi,
The issue is older than the introduction of the cantregenerate keyword and is
linked to the introduction of M10 rules.
Before the AI use a simple ->creatures goes to graveyard -> has regenerate ? ->
enough mana ?
Now since M10 the AI would need to regenerate before the creature goes to the
graveyard...The AI can't understand which creatures have a "risk" of going to
graveyard...
nevertheless testing is alway good...but i don't think it would change anything
Original comment by wagic.la...@gmail.com
on 22 Aug 2010 at 5:45
how about have Ai always interupt with a regenerate if it owns a creature or
card with regen and damage is placed on the stack?
Original comment by omegabla...@gmail.com
on 11 Sep 2010 at 6:23
Ai will now use regenerate during combat however this bug still exist because
Ai was never taught to interupt damage spells to use it.
Original comment by omegabla...@gmail.com
on 22 Oct 2010 at 8:50
changed name to fit the current situation. it now uses it in combat.
Original comment by omegabla...@gmail.com
on 24 Oct 2010 at 12:57
Original comment by pank...@gmail.com
on 28 Sep 2013 at 11:49
Original issue reported on code.google.com by
wagic.la...@gmail.com
on 7 Nov 2009 at 6:16