Three-headed Grave Betrayal
Asked by oshen 12 years ago
I'm playing in a free-for-all with two of my friends. One of my friends has a Grave Betrayal on the field and so do I. When our third friend's creature dies, who gets the creature?
Who's ever grave betrayal triggered first. For example, if you and 2 friends are sitting at a table, just like the situation in your question, but you went first, you're player A (and you have a grave betrayal), Player B is the one whose creature died (this is just an example), and the last player to go, player C also has a grave betrayal. Player B's creature died, which trigger's Player C's grave betrayal, and then your's triggers next. You're resolves first, giving you the creature, but Player C's resolves next, giving him the creature and 2 +1/+1 counters on it. This is what I believe to happen, but I could be wrong.
February 23, 2013 8:03 p.m.
You are player A, the other Grave Betrayal belongs to player B, and player C has a creature die. Abilities go on the stack in APNAP (Active Player, Non Active Player) order, so your Betrayal will trigger and go on the stack, then player B's will. The stack resolves in FILO (First In, Last Out) order, so player B's Grave Betrayl resolves first, giving him the creature.
February 23, 2013 8:05 p.m.
JMANN, in your example, player C's ability will fizzle because the creature is no longer in the graveyard.
February 23, 2013 8:06 p.m.
But it's when it dies, and it never checks the graveyard right?
February 23, 2013 8:08 p.m.
Basically it is whoever's Grave Betrayal triggers last. If Player A has a Grizzly Bears out and an card:Ashnod's Altar. You are player B and have a Grave Betrayal on the battlefield. Player C has a Grave Betrayal on the battlefield also.
This is the order of events:
Player A sacrifices Grizzly Bears to card:Ashnod's Altar to get 2 colorless. You are next in the turn order so your Grave Betrayal trigger goes on the stack. Then Player C, the player after you in turn order, has his trigger go on the stack.
Once the stack begins to resolve it will resolve in "First In, Last Out" Order. That means Player C's trigger will resolve first taking Grizzly Bears out of the graveyard and putting it onto the battlefield under his control as a 3/3 black zombie bear.
Then your trigger will resolve and "look for" Grizzly Bears in the graveyard. It will "see" that the Grizzly Bears is no longer there and do nothing.
Hope that helps.
February 23, 2013 10:08 p.m.
Ok i think i understand but i thought that when 2 actions are supposed to happen simultaneously the player whose turn it is choose the order in which they activate.
February 23, 2013 10:17 p.m.
When two triggers/abilities/spells go on the stack simultaneously that the active player is in control of, then they can choose which order they are put on the stack, but how an opponent's card triggers it out of their control.
And thanks Kirtanian for clearing that up.
February 23, 2013 10:19 p.m.
And here is from the rules in case you need verification of what is being said:
101.4. If multiple players would make choices and/or take actions at the same time, the active player (the player whose turn it is) makes any choices required, then the next player in turn order (usually the player seated to the active players left) makes any choices required, followed by the remaining nonactive players in turn order. Then the actions happen simultaneously. This rule is often referred to as the Active Player, Nonactive Player (APNAP) order rule.
603.3b If multiple abilities have triggered since the last time a player received priority, each player, in APNAP order, puts triggered abilities he or she controls on the stack in any order he or she chooses. (See rule 101.4.) Then the game once again checks for and resolves state-based actions until none are performed, then abilities that triggered during this process go on the stack. This process repeats until no new state-based actions are performed and no abilities trigger. Then the appropriate player gets priority.
valendras says... #1
Whoever killed it
February 23, 2013 7:53 p.m.