How do I target the Moonbeam spell, using a grid?
How do I target the Moonbeam spell, using a grid?
So, as my title implies; If you shoot a Moonbeam at an enemy standing in a square, would the area covered by the Moonbeam be just that single square, from one of the corners 2x2 or midsquare 3x3 around the square with the target?
It's more about how to aim spells with AoE in general, PoO and what squares get affected :) I chose Moonbeam since our Druid just turned lvl 3, so it will be used! But I think the new title is fitting as well, just tried a broader incase anyone else searches for the answer to how to aim spells ^^
– DerpwaldDuck
Sep 3 at 14:54
2 Answers
2
Moonbeam says:
A silvery beam of pale light shines down in a 5-foot- radius, 40-foot-high cylinder centered on a point within range. Until the spell ends, dim light fills the cylinder.
The Player's Handbook says, p 204, when casting a spell with a cylindrical area of effect:
A cylinder's point of origin is the center of a circle of a particular radius, as given in the spell description.
If you shoot a moonbeam at an enemy, and you choose the point of origin to be where the enemy is, then the center of the circle is where the enemy is standing.
Additionally, the DMG on p249, under Adjudicating Areas of Effect, says in part:
Many spells and other game features create areas of effect, such as the cone and the sphere. If you're not using miniatures or another visual aid, it can sometimes be difficult to determine who's in an area of effect and who isn't. The easiest way to address such uncertainty is to go with your gut and make a call.
It sounds like you're using the optional grid rules from the PHB, p 192.
There are some challenges to using the grid system.
If the point of origin of the circle is where the target is, then it is where you decide the creature is. Is the creature in the center of the square? Then that's where the moonbeam is centered. Then the issue is how to handle the surrounding squares.
The DMG on p 251 in the section on Using Miniatures talks about additional rules to the grid system, and says that under this method the point of origin is restricted to a grid intersection.
The area of effect of a spell, monster ability, or other feature must be translated onto squares or hexes to determine which potential targets are in the area and which aren't. Choose an intersection of squares or hexes as the point of origin of an area of effect, then follow its rules as normal. If an area of effect is circular and covers at least half a square, it affects that square.
To summarize, assuming you want to use a grid system to visualize combat, you're going to have to make some compromises. Round pegs don't fit into square holes very well. Round areas-of-effect don't fit a grid system very well. You can center the AoE in the middle of a square, but then you have squares that are partially covered and you're going to have to adjudicate that. Or you can place the AoE at an intersection, but then you're denying the spellcaster the ability to actually target where the target is standing.
In the end, the GM is going to have to adjudicate exactly how it works in their game.
I was going to write an answer that I feel adds something, but I realised that I'd basically have to recreate your answer to lay the groundwork, and then add like a 10% add-on, so: Might be good to add reference to how much of the surrounding squares could be effected by moonbeam, and what the source books say about when squares are partially covered by an area of effect.
– Isaac Reefman
Sep 3 at 2:44
You quote the DMG bit about AoEs, but you don't include the more specific guidance provided by the DMG regarding adjudicating areas of effect on a grid a few pages later, on p. 251: "Choose an intersection of squares or hexes as the point of origin of an area of effect, then follow its rules as normal. If an area of effect is circular and covers at least half a square, it affects that square." Moonbeam covers 4 squares when centered at an intersection, with its 5-foot radius; it doesn't hit just one enemy.
– V2Blast
Sep 3 at 3:00
@V2Blast that's what I was getting at. Interestingly the same guidelines suggest that if centered on a creature when using snap-t0-grid, the fact that it's centered on the center (ugh, spamming that word) of a square would mean that no other square is at least 50% covered - it only affects one creature; having a 5'radius sounds kinda like a 5' range, though... seems a bit sad to rule that way...
– Isaac Reefman
Sep 3 at 6:36
"In that case, the center of the circle is the middle of the square." — can you please back up this statement with any source?
– enkryptor
Sep 3 at 12:53
With area spells, you don't target specific enemies anyway. So following the rules and centering them on corners does not take away anything. Also there are always partially covered squares, regardless of the position of the center
– András
Sep 3 at 13:23
It originates from a corner
DMG 251:
Choose an intersection of squares or hexes as the point of origin of an area of effect, then follow its rules as normal. If an area of effect is circular and covers at least half a square, it affects that square.
As with most area spells, you don't target an enemy with it, just a patch of ground. So it covers 2x2 squares.
Thanks for contributing an answer to Role-playing Games Stack Exchange!
But avoid …
Use MathJax to format equations. MathJax reference.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
But avoid …
To learn more, see our tips on writing great answers.
Required, but never shown
Required, but never shown
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
Edited the title. The question is not about point of origin, it is about aligning the spell effect area to the grid. Please rollback if I was wrong.
– enkryptor
Sep 3 at 13:04