Discussion Forum

the flanking will stack but the first strike will not become double those are completely seperate abilities

Waahhhh??? NO NO NO....I demand a recount!!!:mad:

sorry lol it does not to dissapoint if she has multiple poison slivers out they stack too

just make a sliver deck yourself, then the flanking won't work. :P

Sliver vs. Sliver???? Saw it once, my head exploded!:eek:

My red/white Knights have flanking too

Flanking is a simple triggered ability. If there are multiple instances of it, each will trigger separately, and each will give the blocking nonflanking creature(s) -1/-1 when it resolves.

Double strike, on the other hand, is an ability that allows a creature to participate in both the first strike combat damage step and the normal combat damage step. Each of those steps only occurs once, though, and one instance of double strike is all a creature needs to join in on both. There's nothing more for further instances of double strike to do.


Relevant rules:

702.22. Flanking

702.22a Flanking is a triggered ability that triggers during the declare blockers step. (See rule 509, “Declare Blockers Step.”) “Flanking” means “Whenever this creature becomes blocked by a creature without flanking, the blocking creature gets -1/-1 until end of turn.”

702.22b If a creature has multiple instances of flanking, each triggers separately.


702.4. Double Strike

702.4a Double strike is a static ability that modifies the rules for the combat damage step. (See rule 510, “Combat Damage Step.”)

702.4b If at least one attacking or blocking creature has first strike (see rule 702.7) or double strike as the combat damage step begins, the only creatures that assign combat damage in that step are those with first strike or double strike. After that step, instead of proceeding to the end of combat step, the phase gets a second combat damage step. The only creatures that assign combat damage in that step are the remaining attackers and blockers that had neither first strike nor double strike as the first combat damage step began, as well as the remaining attackers and blockers that currently have double strike. After that step, the phase proceeds to the end of combat step.

702.4c Removing double strike from a creature during the first combat damage step will stop it from assigning combat damage in the second combat damage step.

702.4d Giving double strike to a creature with first strike after it has already dealt combat damage in the first combat damage step will allow the creature to assign combat damage in the second combat damage step.

702.4e Multiple instances of double strike on the same creature are redundant.