TheManaDrain.com
September 18, 2025, 12:00:29 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Calendar Login Register  
Pages: [1]
  Print  
Author Topic: Meddling Mage naming Fire/Ice  (Read 3905 times)
PucktheCat
My interests include blue decks, arguing, and beer.
Full Members
Basic User
***
Posts: 549


View Profile
« on: June 02, 2004, 12:35:08 pm »

Quote
Whatever you do, don't plan on stopping Fire/Ice.

Meddling Mage asks for (and "bans") a card name. Fire is not a valid card name. Ice is not a valid card name. Fire/Ice ("Fire and Ice") is a valid card name.

However, when your opponent goes to Fire your dude, he's only playing the spell Fire. A Meddling Mage set to "Fire/Ice" won't stop it.


Is this correct?  Crystalkeep seemed silent on the issue.  The Comp rules offer this:

Quote
505.7. If an effect instructs a player to name a card and the player wants to name a split card, the player must name both halves of the split card.


Which doesn't really address the question.  Also relevent is this:

Quote
409.4 A player can't begin to play a spell or activated ability that's prohibited from being played by an effect.


Since Fire/Ice is known as Fire/Ice everywhere except on the stack, and you can't put it on the stack because of Meddling Mage it would seem to me to not be playable, but I am not sure of that.  What is correct?

Leo
Logged
Jebus
Full Members
Basic User
***
Posts: 1216


Corn is no place for a mighty warrior!

Jeabus64
View Profile
« Reply #1 on: June 02, 2004, 12:36:37 pm »

No, it is not correct.  I already posted in that thread.

The Mage prevents you from playing the named card, not the named spell.

There is no Spell named Fire/Ice, but there is a card.  Naming Fire/Ice prevents you from playing the card Fire/Ice no matter which half you actually play.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!
Page created in 0.025 seconds with 18 queries.