Legendary Enchantment // Legendary Land
When Path of Mettle enters, it deals 1 damage to each creature that doesn't have first strikeFirst strike is a static ability that modifies the rules for the combat damage step. (See rule 510, “Combat Damage Step.”)
If at least one attacking or blocking creature has first strike or double strike (see rule 702.4) 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.
Giving first strike to a creature without it after combat damage has already been dealt in the first combat damage step won’t preclude that creature from assigning combat damage in the second combat damage step. Removing first strike from a creature after it has already dealt combat damage in the first combat damage step won’t allow it to also assign combat damage in the second combat damage step (unless the creature has double strike).
Multiple instances of first strike on the same creature are redundant. (CR 702.7), double strikeDouble strike is a static ability that modifies the rules for the combat damage step. (See rule 510, “Combat Damage Step.”)
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.
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.
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.
Multiple instances of double strike on the same creature are redundant. (CR 702.4), vigilanceVigilance is a static ability that modifies the rules for the declare attackers step.
Attacking doesn’t cause creatures with vigilance to tap. (See rule 508, “Declare Attackers Step.”)
Multiple instances of vigilance on the same creature are redundant. (CR 702.20), or hasteHaste is a static ability.
If a creature has haste, it can attack even if it hasn’t been controlled by its controller continuously since their most recent turn began. (See rule 302.6.)
If a creature has haste, its controller can activate its activated abilities whose cost includes the tap symbol or the untap symbol even if that creature hasn’t been controlled by that player continuously since their most recent turn began. (See rule 302.6.)
Multiple instances of haste on the same creature are redundant. (CR 702.10).
Whenever you attack with at least two creatures that have first strikeFirst strike is a static ability that modifies the rules for the combat damage step. (See rule 510, “Combat Damage Step.”)
If at least one attacking or blocking creature has first strike or double strike (see rule 702.4) 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.
Giving first strike to a creature without it after combat damage has already been dealt in the first combat damage step won’t preclude that creature from assigning combat damage in the second combat damage step. Removing first strike from a creature after it has already dealt combat damage in the first combat damage step won’t allow it to also assign combat damage in the second combat damage step (unless the creature has double strike).
Multiple instances of first strike on the same creature are redundant. (CR 702.7), double strikeDouble strike is a static ability that modifies the rules for the combat damage step. (See rule 510, “Combat Damage Step.”)
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.
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.
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.
Multiple instances of double strike on the same creature are redundant. (CR 702.4), vigilanceVigilance is a static ability that modifies the rules for the declare attackers step.
Attacking doesn’t cause creatures with vigilance to tap. (See rule 508, “Declare Attackers Step.”)
Multiple instances of vigilance on the same creature are redundant. (CR 702.20), and/or hasteHaste is a static ability.
If a creature has haste, it can attack even if it hasn’t been controlled by its controller continuously since their most recent turn began. (See rule 302.6.)
If a creature has haste, its controller can activate its activated abilities whose cost includes the tap symbol or the untap symbol even if that creature hasn’t been controlled by that player continuously since their most recent turn began. (See rule 302.6.)
Multiple instances of haste on the same creature are redundant. (CR 702.10), transformTo transform a permanent, turn it over so that its other face is up. Only permanents represented by double-faced tokens and double-faced cards can transform. (See rule 712, “Double-Faced Cards.”)
Although transforming a permanent uses the same physical action as turning a permanent face up or face down, they are different game actions. Abilities that trigger when a permanent is turned face down won’t trigger when that permanent transforms, and so on.
If a spell or ability instructs a player to transform a permanent that isn’t represented by a double-faced token or a double-faced card, nothing happens.
If a spell or ability instructs a player to transform a permanent, and the face that permanent would transform into is an instant or sorcery face nothing happens.
Some triggered abilities trigger when an object “transforms into” an object with a specified characteristic. Such an ability triggers if the object either transforms or converts (see rule 701.28) and has the specified characteristic immediately after it does so.
If an activated or triggered ability of a permanent that isn’t a delayed triggered ability of that permanent tries to transform it, the permanent does so only if it hasn’t transformed or converted since the ability was put onto the stack. If a delayed triggered ability of a permanent tries to transform that permanent, the permanent does so only if it hasn’t transformed or converted since that delayed triggered ability was created. In both cases, if the permanent has already transformed or converted, an instruction to do either is ignored.
Some spells and abilities refer to a “transformed permanent.” This phrase refers to a double-faced permanent on the battlefield with its back face up. A permanent with its front face up is never considered a transformed permanent, even if it had its back face up previously. Similarly, an object represented by more than one card, such as a melded or merged permanent, is never considered a transformed permanent, even if it has components that are back face up. See rules 701.42, “Meld,” and 730, “Merging with Permanents.” (CR 701.27) Path of Mettle. // (Transforms from Path of Mettle.)
: Add one mana of any color.
, : Metzali deals 2 damage to each opponent.
, : Choose a creature at random that attacked this turn. DestroyThe only ways a permanent can be destroyed are as a result of an effect that uses the word “destroy” or as a result of the state-based actions that check for lethal damage (see rule 704.5g) or damage from a source with deathtouch (see rule 704.5h). If a permanent is put into its owner’s graveyard for any other reason, it hasn’t been “destroyed.”
A regeneration effect replaces a destruction event. See rule 701.19, “Regenerate.” (CR 701.8) that creature.
$0.36
Commander: LegalModern: Legal
Save this card
Log in to save cards to your lists.
Start a deck with this cardTags and classifications
Card attributes are distinct from extracted ability facts and inferred themes. AI themes and predicted tags are suggestions, not rules text.
Ability tags
Mana costs
Color identity
Keyword tags
Mana value
Timing tags
Type tags
Predicted tags are currently unavailable.
