Feats are also an optional rule, but I’ve never heard of a table not using them. “Optional rule” in 5e is kind of like the term “theory” IRL, in that some really are optional and some are basically always used. I will admit that not all tables use the diagonal rule, though.
You’re welcome! For reference it’s a code block, all formatting goes out the window, returns are considered returns, and a monospaced font. You use three backticks (```) on a line above and below your “code” (you can technically specify the code type at the end of that first back tick line) and then go to town between them.
5e accounts for diagonal distance. Each second diagonal is 10ft. A 10ft. radius sphere spell would cover this pattern on the ground:
OOOOOOO
OOXXXOO
OXXXXXO
OXXXXXO
OXXXXXO
OOXXXOO
OOOOOOO
…lemmy formatting kills that but you get the point I hope.
That is only listed in 5e as an optional rule, by default a square is a square and is 5ft regardless of diagonal or not.
Feats are also an optional rule, but I’ve never heard of a table not using them. “Optional rule” in 5e is kind of like the term “theory” IRL, in that some really are optional and some are basically always used. I will admit that not all tables use the diagonal rule, though.
Many thanks!
You’re welcome! For reference it’s a code block, all formatting goes out the window, returns are considered returns, and a monospaced font. You use three backticks (```) on a line above and below your “code” (you can technically specify the code type at the end of that first back tick line) and then go to town between them.
I use them for actual code but the ability to use them to get normal returns somehow hadn’t occurred to me haha
You can also have “normal returns”, or line breaks instead of new paragraph, by putting a double space at the end of a line:
Hello
Double
Spaced
Lemmy!