Rule evolution
Rule 303.4d
Previously numbered 303.4c.
Earliest archived Rules release: 2009-10-01 · 1 wording revision · 1 renumbering
Earliest archived Rules release303.4cDetails
An Aura can't enchant itself. If this occurs somehow, the Aura is put into its owner's graveyard. An Aura that's also a creature can't enchant anything. If this occurs somehow, the Aura becomes unattached, then is put into its owner's graveyard. (These are state-based actions. See rule 704.)
Renumbered
303.4c→ 303.4dDetailsPreviously
3. Card Types
303. EnchantmentsThen
3. Card Types
303. EnchantmentsAn Aura can't enchant itself. If this occurs somehow, the Aura is put into its owner's graveyard. An Aura that's also a creature can't enchant anything. If this occurs somehow, the Aura becomes unattached, then is put into its owner's graveyard. (These are state-based actions. See rule 704.)
Wording changed303.4dDetails
An Aura can't enchant itself. If this occurs somehow, the Aura is put into its owner's graveyard. An Aura that's also a creature can't enchant anything. If this occurs somehow, the Aura becomes unattached, then is put into its owner's graveyard. (These are state-based actions. See rule 704.) An Aura can't enchant more than one object or player. If a spell or ability would cause an Aura to become attached to more than one object or player, the Aura's controller chooses which object or player it becomes attached to.