MTG Salvation

Quote from MaRo »

Q: So there aren't any ... green ninjas?

No.

Quote from leonin_god »

...i was on holidays so could someone fill me in as to why 'news went downhill all of a sudden?

306. Combat Phase

306.1. The combat phase has five steps, which proceed in order: beginning of combat, declare attackers, declare blockers, combat damage, and end of combat. The declare blockers and combat damage steps are skipped if no creatures are declared as attackers (see rule 308.4). There are two combat damage steps if any attacking or blocking creature has first strike (see rule 502.2) or double strike (see rule 502.28).

306.2. A creature is removed from combat if it leaves play (such as by being destroyed or removed from the game), if it regenerates (see rule 419.6b), if its controller changes, if it stops being a creature, or if an effect removes it from combat. Removed from combat means the creature stops being an attacking, blocking, blocked, and/or unblocked creature.

306.2a Once a creature has been declared as an attacking or blocking creature, spells or abilities that would have kept that creature from attacking or blocking don't remove the creature from combat.

306.2b Tapping or untapping a creature that's already been declared as an attacker or blocker doesn't remove it from combat and doesn't prevent its combat damage.

306.3. During the combat phase, the active player is attacking and is the attacking player. The nonactive player is being attacked and is the defending player.

306.4. An attacking creature is attacking alone if no other creatures are attacking. A blocking creature is blocking alone if no other creatures are blocking.

307. Beginning of Combat Step

307.1. As the beginning of combat step begins, any abilities that trigger at the beginning of combat go on the stack. (See rule 410, "Handling Triggered Abilities.") Then the active player gets priority and players may play spells and abilities.

308. Declare Attackers Step

308.1. As the declare attackers step begins, the active player declares attackers (this game action doesn't use the stack). Then any abilities that triggered on attackers being declared go on the stack. (See rule 410, "Handling Triggered Abilities.") Then the active player gets priority and players may play spells and abilities.

308.2. To declare attackers, the active player follows the steps below, in order. If at any point during the declaration of attackers, the active player is unable to comply with any of the steps listed below, the declaration was illegal; the game returns to the moment before the declaration (see rule 422, "Handling Illegal Actions," and rule 500, "Legal Attacks and Blocks").

308.2a The active player either chooses to not attack, or chooses one or more creatures he or she controls and then determines whether this set of creatures could attack. Only creatures can attack, and the following creatures can't attack: tapped creatures (even those that can attack without tapping) and creatures the active player didn't control continuously since the beginning of the turn (except those with haste). Other effects may also affect whether or not a set of creatures could attack. (See rule 500, "Legal Attacks and Blocks.")

308.2b If any of the chosen creatures have banding or a bands with other ability, the active player announces which creatures, if any, are banded with which. (See rule 502.10, "Banding.")

308.2c The active player taps the chosen creatures. Tapping a creature when it's declared as an attacker isn't a cost; attacking simply causes creatures to become tapped.

308.2d If any of the creatures require paying costs to attack, the active player determines the total cost to attack. Costs may include paying mana, tapping permanents, sacrificing permanents, discarding cards, and so on. Once the total cost is determined, it becomes "locked in." If effects would change the total cost after this time, ignore this change.

308.2e If any of the costs require mana, the active player then has a chance to play mana abilities (see rule 411, "Playing Mana Abilities").

308.2f Once the player has enough mana in his or her mana pool, he or she pays all costs in any order. Partial payments are not allowed.

308.2g Each chosen creature becomes an attacking creature if all costs have been paid, but only if it's still controlled by the active player. It remains an attacking creature until it's removed from combat or the combat phase ends, whichever comes first. See rule 306.2.

308.3. Abilities that trigger on a creature attacking trigger only at the point the creature starts to attack. They will not trigger if a creature attacks and the characteristics of that creature are then changed to match the ability's trigger condition.
Example: A permanent has the ability "Whenever a green creature attacks, destroy that creature at end of combat." If a blue creature attacks and is later turned green, the ability will not trigger.

308.4. If no creatures are declared as attackers, finish the declare attackers step, but skip the declare blockers and combat damage steps.

309. Declare Blockers Step

309.1. As the declare blockers step begins, the defending player declares blockers (this game action doesn't use the stack). Then any abilities that triggered on blockers being declared go on the stack. (See rule 410, "Handling Triggered Abilities.") Then the active player gets priority and players may play spells and abilities.

309.2. To declare blockers, the defending player follows the steps below, in order. If at any point during the declaration of blockers, the defending player is unable to comply with any of the steps listed below, the declaration was illegal; the game returns to the moment before the declaration (see rule 422, "Handling Illegal Actions," and rule 500, "Legal Attacks and Blocks").

309.2a The defending player chooses zero or more creatures he or she controls, chooses one attacking creature for each one to block, then determines whether this set of blocks is legal. Only untapped creatures can block, but blocking does not cause creatures to tap. Other effects may also affect whether or not a set of creatures could block. (See rule 500, "Legal Attacks and Blocks.")

309.2b If any of the creatures require paying costs to block, the defending player determines the total cost to block. Costs may include paying mana, tapping permanents, sacrificing permanents, discarding cards, and so on. Once the total cost is determined, it becomes "locked in." If effects would change the total cost after this time, ignore this change.

309.2c If any of the costs require mana, the defending player then has a chance to play mana abilities (see rule 411, "Playing Mana Abilities").

309.2d Once the player has enough mana in his or her mana pool, he or she pays all costs in any order. Partial payments are not allowed.

309.2e Each chosen creature becomes a blocking creature, but only if it's controlled by the defending player. Each one is blocking the attacking creature chosen for it. It remains a blocking creature until it's removed from combat or the combat phase ends, whichever comes first. See rule 306.2.

309.2f An attacking creature with one or more creatures declared as blockers for it becomes a blocked creature; one with no blockers becomes an unblocked creature. The creature's status remains unchanged until the creature is removed from combat or the combat phase ends, whichever comes first. (Some effects can change a creature's status.)

309.3. Abilities that trigger on a creature blocking or becoming blocked trigger only at the point the creature blocks or becomes blocked. They will not trigger if a creature blocks or becomes blocked, and then the characteristics of that creature are changed to match the ability's trigger condition.
Example: A creature has the ability "Whenever this creature becomes blocked by a white creature, destroy that creature at end of combat." If that creature is blocked by a black creature that is later turned white, the ability will not trigger.

310. Combat Damage Step

310.1. As the combat damage step begins, the active player announces how each attacking creature will assign its combat damage. Then the defending player announces how each blocking creature will assign its combat damage. All assignments of combat damage go on the stack as a single object. Then any abilities that triggered on damage being assigned go on the stack. (See rule 410, "Handling Triggered Abilities.") Then the active player gets priority and players may play spells and abilities.

310.2. A player may divide a creature's combat damage as he or she chooses among the legal recipients. Dividing combat damage is subject to the following restrictions:

310.2a Each attacking creature and each blocking creature will assign combat damage equal to its power. Creatures with 0 or less power don't assign combat damage.

310.2b An unblocked attacking creature will assign all its combat damage to the defending player.

310.2c A blocked creature will assign combat damage, divided as its controller chooses, to the creatures blocking it. If no creatures are currently blocking it (if, for example, they were destroyed or removed from combat), it will assign no combat damage.
310.2d A blocking creature will assign combat damage, divided as its controller chooses, to the attacking creatures it's blocking. If it isn't currently blocking any creatures (if, for example, they were destroyed or removed from combat), it will assign no combat damage.

310.2e An effect that states a creature deals its combat damage in a different manner than normal affects the assignment of combat damage.

310.3. Although combat-damage assignments go on the stack as an object, they aren't spells or abilities, so they can't be countered.

310.4. Combat damage resolves as an object on the stack. When it resolves, it's all dealt at once, as originally assigned. After combat damage finishes resolving, the active player gets priority.

310.4a Combat damage is dealt as it was originally assigned even if the creature dealing damage is no longer in play, its power has changed, or the creature receiving damage has left combat.

310.4b The source of the combat damage is the creature as it currently exists, or as it most recently existed if it is no longer in play.

310.4c If a creature that was supposed to receive combat damage is no longer in play or is no longer a creature, the damage assigned to it isn't dealt.

310.5. At the start of the combat damage step, if at least one attacking or blocking creature has first strike (see rule 502.2) or double strike (see rule 502.28), creatures without first strike or double strike don't assign combat damage. Instead of proceeding to end of combat, the phase gets a second combat damage step to handle the remaining creatures. In the second combat damage step, surviving attackers and blockers that didn't assign combat damage in the first step, plus any creatures with double strike, assign their combat damage.

311. End of Combat Step

311.1. All "at end of combat" abilities trigger and go on the stack. (See rule 410, "Handling Triggered Abilities.") Then the active player gets priority and players may play spells and abilities.

311.2. As soon as the end of combat step ends, all creatures are removed from combat. After the end of combat step ends, the combat phase is over and the postcombat main phase begins.

Quote from "Anno" »

So I posted an argument without reading what I was ranting against. Shoot me.

Quote from Shivan19532 »

Well Woman. I am woman hear me ROAR!