16
\$\begingroup\$

If I am under Sanctuary and ready an action to cast a spell such as Shocking Grasp, what actually happens? Sanctuary says:

If the warded creature makes an attack, casts a spell that affects an enemy, or deals damage to another creature, this spell ends

Readying a spell says:

When you ready a spell, you cast it as normal but hold its energy, which you release with your reaction when the trigger occurs. To be readied, a spell must have a casting time of 1 action, and holding onto the spell's magic requires concentration. If your concentration is broken, the spell dissipates without taking effect. For example, if you are concentrating on the web spell and ready magic missile, your web spell ends, and if you take damage before you release magic missile with your reaction, your concentration might be broken.

So since I'm holding the energy of the Shocking Grasp, I believe the spell does not affect its target before its released. Would I be protected by Sanctuary until the readied action takes place? It seems that way to me, but then again the spell is cast and does affect an enemy...it just hasn't affected the enemy yet. I guess it comes down to parsing "a spell that affects an enemy"; does this mean "a spell that, at some point, affects an enemy" or "a spell that affects an enemy in this instance"?

\$\endgroup\$
1

4 Answers 4

14
\$\begingroup\$

You would be protected

For the second condition

casts a spell that affects an enemy

two things need to happen for your protection to lapse: (1) you cast a spell, (2) it affects an enemy. You could for example also cast Evard's Black Tentacles on an area, and the Sanctuary will not end until an enemy gets caught in the effect or someone takes damage from it.

The idea is that Sanctuary shields you as long as you take no directly aggressive actions, and that is technically expressed in the listed conditions. You can see this in the pedigree of the spell, which goes back all the way to first edition (even if it technically does not matter for fifth edition):

During the period of protection afforded by this spell, the cleric cannot take offensive action, but he or she may use non-attack spells or otherwise act in any way which does not violate the prohibition against offensive action.

\$\endgroup\$
8
\$\begingroup\$

It does not say “a spell that can affect an enemy”.

For it to be said that I have “cast a spell that affects an enemy”, I have to actually affect an enemy. If I have affected no enemies, I have not cast a spell that affects an enemy. This would be different if sanctuary said “casts a spell that can affect an enemy”. But it doesn’t say that.

\$\endgroup\$
3
  • \$\begingroup\$ Interesting take on this reading: If I cast an offensive spell but it fails (without the target rolling to make it fail) then I'm good and still protected \$\endgroup\$
    – Hobbamok
    Commented Oct 24, 2022 at 9:20
  • 2
    \$\begingroup\$ @Hobbamok, not necessarily. It's a spell that effects, not a spell that does damage and/or causes a condition. Firing a spell that misses still has an effect. It caused the target to dodge, or bounce off of their armor/shield, use a shield spell, etc. \$\endgroup\$
    – MivaScott
    Commented Oct 24, 2022 at 15:37
  • \$\begingroup\$ It also does not say "a spell that does affect an enemy". 'Affects', by itself, is ambiguous here. \$\endgroup\$
    – Kirt
    Commented Mar 26 at 15:07
7
\$\begingroup\$

By comparing to a similar case, sanctuary ends when the spell is cast

The following question already exists:

Comparing the wording of Overchannel and sanctuary then:

If the warded creature [...] casts a spell that affects an enemy

When you cast a wizard spell [...] that deals damage

All three positively-scoring answers there state that Overchannel is decided when the spell is cast and not when it deals damage. To quote the highest-scoring one:

If it was meant to be decided after it had dealt damage, it would have to use wording like "When you cast a wizard spell of 5th level or lower and deal damage".

I believe the exact same case can then be made for sanctuary. Whether or not sanctuary ends is determined when you cast the spell and thus we must decide whether the spell affects a creature at the moment it is cast. Just like with Overchanneling, this would be determined based on whether or not we expect the spell to affect a creature, given its description. The shocking grasp spell certainly expects a target, so I would rule that sanctuary ends the moment you ready it.


Other similar cases:

\$\endgroup\$
0
\$\begingroup\$

That vs. which

Casual users of English (including myself, in everyday conversation) use "that" and "which" to introduce clauses largely interchangeably. But there actually is a difference between their formal grammatical meanings. If you believe that the writers of the sanctuary spell's text kept this difference in mind, and used the words they did intentionally, that alone is enough to settle this question.

'That' opens a restrictive clause

'That' is used to introduce a clause setting apart its specific members as being distinct from a larger group. The clause

casts a spell that affects an enemy

means "casts a spell, of the type of spells capable by design of affecting others". Whether or not the spell subsequently results in an enemy being affected is immaterial; "that" is simply identifying the class of spell to which shocking grasp belongs. Shocking grasp is the type of spell that affects others, and the spell is cast when the readied action is taken. Thus sanctuary would drop the moment it was cast, on the caster's turn.

'Which' opens a nonrestrictive clause

'Which' is used to introduce a clause describing what is incidentally particular to a specific member of a group without defining it as categorically distinct from a larger group. If the sanctuary spell had instead read:

casts a spell which affects an enemy

it would mean "casts a spell, as it happens to have turned out, resulting in an enemy being affected". Whether or not the spell does result in an enemy being affected is crucial; "which" does not identify the class of spell to which shocking grasp belongs, but rather indicates that sanctuary would drop the moment it actually does affect an enemy.

By selecting "that" rather than "which", the writers of the sanctuary spell are indicating that sanctuary is reacting to the kind of spell cast, not what its subsequent effects actually are. However, that indication may not have been intentional, as the PHB does not always follow the rules of formal prescriptive grammar. To the extent that you believe that the PHB is using grammar intentionally, the sanctuary spell would drop as soon as the readied shocking grasp was cast, and before it could be held.

\$\endgroup\$
7
  • 1
    \$\begingroup\$ I thought about if this after all could be the right answer. Dictionary provides a test: if you leave out a "that" clause, it changes what's inlcuded, if you leave out a "which" clause, it doesn't. Here, leaving out the clause would make it trigger on any spell, so it's restrictive, as you say. But restricted to what? It does not say "that can affect a creature" (see @Dale's answer), it says "that affects a creature". I believe the restricition comes only into play if the spell actually affects a creature, yet it still is a restrictive clause. \$\endgroup\$ Commented Nov 3 at 8:59
  • \$\begingroup\$ Is "affects" is more likely "does affect" or "can affect"? I'm not a native speaker, but asking ChatGPT, it tells me that there is no semantic difference between "does affect" and "affects", other than emphasis and tone, i.e. "affects" states the fact plainly, while "does affect" underscores this fact with more emphasis. \$\endgroup\$ Commented Nov 3 at 9:06
  • \$\begingroup\$ @NobodytheHobgoblin 'Affects', by itself, is perfectly ambiguous. It could mean either 'does affect' or 'can effect', and those helping verbs can be added when you want to clarify meaning. Without them, we are left with 'that' vs 'which', and 'that' tells us it is restrictive. You are correct, 'that' could be telling us it is restricted to spells that actually do affect enemies. However, interpreting it that when then creates a further ambiguity. \$\endgroup\$
    – Kirt
    Commented Nov 3 at 15:35
  • 1
    \$\begingroup\$ @NobodytheHobgoblin If sanctuary drops on a spell that does affect an enemy, does that apply only when the spell is cast? Or does my sanctuary drop if I cast a spell that later affects an enemy, as in this case with a readied spell. Or say I cast web and only three turns later someone stumbles into it, does my sanctuary drop at the subsequent moment the spell I cast affects a foe? Given a choice between an interpretation that clearly covers every situation and an interpretation that just raises more questions, I prefer the former. \$\endgroup\$
    – Kirt
    Commented Nov 3 at 15:40
  • \$\begingroup\$ That is a perfectly reasonable way to handle it and I see no issues from doing so. (I do it as I say in my answer: if an enemy -however that is defined, but not e.g. one of your allies- stumbles into your web later on, then you cast a spell that affected an enemy and the sanctuary drops. Which in my experience also causes no problems.) My comment was less about how it plays, and more on the grammatical range of meaning of "affects", which a LLM tells me is more like does affect than can affect, but of course, a LLM might just be wrong on that, too. \$\endgroup\$ Commented Nov 3 at 17:51

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .