Closed GoogleCodeExporter closed 9 years ago
Confirmed! :(
Original comment by dan.solo...@googlemail.com
on 28 Jul 2010 at 4:01
Same issue as 439.
You want to use @movedTo(graveyard) from(mytgt|Battlefield) instead. The card
coder made a confusion between the "previous" and the "next" object.
I know this is confusing, because lots of times the two objects are REALLY
similar.
Think of another example: "when a creature is put into a graveyard from play"
is NOT written:
@movedTo(creature|graveyard) from(Battlefield) , BUT
@movedTo(graveyard) from(creature|Battlefield)
the reason is that there is a possibility that something is a Creature on the
Battlefield, but becomes something else when it reaches the graveyard. (think
about Living Lands + a forest)
fixed in 2302, but I didn't verify the fix, please verify if possible
Original comment by wagic.the.homebrew@gmail.com
on 23 Sep 2010 at 5:04
Fix confirmed! :)
Original comment by dan.solo...@googlemail.com
on 23 Sep 2010 at 7:20
Original issue reported on code.google.com by
tvil...@gmail.com
on 28 Jul 2010 at 12:16