603.1<\/a> Triggered abilities have a trigger condition and an effect. They are written as “[Trigger condition], [effect],” and begin with the word “when,” “whenever,” or “at.” They can also be expressed as “[When\/Whenever\/At] [trigger event], [effect].” A triggered ability is said to \u201ctrigger\u201d whenever the above-mentioned [trigger condition] has been met.<\/p><\/blockquote>\n
Generally speaking, the point at which a player needs to demonstrate awareness of a triggered ability is after it has triggered, but no later than when that ability would \u201cfirst matter.\u201d For triggers with physical actions, a verbal acknowledgement of the trigger is not sufficient; the physical actions must be performed at the correct time. There are thousands of triggers in the game, and they each work a little differently. Some require targets, some require choices made by opponents, some have physical actions on resolution, some are invisible, etc., so when a trigger \u201cfirst matters\u201d is not something that can be defined in a single sentence. We\u2019ll revisit this phrase throughout this section.<\/div>\n
The point by which the player needs to demonstrate this awareness depends on the impact that the trigger would have on the game:<\/p>\n
This is another way of saying that in order to figure out whether or not a player has missed a trigger, you must first consider what the ability does. The point at which the ability first matters depends on which of the below four categories that ability belongs to. Note that this is intended to be an exhaustive list \u2014 all triggered abilities in the game may be categorized in one of the following ways.<\/div>\n\n
- A triggered ability that requires its controller to choose targets (other than ‘target opponent’), modes, or other choices made when the ability is put onto the stack<\/strong>: The controller must announce those choices before they next pass priority.<\/li>\n<\/ul>\n
These are triggered abilities that first matter as they are put onto the stack. In order to avoid missing these triggers, the controller of these abilities must remember to make the choices involved with these right away.<\/p>\nExamples:<\/strong> Advocate of the Beast<\/a>, Archaeomancer<\/a>, Blightcaster<\/a><\/p>\n
For the purposes of triggered abilities, the choice of a \u201ctarget opponent\u201d is automatically assumed in a two-player game. The controller is not required to explicitly make this choice to avoid missing the trigger. A player isn’t off the hook just yet, though \u2014 he or she will still need to demonstrate awareness at some later point according to whichever of the three remaining groups the effect fits into. Also, the opponent is not assumed to be the target when the trigger requires a \u201ctarget player,\u201d even if it’s \u201cobvious\u201d that you want to target the opponent.<\/div>\n
\n
- A triggered ability that causes a change in the visible game state (including life totals) or requires a choice upon resolution<\/strong>: The controller must take the appropriate physical action or make it clear what the action taken or choice made is before taking any game actions (such as casting a sorcery spell or explicitly\u00a0moving to the next step or phase) that can be taken only after the triggered ability should have resolved.<\/li>\n<\/ul>\n
These are triggered abilities that first matter at resolution. In order to avoid missing these triggers, the controller of these abilities must remember to make the choice or take the visible action when the trigger would resolve (or prompt the opponent to do so).<\/p>\nExamples:<\/strong> Ainok Guide<\/a>, Burning Earth<\/a>, Abzan Skycaptain<\/a><\/p>\n
As it turns out, this is by far the most common type of triggered ability in the game. Most triggered abilities involve obvious visible actions such as drawing cards, moving objects from zone to zone, or modifying the state of permanents. Note that life totals are considered part of the visible representation of the game \u2014 this implies that triggered abilities that cause a player to take damage or gain life first matter at the point that a score pad should be updated.<\/div>\n
Note that casting an instant spell or activating an ability doesn\u2019t mean a triggered ability has been forgotten, as it could still be on the stack.<\/p>\n
When making this determination, a lot of benefit of the doubt is given to players \u2014 they usually have to go well out of their way to show that they’ve missed a trigger. For example, if a player casts a spell during upkeep, it is assumed that upkeep triggers are still on the stack, not missed.<\/div>\n\n
- A triggered ability that changes the rules of the game<\/strong>: The controller must acknowledge the trigger or prevent an opponent from taking any resulting illegal action.<\/li>\n<\/ul>\n
These are triggered abilities that first matter at the point at which an opponent would first take what would otherwise be an illegal action. In order to avoid missing these triggers, the controller of these abilities must announce the trigger at the correct time and\/or actively prevent an opponent from taking an action that wouldn\u2019t be possible had the triggered ability resolved.<\/p>\nExamples:<\/strong> Brine Elemental<\/a>, Lavinia of the Tenth<\/a>, Wall of Frost<\/a>, Pyreheart Wolf<\/a><\/p>\n
Players are under no obligation to assume the resolution of a triggered ability controlled by an opponent that has not yet been acknowledged. Players are welcome to behave as if it an unacknowledged triggered ability belonging to an opponent was forgotten, but they must expect to be stopped by that opponent if they begin to take an action that the resolution of the triggered ability rendered illegal.<\/p>\n
For example, suppose Abelard attacks Nutella with a Pyreheart Wolf<\/a> and doesn\u2019t immediately mention his trigger. Nutella is allowed to try to declare her animated Mutavault<\/a> as a blocker. If Abelard does not speak up about this blocking assignment being illegal before taking a later action or continuing with combat, Abelard has missed his trigger.<\/p>\n
If a player chooses to perform this \u201cMissed Trigger gambit,\u201d so to speak, he or she risks giving away information like the identity of cards in his or her hand or intended plays. Worse yet, a player banking on a forgotten trigger of this type may lock himself or herself into plays he or she would otherwise not want to take. In the above example, if Abelard prevents Nutella from blocking with her Mutavault, Nutella would not get to undo the activation of Mutavault’s ability and would not get a \u201crefund\u201d for the mana spent. <\/div>\n
\n
- A triggered ability that affects the game state in non-visible ways<\/strong>: The controller must make the change known by the first time the change has an effect on the visible game state.<\/li>\n<\/ul>\n
These are triggered abilities that aren’t immediately visually apparent, but would first matter at some point after resolution. Examples include causing a creature to gain some ability, giving a creature a power and toughness bonus (but not a counter), or dealing damage to a creature. Each of these is an example of an effect that isn’t usually represented visually.<\/p>\nHowever, the result of these effects may cause some later visible change to the game state. For example, suppose Norville controls an Aether Flash<\/a> at the time that Anise casts a 3\/3 Hill Giant<\/a>, and neither player mentions the trigger. If, later that turn, Norville deals 1 additional damage to Anise’s creature, Norville will have not missed his Aether Flash trigger if he prompts Anise to put her creature into the graveyard at that time. In this case, Aether Flash’s trigger first matters at the point when Anise\u2019s creature receives lethal damage.<\/p>\n
Examples:<\/strong> Boros Elite<\/a>, Steppe Lynx<\/a>, Zhur-Taa Ancient<\/a>, Emrakul, the Aeons Torn<\/a><\/p>\n
This is something that people get hung up on, and will be addressed in more detail below. But the default assumption of the opponent should be that the trigger happened when it was supposed to.<\/div>\n
Once any of the above obligations has been fulfilled, further problems are treated as a Game Play Error \u2014 Game Rule Violation<\/a>.<\/p>\n
As convenient as it may be for judges to consider previously acknowledged but problematically-executed triggered abilities to be missed, they must nonetheless be treated as a different infraction.<\/p>\nFor example, suppose Acetone attacks Neutrino with an unblocked Arbor Elf<\/a> equipped with Sword of Feast and Famine<\/a>. During the combat damage step, Acetone untaps his lands but both players forget about Neutrino discarding. Even if this is noticed during the post combat main phase, this must be treated as a Game Rules Violation by either rewinding the game or applying the appropriate partial fix, and not by simply asking Neutrino if she\u2019d like the discard ability to be placed on the stack. It is also a Game Rules Violation if you acknowledge a trigger at the proper time or earlier, and then, because of multiple things on the stack, you forget to resolve it.<\/div>\n
Triggered abilities that do nothing except create delayed triggered abilities automatically resolve without requiring acknowledgment. Awareness of the resulting delayed trigger must be demonstrated at the appropriate point.<\/p>\n
The first sentence implies that it is impossible to miss, for example, Grave Betrayal<\/a>\u2019s triggered ability. However, the second sentence means that the delayed triggered ability itself, which makes a visible change to the game state, may be missed if not acknowledged by the time it would first matter. If Ned’s creature dies while Abe controls a Grave Betrayal, the trigger happens. However Abe can still miss the resulting delayed trigger by later passing the turn without returning the creature to the battlefield or otherwise calling attention to the ability. This is a concession to the way players play. The delayed triggers creation isn\u2019t \u201crelevant\u201d but its resolution is.<\/div>\nTriggered abilities that do nothing except create one or more copies of a spell or ability (such as Storm or Cipher) automatically resolve, but awareness of the resulting objects must be demonstrated using the same requirements as described above (even though the objects may not be triggered abilities).<\/p>\n
For example, the Storm ability of Empty the Warrens<\/a> is not considered missed even if the spell\u2019s controller does not specifically announce the trigger before passing priority after casting the spell. However, if that player then forgets to put the additional Goblins onto the battlefield before moving on with his or her turn, the Storm trigger would be considered missed after all. Again, this is a concession to the way players actually play Magic<\/strong>.<\/div>\nIf a triggered ability would have no impact on the game, it\u2019s not an infraction to fail to demonstrate awareness of it.<\/p>\n
Triggered abilities that don\u2019t matter are few and far between. When determining whether or not a triggered ability would have no impact on the game, you should not take into account how likely an opponent is to perform some optional action permitted by the ability. For example, a tapped Desecration Demon<\/a> should still have its triggered ability acknowledged and the opponent should be prompted for choice of a sacrifice even though Desecration Demon is already tapped.<\/div>\nFor example, if the effect of a triggered ability instructs its controller to sacrifice a creature, a player who controls no creatures isn\u2019t required to demonstrate awareness of the ability.<\/p>\n
Another example of a triggered ability that would have no impact on the game may occur in a scenario in which a player attacks with only a Chasm Drake<\/a>. The Chasm Drake itself is the only legal target for the ability, but giving a Chasm Drake a second instance of Flying would be redundant. So, this trigger would not matter and intentionally ignoring it would not be an infraction.<\/div>\nJudges do not intervene in a Missed Trigger situation unless they intend to issue a Warning or have reason to suspect that the controller is intentionally missing his or her triggered abilities.<\/p>\n
This is another very important detail to keep in mind when observing a match as either a spectator or judge. Simply asking a player if he or she acknowledged a triggered ability is itself a reminder of that ability. Worse still, calling attention to a particular triggered ability before it would first matter provides an opportunity for a player to acknowledge it then. Depending on the circumstances, making this mistake could be perceived by an opponent as a lack of impartiality or even as significant coaching. Furthermore, if a spectator makes this mistake, it could be considered Tournament Error \u2014 Outside Assistance<\/a>. Clearly, this should be avoided.<\/p>\nThe only exception to this, of course, is when a judge needs to issue a Warning or investigate a player for Cheating<\/a>. The needs of the tournament \u2014 specifically, ensuring its integrity \u2014 exceed those of an individual match.<\/div>\n
Examples<\/h2>\n
A.<\/strong> Knight of Infamy<\/a> (a 2\/1 creature with exalted) attacks alone. Its controller says \u201cTake two.\u201d<\/p>\n
(Whenever a creature you control attacks alone, that creature gets +1\/+1 until end of turn.) In this scenario, this ability first matters during the combat damage step. This is a triggered ability that affects the game state in non-visible ways. By indicating the Knight is attacking for 2 damage, the player has missed her trigger, even if she is stating the knight is attacking for 2 prior to the combat damage step.<\/div>\nB.<\/strong> A player forgets to remove the final time counter from a suspended spell and then draws a card during his draw step.<\/p>\n
(At the beginning of your upkeep, if this card is suspended, remove a time counter from it) In this scenario, this ability first matters before the player draws for the turn. This is a triggered ability that causes a change in the visible game state. Once the player draws a card, he has advanced the game past the point where the visible game state would first be altered had the trigger resolved.<\/div>\nC.<\/strong> A player casts Azorius Arrester<\/a>, then forgets its triggered ability by not choosing a target for it. He realizes this only after casting another spell.<\/p>\n
(When Azorius Arrester enters the battlefield, detain target creature an opponent controls.) In this scenario, this ability first matters before the player passes priority. This is a triggered ability that requires its controller to choose targets.<\/div>\nD.<\/strong> A player forgets to exile the Angel token created by Geist of Saint Traft<\/a> at end of combat. She realizes the error when declaring blockers during the next turn.<\/p>\n
In this scenario, this ability first matters before the player indicates that she has moved past the combat phase. This is a delayed triggered ability that causes a change in the visible game state.<\/div>\nPhilosophy<\/h2>\n
Triggered abilities are common and invisible, so players should not be harshly penalized when forgetting about one.<\/p>\n
It\u2019s pretty easy to forget triggers, there are a lot of them and there is often no visual component to them. They are also typically beneficial, and the ones that aren’t, the opponent is motivated to be aware of. Furthermore, triggered abilities have sort of a \u201cnatural\u201d handling if they\u2019re forgotten \u2014 most of the time, they can simply just not happen without any additional cleanup or situation-specific remedy being needed.<\/div>\nPlayers are expected to remember their own triggered abilities; intentionally ignoring one may be Unsporting Conduct \u2014 Cheating<\/a> (unless the ability would have no impact on the game as described above).<\/p>\n
So, while forgetting your trigger is not to be harshly penalized, intentionally missing your trigger is much more serious. Note the subtle usage of the word \u201cmay,\u201d in the sentence above. If you suspect a player of cheating, read the definition of Cheating to see if it applies. Another exception to this being Unsporting Conduct \u2013 Cheating<\/a> is if the player in question were not aware that intentionally ignoring one’s own triggered abilities is against the rules.<\/div>\nEven if an opponent is involved in the announcement or resolution of the ability, the controller is still responsible for ensuring the opponents make the appropriate choices and take the appropriate actions. Opponents are not required to point out triggered abilities that they do not control, though they may do so if they wish.<\/p>\n
Remembering one\u2019s trigger is always the responsibility of the player who controls the ability. This is usually, but not always, the controller of the object that has the ability. It doesn’t matter that the triggered ability may allow an opponent to take an optional action \u2014 the controller of the trigger is responsible for remembering it and prompting the opponent to make a choice. Examples include things like Frost Titan<\/a>, Desecration Demon<\/a> and Rhystic Study<\/a>.<\/p>\nOne of the many skills tested in Magic<\/strong> is the ability of players to remember their own triggered abilities. Players should not be punished for the inabilities or poor memories of their opponents.<\/p>\n
Why might a player want to remind an opponent of his or her triggered ability? It\u2019s possible that the triggered ability might be subjectively bad for that opponent. For example, suppose Absinthe is at 1 life and controls a Dark Confidant<\/a> whose triggered ability has been missed several times earlier in the game. Given the player\u2019s now low life total, Novocain would have a high incentive to make sure that the trigger happens when it\u2019s supposed to.<\/div>\n
Triggered abilities are assumed to be remembered until otherwise indicated, and the impact on the game state may not be immediately apparent.<\/p>\n
Triggered abilities are assumed to be remembered not only by both the player and opponent, but also by any judges watching the match. By failing to acknowledge a triggered ability by when it would first matter, the player effectively disproves this assumption. This sentence also answers the question of \u201cHow can I tell if my opponent missed his exalted trigger?\u201d You are to assume it happened until you have evidence that it didn’t. This is an important point. Just as you can acknowledge a trigger happened earlier than required, you can also indicate the trigger didn’t<\/strong> happen earlier than required. For example, if you untap with a Kragma Butcher<\/a> and say nothing indicating the trigger, it is assumed to be a 4\/3. However, the controller can indicate earlier than combat damage that he forgot the trigger. Attacking with an Ensnaring Bridge<\/a> on the battlefield might indicate its trigger was missed. Answering “what’s that creature’s power?” with “it’s a 2\/3” is an indication it was missed.<\/div>\nThe opponent\u2019s benefit is in not having to point out triggered abilities, although this does not mean that they can cause triggers to be missed.<\/p>\n
To repeat an earlier annotation, players are never responsible for remembering their opponent\u2019s triggers. Players are allowed to remain quiet about triggers controlled by an opponent being missed, even if the triggered ability would do something harmful to its controller. There is never a time when a player should be issued an infraction, be it Unsporting Conduct \u2014 Cheating<\/a>, Game Play Error \u2014 Failure to Maintain Game State<\/a>, etc., for either accidentally or intentionally not calling attention to an opponent\u2019s Missed Trigger. Players do not have to help their opponents beat them; however, they cannot trick their opponents into missing triggers.<\/div>\nIf an opponent requires information about the precise timing of a triggered ability or needs details about a game object that may be affected by a resolved triggered ability, that player may need to acknowledge that ability\u2019s existence before its controller does.<\/p>\n
Suppose Amaranth controls Cathedral of War<\/a> and attacks with her single 2\/2 Bear Cub<\/a>, proceeding through to the declare blockers step without mentioning the triggered ability. After declaring blockers, Niles considers casting Shock <\/a>targeting the unblocked Bear Cub<\/a>.<\/p>\nNiles has two options \u2014 he could simply cast Shock, targeting the Bear Cub, hoping that Amaranth forgot about the trigger. However, by doing so, Niles risks Amaranth acknowledging the trigger by afterward not putting the Bear Cub into the graveyard. In other words, just because Amaranth didn’t explicitly announce her trigger doesn’t mean she’s yet missed it \u2014 the point at which the trigger would first matter in this case would be after Shock resolves. So, if Niles were to attempt this ploy, he risks wasting his Shock.<\/p>\n
Alternatively, Niles could first ask Amaranth if any abilities have modified Bear Cub’s toughness. This is free information, so Amaranth would be required to answer it honestly and completely. With this option, the point at which Cathedral of War’s trigger would first matter would be when Amaranth answers the question.<\/p>\n
This may seem somewhat unsatisfactory to Niles, since asking questions about the toughness of the Bear Cub might remind Amaranth about her trigger and give her one last opportunity to acknowledge it. However, as the IPG says, \u201ctriggered abilities are assumed to be remembered until otherwise indicated.\u201d Niles should be reminded of this by judges as needed.<\/div>\n
A player who makes a play that may or may not be legal depending on whether an uncommunicated trigger has been remembered has not committed an infraction; their play either succeeds, confirming that the trigger has been missed, or is rewound.<\/p>\n
It isn’t up to the opponent to confirm whether or not a player has missed their trigger before making a play that may be illegal. For example, if Anna is attacking with Pyreheart Wolf<\/a>, it is not illegal for Nolan to block the wolf with one creature. When that block is proposed, it is up to Anna to indicate the illegality of the block or not, and this will determine if the play needs to be rewound.<\/div>\nPlayers may not cause triggered abilities controlled by an opponent to be missed by taking game actions or otherwise prematurely advancing the game.<\/p>\n
This sentence has a lot of philosophical weight, and provides guidance on how to deal with triggered abilities controlled by one player that trigger during another player\u2019s turn. Triggered abilities fitting this description deserve some special consideration. Generally speaking, the active player \u2014 that\u2019s the player whose turn it is \u2014 controls the flow of the game by taking each turn-based action as he or she moves through that turn\u2019s steps and phases. Magic<\/strong> players rarely explicitly pass priority, most of the time just shortcutting through nearly all of the technical rigmarole.<\/p>\nThe reason that policy allows for players to acknowledge triggers just after an opponent takes a game action that would otherwise cause the trigger to be missed is precisely because players do not usually prompt their opponents for actions before moving ahead with their turns. For example, players will often proceed straight from their main phase to declaring attackers without asking the opponent if he or she wants to first do anything \u2014 such as announcing any beginning of combat triggers.<\/p>\n
The Missed Trigger policy was written to address the way that players already play the game and not the other way around.<\/p>\n
A player that says nothing about his or her opponent\u2019s Braids, Cabal Minion<\/a> trigger before attempting to draw for the turn hasn\u2019t committed an infraction. If an opponent speaks up about the trigger as soon as the card is drawn, the trigger has not been missed.<\/div>\n
During an opponent\u2019s turn, if a trigger\u2019s controller demonstrates awareness of the trigger before they take an active role (such as taking an action or explicitly passing priority), the trigger is remembered.<\/p>\n
This sentence simply further clarifies what has been stated above. If a player has a trigger that would happen on an opponent\u2019s turn, that player has to actively “miss” it, they can’t be moved past the point of acknowledging the trigger by the active player’s actions in their own turn. It is also to prevent players from trying to use a loophole in the policy to rush past their opponents trigger, so that they can deny their opponent the trigger. This sentence closes the perception of that loophole. You cannot force your opponent to miss his or her trigger.<\/div>\nThe Out-of-Order Sequencing rules (MTR section 4.3<\/a>) may also be applicable, especially as they relate to batches of actions or resolving items on the stack in an improper order.<\/p>\n
From MTR 4.3<\/a>:<\/p>\nDue to the complexity of accurately representing a game of Magic<\/strong>, it is acceptable for players to engage in a block of actions that, while technically in an incorrect order, arrive at a legal and clearly understood game state once they are complete.<\/p>\n
All actions taken must be legal if they were executed in the correct order, and any opponent can ask the player to do the actions in the correct sequence so that he or she can respond at the appropriate time (at which point players will not be held to any still-pending actions).<\/p>\n
An out-of-order sequence must not result in a player prematurely gaining information which could reasonably affect decisions made later in that sequence.<\/p><\/blockquote>\n
This means that, in certain situations, players may acknowledge a trigger as part of a block of actions, some of which may technically be later than the point at which the trigger would first matter, without the trigger being missed.<\/p>\n
For example, a player may, in quick succession, sacrifice Pitchburn Devils<\/a> to pay the cost of his Carrion Feeder<\/a>\u2019s activated ability, then put a counter on the Carrion Feeder, and then say \u201cyou take 3,\u201d without Pitchburn Devils\u2019s trigger being considered missed. If the player takes these actions all at once without leaving an opportunity for the opponent to indicate responses or provide additional information, this should usually be ruled a legal out-of-order sequence of actions.<\/p>\n
A player could not, however, remove the last counter from a Rift Bolt<\/a>, then draw for the turn, and then say \u201cI\u2019ll Rift Bolt your creature.\u201d Even if the player performs these actions in quick succession and without the opponent saying anything, he or she would still have gained the knowledge of the card drawn for the turn before choosing his Rift Bolt target. This should usually be ruled a Missed Trigger.<\/div>\n
Additional Remedy<\/h2>\n
If the triggered ability specifies a default action associated with a choice made by the controller (usually “If you don’t …” or “… unless”), resolve it choosing the default option.<\/p>\n
\u201cOh, you drew before paying your Echo cost? That\u2019s cool, just sacrifice your guy now\u201d is the way that casual players have handled this kind of error for years \u2014 this piece of policy has significant precedent. Indeed, much of policy is built around the pre-existing habits and expectations of players. The above sentence is one of the most clear-cut examples of this in the entire IPG.<\/p>\nExamples:<\/strong> Masticore<\/a>, Pact of Negation<\/a>, Transguild Promenade<\/a>. We will see the next two sentences detail how to “resolve it”.<\/div>\n
If the triggered ability is a delayed triggered ability that changes the zone of an object, resolve it.<\/p>\n
This type of triggered ability, known as delayed zone-change triggers, frequently exist in order to \u201cclean things up.\u201d While this type of trigger includes a lot of delayed sacrifices of tokens (Kiki-Jiki, Mirror Breaker<\/a>, Thatcher Revolt<\/a>, Geist of Saint Traft<\/a>, etc.), it also includes many abilities that are utterly vital to the continued use of the associated object. For example, the delayed triggered abilities that return \u00c6therling<\/a> and Obzedat, Ghost Council<\/a> to the battlefield are included in this category. These triggers are necessary for the creatures\u2019 controllers to be able to continue using them that game. This will be an important concept shortly. We will see in the next description details on how to “resolve it”.<\/div>\nFor these two types of abilities, the opponent chooses whether to resolve the ability the next time a player would get priority or when a player would get priority at the start of the next phase.<\/p>\n
So the opponent’s choice is for the trigger to occur “now” or “in a moment.” \u201cNever\u201d is not an option for these types of triggers.<\/p>\nNote that policy allows for the object to be returned when a player would get priority at the start of the next phase, and not step. The timing option here allows for a bit of control over creatures appearing and disappearing from the battlefield mid-combat. Putting the control in the hands of the opponent is acceptable because the opponent isn’t the one who missed his or her trigger, and this allows the opponent to minimize the impact of the player \u201csuddenly\u201d remembering the trigger.<\/p>\n
Resolving a delayed zone-change trigger that returns a creature to the battlefield at the start of the next phase means that if a player notices his or her own Missed Trigger during his or her opponent\u2019s end step, the opponent may choose to have the creature remain exiled until the player\u2019s upkeep. That means this creature will have summoning sickness and won\u2019t be able to attack that turn. Of course, an opponent can still opt to have that creature returned to the battlefield when a player got priority during that end of turn step if he or she really wanted to.<\/p>\n
Finally, wherever the opponent chooses to place the trigger, it is resolved immediately, without using the stack. This is to prevent responding to these triggers that should have already happened. You wouldn’t want a pact trigger placed on the stack, then the player casts a card draw spell in response to dig out a Stifle<\/a>, would you?<\/div>\n
These abilities do not expire and should be remedied no matter how much time has passed since they should have triggered.<\/p>\n
Notably, the opponent gets to choose the \u201cwhen,\u201d but not the \u201cif.\u201d One reason for this has to do with the fact that many zone-change triggers are, as pointed out above, utterly vital to the continued use of the associated objects. If an opponent got to choose whether these triggers happened at all, this infraction might be a little too harsh on players who, for example, suddenly find their \u00c6therling<\/a> exiled forever just because they forgot to return it last turn. From the previous section: \u201cTriggered abilities are common and invisible, so players should not be harshly penalized when forgetting about one.\u201d So, policy has to have some special consideration here.<\/p>\nAlso of interest is that even though these abilities don\u2019t expire, players are still under no obligation to remind the opponent of their existence. A player is perfectly within policy by remaining quiet for several turns despite having noticed that his opponent\u2019s Obzedat, Ghost Council<\/a> never returned from exile. And don’t forget the triggers on Pact of Negation<\/a> and his buddies. The default action will be resolved even if it\u2019s remembered two turns later.<\/div>\n
If the ability was missed prior to the current phase in the previous player’s turn, instruct the players to continue playing.<\/p>\n
If it\u2019s been more than a turn since the trigger was missed, the ability is skipped with no further resolution. Remember, though, that if that ability were detrimental for the controlling player, he or she should still receive a penalty no matter how long it\u2019s been.<\/div>\nIf the triggered ability created an effect whose duration has already expired, instruct the players to continue playing.<\/p>\n
For example, if the missed triggered ability lasts \u201cuntil [some amount of time]\u201d or \u201cfor as long as [some condition],\u201d then the ability has a duration. If a Missed Trigger is not noticed until after the amount of time has elapsed or the condition is no longer true, the ability is skipped with no further resolution.<\/p>\nExamples:<\/strong> Battlegrace Angel<\/a>, Colossal Whale<\/a>, Nivix Cyclops<\/a><\/p>\n
If the triggered ability isn\u2019t covered by the previous two paragraphs, the opponent chooses whether the triggered ability is added to the stack.<\/p>\n
So, run through the checks above. If none of them fit, this is our default.<\/p>\n
The opponent should be explicitly asked if he or she would like the ability to go on the stack. Judges should not just assume that players won\u2019t want triggers harmful to them or helpful to an opponent to be skipped, no matter how silly asking might seem.<\/div>\n
If it is, it\u2019s inserted at the appropriate place on the stack if possible or on the bottom of the stack.<\/p>\n
One case in which it might not be possible to insert the trigger in the appropriate place on the stack is if some of the other abilities that triggered at the same time as the Missed Trigger have since resolved and are no longer there.<\/div>\nNo player may make choices involving objects that would not have been legal choices when the ability should have triggered.<\/p>\n
When placing Missed Triggers on the stack, players may make choices only about objects that could have been chosen had the trigger not been missed. Because there is one-turn expiration on placing Missed Triggers on the stack, it\u2019s unlikely that many permanents have moved around in the interim. For this reason, remembering which objects were in which zones shouldn\u2019t be too taxing to either player\u2019s memory.<\/div>\nFor example, if the ability instructs a player to sacrifice a creature, that player can’t sacrifice a creature that wasn’t on the battlefield when the ability should have triggered.<\/p>\n
If a player unintentionally misses his or her own Smokestack<\/a> trigger (At the beginning of each player’s upkeep, that player sacrifices a permanent for each soot counter on Smokestack), but this is not noticed until after the player has moved into his first main phase and played a land, the player should receive a Warning and the opponent should be asked if he or she would like the trigger to go on the stack. If the trigger is placed on the stack, then the player may not choose the land he or she just played for the turn as one of the permanents to sacrifice.<\/div>\n
Upgrade<\/div><\/div><\/h5>\nIf the triggered ability is usually considered detrimental for the controlling player the penalty is a Warning.<\/p>\n
\u201cUsually detrimental\u201d triggers are often all-downside triggers that have been added to some card in order to balance out some other above-the-curve stats or other beneficial effects. Other times, \u201cusually detrimental\u201d triggers are ones that \u201cclean up\u201d a game state by causing the controller to sacrifice some temporarily-created tokens or to give a momentarily nullified permanent back to an opponent.<\/p>\nFurthermore, \u201cusually detrimental\u201d means that you should consider the card associated with the trigger in a vacuum and not take into account any game-specific information in order to determine whether or not a trigger is detrimental. Toby Elliott<\/a>
<\/span><\/span> once said (on his blog<\/a>) that one guideline for making this determination is to ask yourself: \u201cIf the trigger didn’t exist, would the card be played?\u201d If the answer is no, then the ability is probably not detrimental.<\/p>\n
In theory, all triggered abilities in Magic<\/strong> could be classified as either detrimental or non-detrimental \u2014 in fact, a small group of judges are endeavoring to accomplish this very thing with the Missed Trigger Guides project<\/a>.<\/div>\n
The current game state is not a factor in determining this, though symmetrical abilities (such as Howling Mine<\/a>) may be considered usually detrimental or not depending on who is being affected.<\/p>\n
When determining if a trigger is \u2018usually detrimental,\u2019 we do not look at the game state. A Dark Confidant<\/a> trigger at 20 life is the same as a Dark Confidant<\/a> trigger at 1 life. This is because we want consistent rulings and there is no way to take game state into account and have every judge answer the same way.<\/p>\nHowever, we are allowed to consider symmetrical abilities differently based on who is affected. What exactly is a symmetrical ability? Symmetrical abilities are triggered abilities that meet two conditions. They: 1. are likely to trigger multiple times per game, triggering for different players 2. have the same effect on both players.<\/p>\n
Examples include Howling Mine<\/a>, Sulfuric Vortex<\/a>, and Burning Earth<\/a>. A symmetrical ability may either do something positive to both players, or do something negative to both players, but would never do something positive to one player and negative to the other player. Furthermore, a symmetrical ability must have its effect on each player during separate instances of the same ability. For example, Sire of Insanity<\/a>\u2019s triggered ability (At the beginning of each end step, each player discards his or her hand.) is not symmetrical.<\/p>\n
If a player misses a symmetrical trigger that would be either bad for him or her or good for an opponent, he or she should receive a Warning.<\/div>\n","protected":false},"excerpt":{"rendered":"
[cets_callout_box style=’yellow’ align=’right’ title=’Penalty’]None[\/cets_callout_box] Definition A triggered ability triggers, but the player controlling the ability doesn\u2019t demonstrate awareness of the trigger\u2019s existence the first time that it would affect the game in a visible fashion. The point by which the player needs to demonstrate this awareness depends on the impact that the trigger would have […]<\/p>\n","protected":false},"author":13,"featured_media":0,"parent":0,"menu_order":21,"comment_status":"closed","ping_status":"closed","template":"page_width-index.php","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"class_list":["post-37","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/blogs.magicjudges.org\/dev\/wp-json\/wp\/v2\/pages\/37","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.magicjudges.org\/dev\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/blogs.magicjudges.org\/dev\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/dev\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/dev\/wp-json\/wp\/v2\/comments?post=37"}],"version-history":[{"count":21,"href":"https:\/\/blogs.magicjudges.org\/dev\/wp-json\/wp\/v2\/pages\/37\/revisions"}],"predecessor-version":[{"id":86,"href":"https:\/\/blogs.magicjudges.org\/dev\/wp-json\/wp\/v2\/pages\/37\/revisions\/86"}],"wp:attachment":[{"href":"https:\/\/blogs.magicjudges.org\/dev\/wp-json\/wp\/v2\/media?parent=37"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}