Posts with deep dives into a particular game state or card combinations.
In a recent game, a question arose about crewing. Two vehicles are in play, and one creature. Can you tap the one creature to crew both vehicles? I played it only being able to crew a single vehicle, and a quick look at the rules didn’t seem to clarify. What do you think?
-s
Fleetwheel Cruiser vehicle [wizards.com]
http://gatherer.wizards.com/Pages/Card/Details.aspx?multiverseid=417787
If I play a deck with only one land can I mulligan until I find my land?
Or is it? Conspiracy: Take the Crown adds a new element to the game – The Monarch. The Monarch gets to draw a card at the beginning of their end step. Awesome, but how does one become the Monarch? Well, first you can play one of these cards. But the more entertaining (and possibly easier method) is to deal combat damage to the poor sap that is the current Monarch. It remains to be seen whether being the Monarch will draw the ire of the table and whether the extra card is worth the extra attention. Maybe folks will try to avoid being the Monarch, but I doubt it.
There are some other fun new mechanics as well such as Council’s Dilemma. These cards require each player to decide between two choices on the card. Do you want to give someone an extra turn or their choice of a permanent you control? Quite the dilemma!
Finally, Conspiracy cards are back and in true fashion, they are not searchable on Wizard’s Card Search so you will have to wait to see them. The important thing to note though is they do not count towards your 40 cards in your deck. Should you take a conspiracy card or the card your deck needs? Tough decisions ahead…
There are two other new mechanics, Goad and Melee, but you can look those up on your own.
No, seriously. Look them up yourself.
In Mississippi the important thing is hooch, not bar equipment. — Florence King
Q: Does Equipment fall off if you attach it to a manland and it stops being a creature?
A: Yes. If you have an Equipment or “Enchant/Aura Creature” attached to a create and the creature stops being a creature, then the attached card is buried. This happens during the at the beginning of the end step when when the land stops being a creature and state-based actions checked and resolved. So the Aura (Enchant Creature) or Equipment has to check if it’s target is valid and when it checks, the object it was targeting is no longer a legal target so it is placed in the graveyard (if Aura) or stops being equipped.
MrG
=====
References:
Comprehensive Rules:
301.5 Some artifacts have the subtype “Equipment.” An Equipment can be attached to a creature. It can’t legally be attached to an object that isn’t a creature.
303.4a An Aura spell requires a target, which is defined by its enchant ability.
303.4c If an Aura is enchanting an illegal object or player as defined by its enchant ability and other applicable effects, the object it was attached to no longer exists, or the player it was attached to has left the game, the Aura is put into its owner’s graveyard. (This is a state-based action. See rule 704.)
514.3a At this point, the game checks to see if any state-based actions would be performed and/or any triggered abilities are waiting to be put onto the stack (including those that trigger “at the beginning of the next cleanup step”). If so, those state-based actions are performed, then those triggered abilities are put on the stack, then the active player gets priority. Players may cast spells and activate abilities. Once the stack is empty and all players pass in succession, another cleanup step begins.
704.3 Whenever a player would get priority (see rule 116, “Timing and Priority”), the game checks for any of the listed conditions for state-based actions, then performs all applicable state-based actions simultaneously as a single event. If any state-based actions are performed as a result of a check, the check is repeated; otherwise all triggered abilities that are waiting to be put on the stack are put on the stack, then the check is repeated. Once no more state-based actions have been performed as the result of a check and no triggered abilities are waiting to be put on the stack, the appropriate player gets priority. This process also occurs during the cleanup step (see rule 514), except that if no state- based actions are performed as the result of the step’s first check and no triggered abilities are waiting to be put on the stack, then no player gets priority and the step ends.
704.5n If an Aura is attached to an illegal object or player, or is not attached to an object or player, that Aura is put into its owner’s graveyard.
704.5p If an Equipment or Fortification is attached to an illegal permanent, it becomes unattached from that permanent. It remains on the battlefield.
Links to other explanations:
[stackexchange]…do-auras-and-equipment-stay-on-cards-if-they-stop-being-creatures
[mtgsalvation]…man-lands
Q: Does the Planeswalker rule apply when I cast a Planeswalker that another person already has?
A: So Planeswalkers and Legends do not check what any other player has in play. It only cares that you don’t have Planeswalkers and Legends on your side. If you do make a mistake and add a second Chandra to your side, you get to decide which sticks around. This would be important if you have invested turns build Planeswalker Loyalty counters. This how it works when you copy a Planeswalkers and Legends another player has on the Battlefield. So, no problem.
Further: No. You still cannot use Karakas to bounce anything other than a Legendary creature.
This rule has been in effect since 2014.
MrG
=====
References:
Comprehensive Rules:
704.5j If a player controls two or more planeswalkers that share a planeswalker type, that player chooses one of them, and the rest are put into their owners’ graveyards. This is called the “planeswalker uniqueness rule.”
704.5k If a player controls two or more legendary permanents with the same name, that player chooses one of them, and the rest are put into their owners’ graveyards. This is called the “legend rule.”
Links to other explanations:
[mtgsalvation]…Legend_rule
