General Rulings - 405

• 405.1 - When a spell is cast, the physical card is put on the stack (see Rule 601.2a). When an ability is activated or triggers, it goes on top of the stack without any card associated with it (see Rule 602.2a and Rule 603.3). [CompRules 2009/07/08]
• 405.2 - The stack keeps track of the order that spells and/or abilities were added to it. Each time an object is put on the stack, it's put on top of all objects already there. [CompRules 2009/07/08]
• 405.3 - If an effect puts two or more objects on the stack at the same time, those controlled by the active player are put on lowest, followed by each other player's objects in APNAP order (see Rule 101.4). If a player controls more than one of these objects, that player chooses their relative order on the stack. [CompRules 2009/07/08]
• 405.4 - Each spell has all the characteristics of the card associated with it. Each activated or triggered ability that's on the stack has the text of the ability that created it and no other characteristics. The controller of a spell is the person who cast the spell. The controller of an activated ability is the player who activated the ability. The controller of a triggered ability is the player who controlled the ability's source when it triggered, unless it's a delayed triggered ability. The controller of a delayed triggered ability is the player who controlled the spell or ability that created it. [CompRules 2009/07/08]
• 405.5 - When all players pass in succession, the top (last-added) spell or ability on the stack resolves. If the stack is empty when all players pass, the current step or phase ends and the next begins. [CompRules 2009/07/08]
• 405.6 - Some things that happen during the game don't use the stack. [CompRules 2009/07/08]
• 405.6a - Effects don't go on the stack; they're the result of spells and abilities resolving. Effects may create delayed triggered abilities, however, and these may go on the stack when they trigger (see Rule 603.7). [CompRules 2009/07/08]
• 405.6b - Static abilities continuously generate effects and don't go on the stack. (See Rule 604, "Handling Static Abilities.") This includes characteristic-defining abilities such as "<-This object-> is red" (see Rule 604.3). [CompRules 2009/07/08]
• 405.6c - Mana abilities resolve immediately. If a mana ability produces both mana and another effect, both the mana and the other effect happen immediately. If a player had priority before a mana ability was activated, that player gets priority after it resolves. (See Rule 605, "Mana Abilities.") [CompRules 2009/10/01]
• 405.6d - Special actions don't use the stack; they happen immediately. See Rule 114, "Special Actions." [CompRules 2009/07/08]
• 405.6e - Turn-based actions don't use the stack; they happen automatically when certain steps or phases begin. They're dealt with before a player would receive priority (see Rule 115.3a). Turn-based actions also happen automatically when each step and phase ends; no player receives priority afterward. See Rule 703. [CompRules 2009/07/08]
• 405.6f - State-based actions don't use the stack; they happen automatically when certain conditions are met. See Rule 704. They are dealt with before a player would receive priority. See Rule 115.5. [CompRules 2009/07/08]
• 405.6g - A player may concede the game at any time. That player leaves the game immediately. See Rule 104.3a. [CompRules 2009/07/08]
• 405.6h - If a player leaves a multiplayer game, objects may leave the game, cease to exist, change control, or be exiled as a result. These actions happen immediately. See Rule 800.4a. [CompRules 2009/07/08]