What happens when you cast Fog Cloud behind a wall?
Clash Royale CLAN TAG#URR8PPP
$begingroup$
I'm puzzled by the "a clear path to the target" rule.
To target something, you must have a clear path to it, so it can't be behind total cover.
This seems straightforward: you can't target a point/creature/object/thing behind total cover. But then the rule adds the following:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
And now suddenly I'm lost. You can't do A, but if you do, then B happens.
Let's assume a blind wizard stuck is in a maze, facing a wall he's not aware of. He's trying to cast fog cloud behind it.
How should the DM react, according to the rules?
I mostly see 3 options (but feel free to add others):
"No you can't. Choose another target / action."
This is the strict application of the rule's first sentence.
"Even though you placed your spell 60 feet away, you feel a strong humidity on your skin. It looks like the fog cloud appeared closer than what you intended."
This would be the application of the rule's second sentence.
"You say the words and do the gestures, but nothing happens."
As found here, Xanathar's Guide to Everything offers optional rules for invalid targets — that you can use... if you feel this falls into invalid targeting.
What bothers me is that the first option seemed to have an broad consensus (~90 person before the associated answer update): not only does it render the second sentence obsolete, but it allows the player to gain information on it's environment without spending actions. Suddenly, the wizard gains some kind of radar that allows him to check if the path in front of him is free, and circulate quickly in a maze made of prismatic walls without harm. This can't be right... right?
dnd-5e spells targeting cover line-of-effect
$endgroup$
add a comment |
$begingroup$
I'm puzzled by the "a clear path to the target" rule.
To target something, you must have a clear path to it, so it can't be behind total cover.
This seems straightforward: you can't target a point/creature/object/thing behind total cover. But then the rule adds the following:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
And now suddenly I'm lost. You can't do A, but if you do, then B happens.
Let's assume a blind wizard stuck is in a maze, facing a wall he's not aware of. He's trying to cast fog cloud behind it.
How should the DM react, according to the rules?
I mostly see 3 options (but feel free to add others):
"No you can't. Choose another target / action."
This is the strict application of the rule's first sentence.
"Even though you placed your spell 60 feet away, you feel a strong humidity on your skin. It looks like the fog cloud appeared closer than what you intended."
This would be the application of the rule's second sentence.
"You say the words and do the gestures, but nothing happens."
As found here, Xanathar's Guide to Everything offers optional rules for invalid targets — that you can use... if you feel this falls into invalid targeting.
What bothers me is that the first option seemed to have an broad consensus (~90 person before the associated answer update): not only does it render the second sentence obsolete, but it allows the player to gain information on it's environment without spending actions. Suddenly, the wizard gains some kind of radar that allows him to check if the path in front of him is free, and circulate quickly in a maze made of prismatic walls without harm. This can't be right... right?
dnd-5e spells targeting cover line-of-effect
$endgroup$
1
$begingroup$
Can someone edit the first mention of fog cloud to be spelled correctly? Kind of important spell in the question but I am required to edit more of the question in order to propose an edit.
$endgroup$
– findusl
Feb 16 at 13:28
1
$begingroup$
I've gone ahead and deleted my answer, since it is no longer relevant to the question (and thus is effectively a comment that was no longer needed). I'll also remove the link from the question.
$endgroup$
– Tim C
Feb 16 at 22:16
add a comment |
$begingroup$
I'm puzzled by the "a clear path to the target" rule.
To target something, you must have a clear path to it, so it can't be behind total cover.
This seems straightforward: you can't target a point/creature/object/thing behind total cover. But then the rule adds the following:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
And now suddenly I'm lost. You can't do A, but if you do, then B happens.
Let's assume a blind wizard stuck is in a maze, facing a wall he's not aware of. He's trying to cast fog cloud behind it.
How should the DM react, according to the rules?
I mostly see 3 options (but feel free to add others):
"No you can't. Choose another target / action."
This is the strict application of the rule's first sentence.
"Even though you placed your spell 60 feet away, you feel a strong humidity on your skin. It looks like the fog cloud appeared closer than what you intended."
This would be the application of the rule's second sentence.
"You say the words and do the gestures, but nothing happens."
As found here, Xanathar's Guide to Everything offers optional rules for invalid targets — that you can use... if you feel this falls into invalid targeting.
What bothers me is that the first option seemed to have an broad consensus (~90 person before the associated answer update): not only does it render the second sentence obsolete, but it allows the player to gain information on it's environment without spending actions. Suddenly, the wizard gains some kind of radar that allows him to check if the path in front of him is free, and circulate quickly in a maze made of prismatic walls without harm. This can't be right... right?
dnd-5e spells targeting cover line-of-effect
$endgroup$
I'm puzzled by the "a clear path to the target" rule.
To target something, you must have a clear path to it, so it can't be behind total cover.
This seems straightforward: you can't target a point/creature/object/thing behind total cover. But then the rule adds the following:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
And now suddenly I'm lost. You can't do A, but if you do, then B happens.
Let's assume a blind wizard stuck is in a maze, facing a wall he's not aware of. He's trying to cast fog cloud behind it.
How should the DM react, according to the rules?
I mostly see 3 options (but feel free to add others):
"No you can't. Choose another target / action."
This is the strict application of the rule's first sentence.
"Even though you placed your spell 60 feet away, you feel a strong humidity on your skin. It looks like the fog cloud appeared closer than what you intended."
This would be the application of the rule's second sentence.
"You say the words and do the gestures, but nothing happens."
As found here, Xanathar's Guide to Everything offers optional rules for invalid targets — that you can use... if you feel this falls into invalid targeting.
What bothers me is that the first option seemed to have an broad consensus (~90 person before the associated answer update): not only does it render the second sentence obsolete, but it allows the player to gain information on it's environment without spending actions. Suddenly, the wizard gains some kind of radar that allows him to check if the path in front of him is free, and circulate quickly in a maze made of prismatic walls without harm. This can't be right... right?
dnd-5e spells targeting cover line-of-effect
dnd-5e spells targeting cover line-of-effect
edited Feb 16 at 22:29
V2Blast
24k380151
24k380151
asked Feb 15 at 15:15
BashBash
1,423221
1,423221
1
$begingroup$
Can someone edit the first mention of fog cloud to be spelled correctly? Kind of important spell in the question but I am required to edit more of the question in order to propose an edit.
$endgroup$
– findusl
Feb 16 at 13:28
1
$begingroup$
I've gone ahead and deleted my answer, since it is no longer relevant to the question (and thus is effectively a comment that was no longer needed). I'll also remove the link from the question.
$endgroup$
– Tim C
Feb 16 at 22:16
add a comment |
1
$begingroup$
Can someone edit the first mention of fog cloud to be spelled correctly? Kind of important spell in the question but I am required to edit more of the question in order to propose an edit.
$endgroup$
– findusl
Feb 16 at 13:28
1
$begingroup$
I've gone ahead and deleted my answer, since it is no longer relevant to the question (and thus is effectively a comment that was no longer needed). I'll also remove the link from the question.
$endgroup$
– Tim C
Feb 16 at 22:16
1
1
$begingroup$
Can someone edit the first mention of fog cloud to be spelled correctly? Kind of important spell in the question but I am required to edit more of the question in order to propose an edit.
$endgroup$
– findusl
Feb 16 at 13:28
$begingroup$
Can someone edit the first mention of fog cloud to be spelled correctly? Kind of important spell in the question but I am required to edit more of the question in order to propose an edit.
$endgroup$
– findusl
Feb 16 at 13:28
1
1
$begingroup$
I've gone ahead and deleted my answer, since it is no longer relevant to the question (and thus is effectively a comment that was no longer needed). I'll also remove the link from the question.
$endgroup$
– Tim C
Feb 16 at 22:16
$begingroup$
I've gone ahead and deleted my answer, since it is no longer relevant to the question (and thus is effectively a comment that was no longer needed). I'll also remove the link from the question.
$endgroup$
– Tim C
Feb 16 at 22:16
add a comment |
3 Answers
3
active
oldest
votes
$begingroup$
#2 is correct in this case.
The relationship between those two sentences can be resolved as You can't do A. If you try to do A, B happens instead. You can't place the fog cloud behind the unseen wall, and if you try, it ends up in front of the wall instead.
But all of these outcomes are appropriate in some cases.
The rule about the effect ending up on the near side of the obstruction only applies when you're placing an area of effect, not when the spell targets a single creature or object.
"No, you can't" (#1) is correct when the player tries to choose a target that his character has no way to even identify. If our blind wizard tries to cast magic missile, well, no, he can't. Because it has to be cast at a creature you can see.
"You do the spell but nothing happens" (#3) is correct when the player chooses a target that is invalid for a reason the character doesn't know yet. Like, if you cast magic missile at a monster who's actually an illusion, or try to cast cure wounds on someone you don't know is a simulacrum.
$endgroup$
$begingroup$
It is worth noting that #3 is actually an optional rule in XGE, nowhere does the rules say this has to be what happens in this case. In fact, it says it can be ruled to be otherwise by the DM.
$endgroup$
– Rubiksmoose
Feb 18 at 16:14
$begingroup$
@Rubiksmoose I'm not seeing how that's different from any other rule.
$endgroup$
– Mark Wells
Feb 18 at 16:49
1
$begingroup$
The point I'm trying to make is that there is no hard rule that says that a spell fails when an invalid creature is targeted. For example, it could fail to be cast as all (such as case #1). The way you write it makes it seem like you are implying that there is a rule that says that it happens that way. The only thing I know of that comes close is the optional rule from XGE which is not a core rule. My only suggestion is that you add the fact that it is optional to your last paragraph so as to not give the wrong impression is all.
$endgroup$
– Rubiksmoose
Feb 18 at 16:53
add a comment |
$begingroup$
#2 - Fog cloud would appear on the wizard's side of the wall
To target something, you must have a clear path to it, so it can't be behind total cover.
This gives a broad, general rule that covers anything that targets something. However, rules then go on to create a special case that tells you how to apply the rule in a specific circumstance:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
This special case applies only to an AOE cast while the caster cannot see. You still cannot target the other side of the obstruction so you are still following the top line. The rule is simply telling you what happens after you try to target it. In this case, the spell simply comes into being on the near side of the obstruction where it follows all the normal rules.
So, in the example you give, the blind wizard would try to target a point behind a wall with fog cloud. The rules do not allow targeting that point and instead say that the effect comes into being on the near side of the wall which is what happens.
There's no contradiction at all here between the first and second lines of the spell or how they interact.
With a seeing wizard or non-AOE spells the other two cases are possible
What about non-AOE spells and the rule from Xanathar's?
A spell that targets a creature or object also still follows the general rule that the covered point cannot be targeted, but obviously the second line does not apply. The only difference between this case and the blind-AOE case is that the rule does not tell us what happens in this case.
This is where the optional rule from XGE comes in. It gives the DM an optional way to deal with attempts to cast a spell on an invalid target since this case is not defined in the original rule. Which means that, depending on the specific DM and case, either #1 or #3 would still be valid rulings for non-AOE spells casted by a non-blind spellcaster.
$endgroup$
add a comment |
$begingroup$
As others have stated, #2 is the answer for your situation.
The answer is already in the wording:
To target something, you must have a clear path to it, so it can't be behind total cover.
and
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
In the Player's Handbook: Spellcasting > Targets
A typical spell requires you to pick one or more targets to be affected by the spell's magic. A spell's description tells you whether the spell targets creatures, objects, or a point of origin for an area of effect.
And Spellcasting > Range
The target of a spell must be within the spell's range. For a spell like magic missile, the target is a creature. For a spell like fireball, the target is the point in space where the ball of fire erupts.
And per the rules of cover:
A target with total cover can't be targeted directly by an attack or a spell, although some spells can reach such a target by including it in an area of effect. A target has total cover if it is completely concealed by an obstacle.
For spells that have a target of something/someone, if you cannot see it (concealed), you cannot target it.
Area of effect spells have a point, or place you center the spell. This can be where a creature is standing, but to The Weave, it's just a point in space. So the point can't be somewhere concealed, but it will occur at the space you can see closest to that point. In this case, on the caster's side of the wall.
- You cannot Magic Missile a target that is hiding in a Darkness spell, but you can cast a Fireball in the middle and hope for the best.
- You cannot Fire Bolt the thief behind the barricade, but Sickening Radiance goes around corners.
$endgroup$
$begingroup$
Can you explain how you got to this conclusion? "For spells that have a target, if you cannot see it, you cannot target it." It doesn't seem like anything in your answer says or implies this.
$endgroup$
– Rubiksmoose
Feb 15 at 17:51
2
$begingroup$
It might help to quote the targeting rules to support the separation between “targets” and “point”. I don’t remember such a distinction bring made in the rules, so the answer might need to work harder to sell the concept as correct.
$endgroup$
– SevenSidedDie♦
Feb 15 at 18:16
$begingroup$
@Rubiksmoose Added quotes from PHB
$endgroup$
– MivaScott
Feb 15 at 18:48
$begingroup$
@MivaScott: I'm still not seeing anything that says anything about targets being required to be seen. None of the quotes talk about sight at all. It is also worth noting that JC explicitly has explicitly disagreed with what you say here and several other places.
$endgroup$
– Rubiksmoose
Feb 15 at 18:55
1
$begingroup$
@MivaScott are you just trying to say that you can't target a creature under full cover? Because that would make a lot more sense. However you should note that being under full cover doesn't mean you can't be seen. For example a creature on the other side of a window can be seen but still has full cover.
$endgroup$
– Rubiksmoose
Feb 15 at 20:34
|
show 1 more comment
Your Answer
StackExchange.ifUsing("editor", function ()
return StackExchange.using("mathjaxEditing", function ()
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
);
);
, "mathjax-editing");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "122"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2frpg.stackexchange.com%2fquestions%2f141193%2fwhat-happens-when-you-cast-fog-cloud-behind-a-wall%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
$begingroup$
#2 is correct in this case.
The relationship between those two sentences can be resolved as You can't do A. If you try to do A, B happens instead. You can't place the fog cloud behind the unseen wall, and if you try, it ends up in front of the wall instead.
But all of these outcomes are appropriate in some cases.
The rule about the effect ending up on the near side of the obstruction only applies when you're placing an area of effect, not when the spell targets a single creature or object.
"No, you can't" (#1) is correct when the player tries to choose a target that his character has no way to even identify. If our blind wizard tries to cast magic missile, well, no, he can't. Because it has to be cast at a creature you can see.
"You do the spell but nothing happens" (#3) is correct when the player chooses a target that is invalid for a reason the character doesn't know yet. Like, if you cast magic missile at a monster who's actually an illusion, or try to cast cure wounds on someone you don't know is a simulacrum.
$endgroup$
$begingroup$
It is worth noting that #3 is actually an optional rule in XGE, nowhere does the rules say this has to be what happens in this case. In fact, it says it can be ruled to be otherwise by the DM.
$endgroup$
– Rubiksmoose
Feb 18 at 16:14
$begingroup$
@Rubiksmoose I'm not seeing how that's different from any other rule.
$endgroup$
– Mark Wells
Feb 18 at 16:49
1
$begingroup$
The point I'm trying to make is that there is no hard rule that says that a spell fails when an invalid creature is targeted. For example, it could fail to be cast as all (such as case #1). The way you write it makes it seem like you are implying that there is a rule that says that it happens that way. The only thing I know of that comes close is the optional rule from XGE which is not a core rule. My only suggestion is that you add the fact that it is optional to your last paragraph so as to not give the wrong impression is all.
$endgroup$
– Rubiksmoose
Feb 18 at 16:53
add a comment |
$begingroup$
#2 is correct in this case.
The relationship between those two sentences can be resolved as You can't do A. If you try to do A, B happens instead. You can't place the fog cloud behind the unseen wall, and if you try, it ends up in front of the wall instead.
But all of these outcomes are appropriate in some cases.
The rule about the effect ending up on the near side of the obstruction only applies when you're placing an area of effect, not when the spell targets a single creature or object.
"No, you can't" (#1) is correct when the player tries to choose a target that his character has no way to even identify. If our blind wizard tries to cast magic missile, well, no, he can't. Because it has to be cast at a creature you can see.
"You do the spell but nothing happens" (#3) is correct when the player chooses a target that is invalid for a reason the character doesn't know yet. Like, if you cast magic missile at a monster who's actually an illusion, or try to cast cure wounds on someone you don't know is a simulacrum.
$endgroup$
$begingroup$
It is worth noting that #3 is actually an optional rule in XGE, nowhere does the rules say this has to be what happens in this case. In fact, it says it can be ruled to be otherwise by the DM.
$endgroup$
– Rubiksmoose
Feb 18 at 16:14
$begingroup$
@Rubiksmoose I'm not seeing how that's different from any other rule.
$endgroup$
– Mark Wells
Feb 18 at 16:49
1
$begingroup$
The point I'm trying to make is that there is no hard rule that says that a spell fails when an invalid creature is targeted. For example, it could fail to be cast as all (such as case #1). The way you write it makes it seem like you are implying that there is a rule that says that it happens that way. The only thing I know of that comes close is the optional rule from XGE which is not a core rule. My only suggestion is that you add the fact that it is optional to your last paragraph so as to not give the wrong impression is all.
$endgroup$
– Rubiksmoose
Feb 18 at 16:53
add a comment |
$begingroup$
#2 is correct in this case.
The relationship between those two sentences can be resolved as You can't do A. If you try to do A, B happens instead. You can't place the fog cloud behind the unseen wall, and if you try, it ends up in front of the wall instead.
But all of these outcomes are appropriate in some cases.
The rule about the effect ending up on the near side of the obstruction only applies when you're placing an area of effect, not when the spell targets a single creature or object.
"No, you can't" (#1) is correct when the player tries to choose a target that his character has no way to even identify. If our blind wizard tries to cast magic missile, well, no, he can't. Because it has to be cast at a creature you can see.
"You do the spell but nothing happens" (#3) is correct when the player chooses a target that is invalid for a reason the character doesn't know yet. Like, if you cast magic missile at a monster who's actually an illusion, or try to cast cure wounds on someone you don't know is a simulacrum.
$endgroup$
#2 is correct in this case.
The relationship between those two sentences can be resolved as You can't do A. If you try to do A, B happens instead. You can't place the fog cloud behind the unseen wall, and if you try, it ends up in front of the wall instead.
But all of these outcomes are appropriate in some cases.
The rule about the effect ending up on the near side of the obstruction only applies when you're placing an area of effect, not when the spell targets a single creature or object.
"No, you can't" (#1) is correct when the player tries to choose a target that his character has no way to even identify. If our blind wizard tries to cast magic missile, well, no, he can't. Because it has to be cast at a creature you can see.
"You do the spell but nothing happens" (#3) is correct when the player chooses a target that is invalid for a reason the character doesn't know yet. Like, if you cast magic missile at a monster who's actually an illusion, or try to cast cure wounds on someone you don't know is a simulacrum.
edited Feb 16 at 14:19
Bash
1,423221
1,423221
answered Feb 15 at 16:39
Mark WellsMark Wells
6,58011747
6,58011747
$begingroup$
It is worth noting that #3 is actually an optional rule in XGE, nowhere does the rules say this has to be what happens in this case. In fact, it says it can be ruled to be otherwise by the DM.
$endgroup$
– Rubiksmoose
Feb 18 at 16:14
$begingroup$
@Rubiksmoose I'm not seeing how that's different from any other rule.
$endgroup$
– Mark Wells
Feb 18 at 16:49
1
$begingroup$
The point I'm trying to make is that there is no hard rule that says that a spell fails when an invalid creature is targeted. For example, it could fail to be cast as all (such as case #1). The way you write it makes it seem like you are implying that there is a rule that says that it happens that way. The only thing I know of that comes close is the optional rule from XGE which is not a core rule. My only suggestion is that you add the fact that it is optional to your last paragraph so as to not give the wrong impression is all.
$endgroup$
– Rubiksmoose
Feb 18 at 16:53
add a comment |
$begingroup$
It is worth noting that #3 is actually an optional rule in XGE, nowhere does the rules say this has to be what happens in this case. In fact, it says it can be ruled to be otherwise by the DM.
$endgroup$
– Rubiksmoose
Feb 18 at 16:14
$begingroup$
@Rubiksmoose I'm not seeing how that's different from any other rule.
$endgroup$
– Mark Wells
Feb 18 at 16:49
1
$begingroup$
The point I'm trying to make is that there is no hard rule that says that a spell fails when an invalid creature is targeted. For example, it could fail to be cast as all (such as case #1). The way you write it makes it seem like you are implying that there is a rule that says that it happens that way. The only thing I know of that comes close is the optional rule from XGE which is not a core rule. My only suggestion is that you add the fact that it is optional to your last paragraph so as to not give the wrong impression is all.
$endgroup$
– Rubiksmoose
Feb 18 at 16:53
$begingroup$
It is worth noting that #3 is actually an optional rule in XGE, nowhere does the rules say this has to be what happens in this case. In fact, it says it can be ruled to be otherwise by the DM.
$endgroup$
– Rubiksmoose
Feb 18 at 16:14
$begingroup$
It is worth noting that #3 is actually an optional rule in XGE, nowhere does the rules say this has to be what happens in this case. In fact, it says it can be ruled to be otherwise by the DM.
$endgroup$
– Rubiksmoose
Feb 18 at 16:14
$begingroup$
@Rubiksmoose I'm not seeing how that's different from any other rule.
$endgroup$
– Mark Wells
Feb 18 at 16:49
$begingroup$
@Rubiksmoose I'm not seeing how that's different from any other rule.
$endgroup$
– Mark Wells
Feb 18 at 16:49
1
1
$begingroup$
The point I'm trying to make is that there is no hard rule that says that a spell fails when an invalid creature is targeted. For example, it could fail to be cast as all (such as case #1). The way you write it makes it seem like you are implying that there is a rule that says that it happens that way. The only thing I know of that comes close is the optional rule from XGE which is not a core rule. My only suggestion is that you add the fact that it is optional to your last paragraph so as to not give the wrong impression is all.
$endgroup$
– Rubiksmoose
Feb 18 at 16:53
$begingroup$
The point I'm trying to make is that there is no hard rule that says that a spell fails when an invalid creature is targeted. For example, it could fail to be cast as all (such as case #1). The way you write it makes it seem like you are implying that there is a rule that says that it happens that way. The only thing I know of that comes close is the optional rule from XGE which is not a core rule. My only suggestion is that you add the fact that it is optional to your last paragraph so as to not give the wrong impression is all.
$endgroup$
– Rubiksmoose
Feb 18 at 16:53
add a comment |
$begingroup$
#2 - Fog cloud would appear on the wizard's side of the wall
To target something, you must have a clear path to it, so it can't be behind total cover.
This gives a broad, general rule that covers anything that targets something. However, rules then go on to create a special case that tells you how to apply the rule in a specific circumstance:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
This special case applies only to an AOE cast while the caster cannot see. You still cannot target the other side of the obstruction so you are still following the top line. The rule is simply telling you what happens after you try to target it. In this case, the spell simply comes into being on the near side of the obstruction where it follows all the normal rules.
So, in the example you give, the blind wizard would try to target a point behind a wall with fog cloud. The rules do not allow targeting that point and instead say that the effect comes into being on the near side of the wall which is what happens.
There's no contradiction at all here between the first and second lines of the spell or how they interact.
With a seeing wizard or non-AOE spells the other two cases are possible
What about non-AOE spells and the rule from Xanathar's?
A spell that targets a creature or object also still follows the general rule that the covered point cannot be targeted, but obviously the second line does not apply. The only difference between this case and the blind-AOE case is that the rule does not tell us what happens in this case.
This is where the optional rule from XGE comes in. It gives the DM an optional way to deal with attempts to cast a spell on an invalid target since this case is not defined in the original rule. Which means that, depending on the specific DM and case, either #1 or #3 would still be valid rulings for non-AOE spells casted by a non-blind spellcaster.
$endgroup$
add a comment |
$begingroup$
#2 - Fog cloud would appear on the wizard's side of the wall
To target something, you must have a clear path to it, so it can't be behind total cover.
This gives a broad, general rule that covers anything that targets something. However, rules then go on to create a special case that tells you how to apply the rule in a specific circumstance:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
This special case applies only to an AOE cast while the caster cannot see. You still cannot target the other side of the obstruction so you are still following the top line. The rule is simply telling you what happens after you try to target it. In this case, the spell simply comes into being on the near side of the obstruction where it follows all the normal rules.
So, in the example you give, the blind wizard would try to target a point behind a wall with fog cloud. The rules do not allow targeting that point and instead say that the effect comes into being on the near side of the wall which is what happens.
There's no contradiction at all here between the first and second lines of the spell or how they interact.
With a seeing wizard or non-AOE spells the other two cases are possible
What about non-AOE spells and the rule from Xanathar's?
A spell that targets a creature or object also still follows the general rule that the covered point cannot be targeted, but obviously the second line does not apply. The only difference between this case and the blind-AOE case is that the rule does not tell us what happens in this case.
This is where the optional rule from XGE comes in. It gives the DM an optional way to deal with attempts to cast a spell on an invalid target since this case is not defined in the original rule. Which means that, depending on the specific DM and case, either #1 or #3 would still be valid rulings for non-AOE spells casted by a non-blind spellcaster.
$endgroup$
add a comment |
$begingroup$
#2 - Fog cloud would appear on the wizard's side of the wall
To target something, you must have a clear path to it, so it can't be behind total cover.
This gives a broad, general rule that covers anything that targets something. However, rules then go on to create a special case that tells you how to apply the rule in a specific circumstance:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
This special case applies only to an AOE cast while the caster cannot see. You still cannot target the other side of the obstruction so you are still following the top line. The rule is simply telling you what happens after you try to target it. In this case, the spell simply comes into being on the near side of the obstruction where it follows all the normal rules.
So, in the example you give, the blind wizard would try to target a point behind a wall with fog cloud. The rules do not allow targeting that point and instead say that the effect comes into being on the near side of the wall which is what happens.
There's no contradiction at all here between the first and second lines of the spell or how they interact.
With a seeing wizard or non-AOE spells the other two cases are possible
What about non-AOE spells and the rule from Xanathar's?
A spell that targets a creature or object also still follows the general rule that the covered point cannot be targeted, but obviously the second line does not apply. The only difference between this case and the blind-AOE case is that the rule does not tell us what happens in this case.
This is where the optional rule from XGE comes in. It gives the DM an optional way to deal with attempts to cast a spell on an invalid target since this case is not defined in the original rule. Which means that, depending on the specific DM and case, either #1 or #3 would still be valid rulings for non-AOE spells casted by a non-blind spellcaster.
$endgroup$
#2 - Fog cloud would appear on the wizard's side of the wall
To target something, you must have a clear path to it, so it can't be behind total cover.
This gives a broad, general rule that covers anything that targets something. However, rules then go on to create a special case that tells you how to apply the rule in a specific circumstance:
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
This special case applies only to an AOE cast while the caster cannot see. You still cannot target the other side of the obstruction so you are still following the top line. The rule is simply telling you what happens after you try to target it. In this case, the spell simply comes into being on the near side of the obstruction where it follows all the normal rules.
So, in the example you give, the blind wizard would try to target a point behind a wall with fog cloud. The rules do not allow targeting that point and instead say that the effect comes into being on the near side of the wall which is what happens.
There's no contradiction at all here between the first and second lines of the spell or how they interact.
With a seeing wizard or non-AOE spells the other two cases are possible
What about non-AOE spells and the rule from Xanathar's?
A spell that targets a creature or object also still follows the general rule that the covered point cannot be targeted, but obviously the second line does not apply. The only difference between this case and the blind-AOE case is that the rule does not tell us what happens in this case.
This is where the optional rule from XGE comes in. It gives the DM an optional way to deal with attempts to cast a spell on an invalid target since this case is not defined in the original rule. Which means that, depending on the specific DM and case, either #1 or #3 would still be valid rulings for non-AOE spells casted by a non-blind spellcaster.
edited Feb 18 at 16:12
answered Feb 15 at 16:01
RubiksmooseRubiksmoose
58k10283430
58k10283430
add a comment |
add a comment |
$begingroup$
As others have stated, #2 is the answer for your situation.
The answer is already in the wording:
To target something, you must have a clear path to it, so it can't be behind total cover.
and
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
In the Player's Handbook: Spellcasting > Targets
A typical spell requires you to pick one or more targets to be affected by the spell's magic. A spell's description tells you whether the spell targets creatures, objects, or a point of origin for an area of effect.
And Spellcasting > Range
The target of a spell must be within the spell's range. For a spell like magic missile, the target is a creature. For a spell like fireball, the target is the point in space where the ball of fire erupts.
And per the rules of cover:
A target with total cover can't be targeted directly by an attack or a spell, although some spells can reach such a target by including it in an area of effect. A target has total cover if it is completely concealed by an obstacle.
For spells that have a target of something/someone, if you cannot see it (concealed), you cannot target it.
Area of effect spells have a point, or place you center the spell. This can be where a creature is standing, but to The Weave, it's just a point in space. So the point can't be somewhere concealed, but it will occur at the space you can see closest to that point. In this case, on the caster's side of the wall.
- You cannot Magic Missile a target that is hiding in a Darkness spell, but you can cast a Fireball in the middle and hope for the best.
- You cannot Fire Bolt the thief behind the barricade, but Sickening Radiance goes around corners.
$endgroup$
$begingroup$
Can you explain how you got to this conclusion? "For spells that have a target, if you cannot see it, you cannot target it." It doesn't seem like anything in your answer says or implies this.
$endgroup$
– Rubiksmoose
Feb 15 at 17:51
2
$begingroup$
It might help to quote the targeting rules to support the separation between “targets” and “point”. I don’t remember such a distinction bring made in the rules, so the answer might need to work harder to sell the concept as correct.
$endgroup$
– SevenSidedDie♦
Feb 15 at 18:16
$begingroup$
@Rubiksmoose Added quotes from PHB
$endgroup$
– MivaScott
Feb 15 at 18:48
$begingroup$
@MivaScott: I'm still not seeing anything that says anything about targets being required to be seen. None of the quotes talk about sight at all. It is also worth noting that JC explicitly has explicitly disagreed with what you say here and several other places.
$endgroup$
– Rubiksmoose
Feb 15 at 18:55
1
$begingroup$
@MivaScott are you just trying to say that you can't target a creature under full cover? Because that would make a lot more sense. However you should note that being under full cover doesn't mean you can't be seen. For example a creature on the other side of a window can be seen but still has full cover.
$endgroup$
– Rubiksmoose
Feb 15 at 20:34
|
show 1 more comment
$begingroup$
As others have stated, #2 is the answer for your situation.
The answer is already in the wording:
To target something, you must have a clear path to it, so it can't be behind total cover.
and
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
In the Player's Handbook: Spellcasting > Targets
A typical spell requires you to pick one or more targets to be affected by the spell's magic. A spell's description tells you whether the spell targets creatures, objects, or a point of origin for an area of effect.
And Spellcasting > Range
The target of a spell must be within the spell's range. For a spell like magic missile, the target is a creature. For a spell like fireball, the target is the point in space where the ball of fire erupts.
And per the rules of cover:
A target with total cover can't be targeted directly by an attack or a spell, although some spells can reach such a target by including it in an area of effect. A target has total cover if it is completely concealed by an obstacle.
For spells that have a target of something/someone, if you cannot see it (concealed), you cannot target it.
Area of effect spells have a point, or place you center the spell. This can be where a creature is standing, but to The Weave, it's just a point in space. So the point can't be somewhere concealed, but it will occur at the space you can see closest to that point. In this case, on the caster's side of the wall.
- You cannot Magic Missile a target that is hiding in a Darkness spell, but you can cast a Fireball in the middle and hope for the best.
- You cannot Fire Bolt the thief behind the barricade, but Sickening Radiance goes around corners.
$endgroup$
$begingroup$
Can you explain how you got to this conclusion? "For spells that have a target, if you cannot see it, you cannot target it." It doesn't seem like anything in your answer says or implies this.
$endgroup$
– Rubiksmoose
Feb 15 at 17:51
2
$begingroup$
It might help to quote the targeting rules to support the separation between “targets” and “point”. I don’t remember such a distinction bring made in the rules, so the answer might need to work harder to sell the concept as correct.
$endgroup$
– SevenSidedDie♦
Feb 15 at 18:16
$begingroup$
@Rubiksmoose Added quotes from PHB
$endgroup$
– MivaScott
Feb 15 at 18:48
$begingroup$
@MivaScott: I'm still not seeing anything that says anything about targets being required to be seen. None of the quotes talk about sight at all. It is also worth noting that JC explicitly has explicitly disagreed with what you say here and several other places.
$endgroup$
– Rubiksmoose
Feb 15 at 18:55
1
$begingroup$
@MivaScott are you just trying to say that you can't target a creature under full cover? Because that would make a lot more sense. However you should note that being under full cover doesn't mean you can't be seen. For example a creature on the other side of a window can be seen but still has full cover.
$endgroup$
– Rubiksmoose
Feb 15 at 20:34
|
show 1 more comment
$begingroup$
As others have stated, #2 is the answer for your situation.
The answer is already in the wording:
To target something, you must have a clear path to it, so it can't be behind total cover.
and
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
In the Player's Handbook: Spellcasting > Targets
A typical spell requires you to pick one or more targets to be affected by the spell's magic. A spell's description tells you whether the spell targets creatures, objects, or a point of origin for an area of effect.
And Spellcasting > Range
The target of a spell must be within the spell's range. For a spell like magic missile, the target is a creature. For a spell like fireball, the target is the point in space where the ball of fire erupts.
And per the rules of cover:
A target with total cover can't be targeted directly by an attack or a spell, although some spells can reach such a target by including it in an area of effect. A target has total cover if it is completely concealed by an obstacle.
For spells that have a target of something/someone, if you cannot see it (concealed), you cannot target it.
Area of effect spells have a point, or place you center the spell. This can be where a creature is standing, but to The Weave, it's just a point in space. So the point can't be somewhere concealed, but it will occur at the space you can see closest to that point. In this case, on the caster's side of the wall.
- You cannot Magic Missile a target that is hiding in a Darkness spell, but you can cast a Fireball in the middle and hope for the best.
- You cannot Fire Bolt the thief behind the barricade, but Sickening Radiance goes around corners.
$endgroup$
As others have stated, #2 is the answer for your situation.
The answer is already in the wording:
To target something, you must have a clear path to it, so it can't be behind total cover.
and
If you place an area of effect at a point that you can't see and an obstruction, such as a wall, is between you and that point, the point of origin comes into being on the near side of that obstruction.
In the Player's Handbook: Spellcasting > Targets
A typical spell requires you to pick one or more targets to be affected by the spell's magic. A spell's description tells you whether the spell targets creatures, objects, or a point of origin for an area of effect.
And Spellcasting > Range
The target of a spell must be within the spell's range. For a spell like magic missile, the target is a creature. For a spell like fireball, the target is the point in space where the ball of fire erupts.
And per the rules of cover:
A target with total cover can't be targeted directly by an attack or a spell, although some spells can reach such a target by including it in an area of effect. A target has total cover if it is completely concealed by an obstacle.
For spells that have a target of something/someone, if you cannot see it (concealed), you cannot target it.
Area of effect spells have a point, or place you center the spell. This can be where a creature is standing, but to The Weave, it's just a point in space. So the point can't be somewhere concealed, but it will occur at the space you can see closest to that point. In this case, on the caster's side of the wall.
- You cannot Magic Missile a target that is hiding in a Darkness spell, but you can cast a Fireball in the middle and hope for the best.
- You cannot Fire Bolt the thief behind the barricade, but Sickening Radiance goes around corners.
edited Feb 15 at 20:18
answered Feb 15 at 17:24
MivaScottMivaScott
5,67611143
5,67611143
$begingroup$
Can you explain how you got to this conclusion? "For spells that have a target, if you cannot see it, you cannot target it." It doesn't seem like anything in your answer says or implies this.
$endgroup$
– Rubiksmoose
Feb 15 at 17:51
2
$begingroup$
It might help to quote the targeting rules to support the separation between “targets” and “point”. I don’t remember such a distinction bring made in the rules, so the answer might need to work harder to sell the concept as correct.
$endgroup$
– SevenSidedDie♦
Feb 15 at 18:16
$begingroup$
@Rubiksmoose Added quotes from PHB
$endgroup$
– MivaScott
Feb 15 at 18:48
$begingroup$
@MivaScott: I'm still not seeing anything that says anything about targets being required to be seen. None of the quotes talk about sight at all. It is also worth noting that JC explicitly has explicitly disagreed with what you say here and several other places.
$endgroup$
– Rubiksmoose
Feb 15 at 18:55
1
$begingroup$
@MivaScott are you just trying to say that you can't target a creature under full cover? Because that would make a lot more sense. However you should note that being under full cover doesn't mean you can't be seen. For example a creature on the other side of a window can be seen but still has full cover.
$endgroup$
– Rubiksmoose
Feb 15 at 20:34
|
show 1 more comment
$begingroup$
Can you explain how you got to this conclusion? "For spells that have a target, if you cannot see it, you cannot target it." It doesn't seem like anything in your answer says or implies this.
$endgroup$
– Rubiksmoose
Feb 15 at 17:51
2
$begingroup$
It might help to quote the targeting rules to support the separation between “targets” and “point”. I don’t remember such a distinction bring made in the rules, so the answer might need to work harder to sell the concept as correct.
$endgroup$
– SevenSidedDie♦
Feb 15 at 18:16
$begingroup$
@Rubiksmoose Added quotes from PHB
$endgroup$
– MivaScott
Feb 15 at 18:48
$begingroup$
@MivaScott: I'm still not seeing anything that says anything about targets being required to be seen. None of the quotes talk about sight at all. It is also worth noting that JC explicitly has explicitly disagreed with what you say here and several other places.
$endgroup$
– Rubiksmoose
Feb 15 at 18:55
1
$begingroup$
@MivaScott are you just trying to say that you can't target a creature under full cover? Because that would make a lot more sense. However you should note that being under full cover doesn't mean you can't be seen. For example a creature on the other side of a window can be seen but still has full cover.
$endgroup$
– Rubiksmoose
Feb 15 at 20:34
$begingroup$
Can you explain how you got to this conclusion? "For spells that have a target, if you cannot see it, you cannot target it." It doesn't seem like anything in your answer says or implies this.
$endgroup$
– Rubiksmoose
Feb 15 at 17:51
$begingroup$
Can you explain how you got to this conclusion? "For spells that have a target, if you cannot see it, you cannot target it." It doesn't seem like anything in your answer says or implies this.
$endgroup$
– Rubiksmoose
Feb 15 at 17:51
2
2
$begingroup$
It might help to quote the targeting rules to support the separation between “targets” and “point”. I don’t remember such a distinction bring made in the rules, so the answer might need to work harder to sell the concept as correct.
$endgroup$
– SevenSidedDie♦
Feb 15 at 18:16
$begingroup$
It might help to quote the targeting rules to support the separation between “targets” and “point”. I don’t remember such a distinction bring made in the rules, so the answer might need to work harder to sell the concept as correct.
$endgroup$
– SevenSidedDie♦
Feb 15 at 18:16
$begingroup$
@Rubiksmoose Added quotes from PHB
$endgroup$
– MivaScott
Feb 15 at 18:48
$begingroup$
@Rubiksmoose Added quotes from PHB
$endgroup$
– MivaScott
Feb 15 at 18:48
$begingroup$
@MivaScott: I'm still not seeing anything that says anything about targets being required to be seen. None of the quotes talk about sight at all. It is also worth noting that JC explicitly has explicitly disagreed with what you say here and several other places.
$endgroup$
– Rubiksmoose
Feb 15 at 18:55
$begingroup$
@MivaScott: I'm still not seeing anything that says anything about targets being required to be seen. None of the quotes talk about sight at all. It is also worth noting that JC explicitly has explicitly disagreed with what you say here and several other places.
$endgroup$
– Rubiksmoose
Feb 15 at 18:55
1
1
$begingroup$
@MivaScott are you just trying to say that you can't target a creature under full cover? Because that would make a lot more sense. However you should note that being under full cover doesn't mean you can't be seen. For example a creature on the other side of a window can be seen but still has full cover.
$endgroup$
– Rubiksmoose
Feb 15 at 20:34
$begingroup$
@MivaScott are you just trying to say that you can't target a creature under full cover? Because that would make a lot more sense. However you should note that being under full cover doesn't mean you can't be seen. For example a creature on the other side of a window can be seen but still has full cover.
$endgroup$
– Rubiksmoose
Feb 15 at 20:34
|
show 1 more comment
Thanks for contributing an answer to Role-playing Games Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2frpg.stackexchange.com%2fquestions%2f141193%2fwhat-happens-when-you-cast-fog-cloud-behind-a-wall%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
$begingroup$
Can someone edit the first mention of fog cloud to be spelled correctly? Kind of important spell in the question but I am required to edit more of the question in order to propose an edit.
$endgroup$
– findusl
Feb 16 at 13:28
1
$begingroup$
I've gone ahead and deleted my answer, since it is no longer relevant to the question (and thus is effectively a comment that was no longer needed). I'll also remove the link from the question.
$endgroup$
– Tim C
Feb 16 at 22:16