17

You control a Steel Golem, which says "you can't cast creature spells". Can you pay the Bestow cost on, say, a Hopeful Eidolon, and cast it as an aura enchanting the Steel Golem?

My reading of the rules is that you can't: Paying the bestow cost doesn't make the card into a (non-creature) Aura until after it's on the stack, and Steel Golem's restriction doesn't let you put a creature spell on the stack.

In general the ordering of steps in casting a spell is:

  1. Choose a spell to play and place it on the stack.
  2. Choose modes and targets.
  3. Choose which costs to pay and pay them.

When applied to a Bestow spell, these become:

  1. Place the bestow creature on the stack.
  2. (No modes or targets to choose yet, since it's a creature spell).
  3. Choose to pay the bestow cost.
  4. The spell stops being a creature and becomes an Aura (702.102a).
  5. The spell's controller chooses a target (702.102b).

But if "you can't cast creature spells", then you can't complete step 1, since your Hopeful Eidolon is still a creature. And (per 601.2) "If, at any point during the casting of a spell, a player is unable to comply with any of the steps listed below, the casting of the spell is illegal".

(The converse situation seems to arise with Aurelia's Fury, where a Bestow card is playable because it's not a noncreature card until after the Bestow cost is payed.)

Does this sound correct or am I missing something?

13

Under the current rules, you can bestow despite "you can't cast creature spells."

The rules changed in the Magic Origins rules update to tweak the spell casting procedure and also to address the bestow interaction explicitly.

Matt Tabak (then the rules manager) writes:

I made some tweaks to the procedure of casting a spell or activating an ability. It basically boils down to the proposal of the spell, including making all necessary choices such as modes and targets. Then the game checks to see if what you've proposed is legal. Finally, assuming the spell is legal, you calculate and pay costs. In practice, not much is changing. Bestow gets a little easier to figure out. For example, if an effect stops you from casting creature spells, you can still cast one as an Aura. There are some strange cases with things like split cards or flash that become a bit clearer as well.

(emphasis mine) and

We've deleted [rule 601.5] that says you can't begin to cast a spell that's prohibited from being cast. The legality check now happens at one defined point, according to the changes to rule 601.2. [...]

The updated rules now include 702.102c which explicitly addresses this interaction:

702.102c. The check for whether a spell can legally be cast happens after its controller has chosen whether to pay its bestow cost; see rule 601.2e.

Example: Aether Storm is an enchantment with the ability "Creature spells can’t be cast." This effect doesn't stop a creature card with bestow from being cast for its bestow cost because the spell is an Aura enchantment spell, not an enchantment creature spell, when the game checks whether the spell is illegal.

8

601.5. A player can’t begin to cast a spell that’s prohibited from being cast.

So you are exactly right

EDIT: not correct anymore

  • 3
    Important missing bit: "You don’t choose whether the spell is going to be an Aura spell or not until the spell is already on the stack. [...]" (from the rulings) – ikegami Oct 7 '14 at 17:22
  • This rule no longer exists. – doppelgreener Apr 10 '18 at 7:41
  • @doppelgreener ok. what do you propose I do? delete my answer? – Ivo Beckers Apr 10 '18 at 7:43
  • I think the options come down to requesting moderator attention to have the answer removed, or updating this answer to beat the other one describing the current changes. It's a tough spot to be put in. 🤔 – doppelgreener Apr 10 '18 at 7:53
  • 1
    Or actually also leave the answer be and let it get outvoted is another. I mainly left the comment I did as a signpost to future viewers, because I saw the answer get an upvote (but I don't think that would be correct, given the answer isn't factually correct anymore, though through no fault of yours). – doppelgreener Apr 10 '18 at 8:12

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.