General Rulings - 303

• 303.1 - A player who has priority may cast an enchantment card from his or her hand during a main phase of his or her turn when the stack is empty. Casting an enchantment as a spell uses the stack. (See Rule 601, "Casting Spells.") [CompRules 2009/07/08]
• 303.2 - When an enchantment spell resolves, its controller puts it onto the battlefield under his or her control. [CompRules 2009/07/08]
• 303.3 - Enchantment subtypes are always a single word and are listed after a long dash: "Enchantment -- Shrine." Each word after the dash is a separate subtype. Enchantment subtypes are also called enchantment types. Enchantments may have multiple subtypes. See Rule 204.3g for the complete list of enchantment types. [CompRules 2009/07/08]
• 303.4 - Some enchantments have the subtype "Aura." An Aura enters the battlefield attached to an object or player. What an Aura can be attached to is restricted by its enchant keyword ability (see Rule 702.5, "Enchant"). Other effects can limit what a permanent can be enchanted by. [CompRules 2009/07/08]
• 303.4a - An Aura spell requires a target, which is restricted by its enchant ability. [CompRules 2009/07/08]
• 303.4b - If an Aura is enchanting an illegal object or player, the object it was attached to no longer exists, or the player it was attached to has left the game, the Aura is put into its owner's graveyard. (This is a state-based action. See Rule 704.) [CompRules 2009/07/08]
• 303.4c - 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 a state-based actions. See Rule 704.) [CompRules 2009/10/01]
• 303.4d - The object or player an Aura is attached to is called enchanted. The Aura is attached to, or "enchants," that object or player. [CompRules 2009/07/08]
• 303.4e - An Aura's controller is separate from the enchanted object's controller or the enchanted player; the two need not be the same. If an Aura enchants and object, changing control of the object doesn't change control of the Aura, and vice versa. Only the Aura's controller can activate its abilities. However, if the Aura grants an ability to the enchanted object (with "gains" or "has"), the enchanted object's controller is the only one who can activate that ability. [CompRules 2009/10/01]
• 303.4f - If an Aura is entering the battlefield under a player's control by any means other than by resolving as an Aura spell, and the effect putting it onto the battlefield doesn't specify the object or player the Aura will enchant, that player chooses what it will enchant as the Aura enters the battlefield. The player must choose a legal object or player according to the Aura's enchant ability and any other applicable effects. [CompRules 2009/07/08]
• 303.4g - If an Aura is entering the battlefield and there is no legal object or player for it to 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. [CompRules 2009/07/08]
• 303.4h - 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. [CompRules 2009/07/08]