Sacrifice fetch with Devastating Summons then search a land

Asked by zeda 14 years ago

1- Can I sacrifice an Arid Mesa with Devastating Summons , then search my library for an Mountain?


2- If I attack with a 1/1 creature and my opponent blocks with a 2/2 creature, then I response with a Disfigure on it, the opponent takes 1 damage or the damage goes to the 2/2 (0/0 in thast moment)?


Thanks.

Siegfried says... Accepted answer #1

1) No, sacrificing Mesa is part of the cost of Summons. You pay the cost upon casting the spell, it technically happens before anyone (including yourself) can put any other abilities on the stack.

2) The damage from your creature disappears. Upon Disfigure resolving, the creature they assigned to block is put in the graveyard as a state-based action. But your attacker has still had a blocker assigned to it. It will deal its power as damage to a creature which is no longer there, so basically nothing happens.

December 1, 2010 10:28 a.m.

Eyehate says... #2

Siegfried has you covered here.

The Arid Mesa must be sacrificed as part of the cost of the Devastating Summons or it won't count towards the "X" value.

And once a creature is "blocked" it will only deal combat damage to the defending player if it has or is given trample before the combat damage step.

December 1, 2010 10:53 a.m.

π_is_the_word says... #3

1) I agree with Siegfried completely, he has everything right. Devastating Summons has the land being Sacrificed to cast Devastating Summons. So, you can't respond by fetching until after it is cast which, is after you already Sacrificed the Land to pay the casting cost.

2) You should have Disfigured then, declared attack in order to deal damage to the opponent, once again Siegfried has stated it better than I can.

I hope I haven't confused you. If I did please just forget what I said and listen to Siegfried.

December 1, 2010 10:55 a.m.

zeda says... #4

Ok, thank you for all of your responses!

December 1, 2010 11:06 a.m.

zeda says... #5

*answers lol

December 1, 2010 11:07 a.m.

This discussion has been closed