Open GoogleCodeExporter opened 8 years ago
I have seen things like this many times, the AI has assigned a blocker with
regen, after the point at which blockers should be committed, the AI
regenerates the creature and then changes blocking assignments.
Original comment by Dansi...@gmail.com
on 15 Aug 2012 at 6:38
the topic to this does not match what you are trying to report. Skeleton should
tap, ai taps for regen, then blocks a second creature....
do you mean in cases of first strike and double strike? you need to be more
specific with this report becuase I stand to screw up alot of function if you
don't provide a more accurate report.
and as it stands i can not reproduce it at all....which means i can close this
as invalid, but i will wait until you can give me more info before doing so....
is the ai changing his minds about who it intends to block after it uses regen?
is the ai changing the block assignment in the damage step? or just before
switching.
just a little info about regen and ai...ai can and will change block assignment
on a creature that just gained regen during blockers step right before entering
damage step....reason being that it decided on the block assignment, regen adds
a new aspect for ai to consider and it will change the block order keeping in
mind that the creature is no longer going to die blocking either something it
considered more dangerous or something that can clearly kill the creature.
changing block assignment during blockers is a totally legal move, and if it is
doing what i think you are saying, then it should, can, and will do it :)
however, if you mean it is happening with first strike damage and double
strike, where ai is reassigning blockers in any step other then blockers, this
is what i need to know.
i should not have to fish for info, please be as specific about this as
possible. regenerate is one of those abilities that are deeply integrated into
the combat steps. like i mentioned if there is a problem I need to know where
it is happenning and when otherwise i will end up screwing up stuff just trying
to chase a wild goose.
thanks in advance.
Original comment by omegabla...@gmail.com
on 24 Aug 2012 at 9:39
dude, i never mean to give any programmer issues, in fact i do my best to help
programmers....but you're asking me to remember exact situations from 3 months
ago.
i believe i blocked, paid a black, selected to regen the skeleton, from here i
know there was an issue, but it was too long ago for me to remember. i think
when i regened the skeleton, it's supposed to tap the skeleton, but it untapped
it instead.
Original comment by tjburchf...@gmail.com
on 24 Aug 2012 at 9:45
Zethfox, I know exactly what be is talking aboit, and the issue is valid. The
problem is that the ai gets to choose its blockers several times during the
combat phase, even when it is not allowed to. Lets chat about this if you need
details.
Original comment by wagic.the.homebrew@gmail.com
on 24 Aug 2012 at 11:24
:) dont take my comments personally, i appreciate the reports people do, just
need more info on this bug...when i got to this bug i had already brain mashed
like 30 other issues in the bug tracker...yes wololo i need a repro method for
this actually.
currently this issue can be happen from way too many places, I'm just trying to
narrow it down to something i can recreate over and over.
Original comment by omegabla...@gmail.com
on 25 Aug 2012 at 12:51
also, I only ask for super specifics on this bug becuase regenerate is handled
in about 7 different major functions and even through a function in
MTGCardInstance...
I might consider recoding the regenerate handling into a rule, removing the
scattered functions that handle it. though if wololo saids ai is choosing
blockers in illegal phases, then we have a much larger bug in our hands.
Original comment by omegabla...@gmail.com
on 25 Aug 2012 at 12:55
Original issue reported on code.google.com by
tjburchf...@gmail.com
on 12 May 2012 at 8:35