Yosituna wrote:The AI will play
Scorched Ruins when it has only one other land out, and will sacrifice both that land and
Scorched Ruins to pay the cost for
Scorched Ruins. (ETA: Or it might be sacrificing one, not be able to sacrifice a second, and so
Scorched Ruins goes into the graveyard, but either way it seems very much something the AI should not be doing.)
That actually sounds like an engine bug since rules don't allow this. Either you can sacrifice two untapped lands (and
Scorched Ruins itself doesn't count, since it's not on the battlefield at this point), and then you put
Scorched Ruins onto the battlefield, or you can't sacrifice them, and then you have to put
Scorched Ruins into the graveyard, but don't sacrifice anything. But losing
Scorched Ruins AND another land shouldn't be possible.
I think that the problem is in this line:
- Code: Select all
SVar:PayBeforeETB:AB$ Sacrifice | Cost$ 0 | SacValid$ Land.untapped | Defined$ You | RememberSacrificed$ True | Amount$ 2 | SubAbility$ MoveToGraveyard
The source of the ability should be not on the battlefield at this point and not a valid selection for sacrifice, but apparently it gets counted as such. So, until this bigger problem is fixed, "Land.untapped" should be replaced by "Land.other+untapped", which will disallow sacrificing
Scorched Ruins to its own ability.
The same fix also has to be applied to
Lotus Vale.
Other cards with similar ETB conditions (
Balduvian Trading Post,
Heart of Yavimaya,
Kjeldoran Outpost,
Lake of the Dead,
Soldevi Excavations) will not normally have this problem, as they don't satisfy their own condition. However, in case you have something like
Prismatic Omen, they will satisfy it and the game will erroneously allow you to sacrifice them to their own ability, so they should get the same fix as well.