Enchantment — Aura Cartouche
EnchantEnchant is a static ability, written “Enchant [object or player].” The enchant ability restricts what an Aura spell can target and what an Aura can enchant.
For more information about Auras, see rule 303, “Enchantments.”
If an Aura has multiple instances of enchant, all of them apply. The Aura’s target must follow the restrictions from all the instances of enchant. The Aura can enchant only objects or players that match all of its enchant abilities.
Auras that can enchant a player can target and be attached to players. Such Auras can’t target permanents and can’t be attached to permanents. (CR 702.5) creature you control
When this Aura enters, createTo create one or more tokens with certain characteristics, put the specified number of tokens with the specified characteristics onto the battlefield.
If a replacement effect applies to a token being created, that effect applies before considering any continuous effects that will modify the characteristics of that token. If a replacement effect applies to a token entering the battlefield, that effect applies after considering any continuous effects that will modify the characteristics of that token.
Previously, an effect that created tokens instructed a player to “put [those tokens] onto the battlefield.” Cards that were printed with that text have received errata in the Oracle card reference so they now “create” those tokens. (CR 701.7) a 1/1 white Warrior creature token with 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).
Enchanted creature gets +1/+1 and has 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). (It deals combat damage before creatures without 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).)
$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
Theme tags
Timing tags
Type tags
Predicted tags are currently unavailable.
