Rule evolution
Rule 303.4i
Previously numbered 303.4h.
Earliest archived Rules release: 2009-10-01 · 3 wording revisions · 1 renumbering
Earliest archived Rules release303.4hDetails
If an effect attempts to attach an Aura on the battlefield to an object or player, that object or player must be able to be enchanted by it. If the object or player can't be, the Aura doesn't move.
Renumbered
303.4h→ 303.4iDetailsPreviously
3. Card Types
303. EnchantmentsThen
3. Card Types
303. EnchantmentsIf an effect attempts to attach an Aura on the battlefield to an object or player, that object or player must be able to be enchanted by it. If the object or player can't be, the Aura doesn't move.
Wording changed303.4iDetails
If an effect attempts to attach an Aura on the battlefield to an object or player, that object or player must be able to be enchanted by it.If an effect attempts to put an Aura onto the battlefield enchanting an object or player it can't legally enchant, the Aura remains in its current zone.If the object or player can't be, the Aura doesn't move.Wording changed303.4iDetails
If an effect attempts to put an Aura onto the battlefield
enchantingattached to an object or player it can't legally enchant, the Aura remains in its current zone, unless that zone is the stack. In that case, the Aura is put into its owner's graveyard instead of entering the battlefield. If the Aura is a token, it isn't created.Wording changed303.4iDetails
If an effect attempts to put an Aura onto the battlefield attached to either an object or player it can't legally enchant or an object or player that is undefined, the Aura remains in its current zone, unless that zone is the stack. In that case, the Aura is put into its owner's graveyard instead of entering the battlefield. If the Aura is a token, it isn't created.