Like, if the DM wants to run a Werewolf, there's certain themes and tropes surrounding that kind of encounter. It's classic and has an identity. At the cost of making some DM's afternoons slightly easier, they've blobbified a classic and thematic encounter!
The campaign I'm in just went on a week long journey (irl, like 4 months) to find a Blacksmith that sold silver weapons so we could fight devils. Now, we're realizing that that isn't important anymore.
Silver weapons aren't the same in 5e2024 anymore. Apparently, they only do bonus damage against shapeshifters while they're shapeshifting. Devils don't care, werewolves don't care.
Through lack of play, I didn't really need second opinions on system edge cases. That stopped me from returning as an asker. Since I wasn't already sitting around at the site, I wasn't in chat faffing about seeing what others were talking about and I wasn't looking at the front page for interesting questions to answer.
@JohnP A lot of why I stopped coming here was because of my jadedness with the 5e System and all of the WotC garbage. Since I took such a long break from TTRPG as a result, I almost didn't even check the site for nearly a year. If it weren't for some comments @'ing me in November, I wouldn't have broken the streak.
The grander question is "how does this all work?" But that's only a relevant question if it all works. If there's not enough here in framework to support anything at all, it seems like Hiding/Invisibility, tactical knowledge of what and where, vision, etc. are all up to DM discretion.
Wild question, I know.
Of the rules that dictate whether or not something can be seen, there's only two places where it's explicitly discussed. Heavy Obscurement (which grants Blinded) and the Blinded condition.
Can't See. You can't see and automatically fail any ability check that requires sigh...
The only time Strength is referred to in the Glossary is for the definition of Unarmed Strike. All the ink they wasted explaining that Strength applies to unarmed strike could have been spent explaining that attacks with weapons apply your appropriate stat.
I understand the sentiment (everything is really just roll a d20 against some criteria), but it seems like a pain in the ass to use new vernacular that only exists here and exists only to be immediately obsoleted.
Also, the idea of calling them D20 Tests didn't really simplify anything when they still refer to them as saves, checks, and rolls literally everywhere else.
https://www.dndbeyond.com/sources/dnd/free-rules/playing-the-game#Actions Going here, it redirects users who want to learn how Attack Actions work to the Rules Glossary which started this whole mess.
One of our players got confused in a new campaign and got into an argument about what to add to weapon attack damage rolls. When we then went to the Glossary to explain this to them, we went through this sequence: https://www.dndbeyond.com/sources/dnd/free-rules/rules-glossary#AttackAction Mentions nothing about the weapon stat being applied to the roll. https://www.dndbeyond.com/sources/dnd/free-rules/rules-glossary#AttackRoll Makes still no mention of weapon stat being added. Finally, it redirects us to this section:
There's an off-by-one in there. Indexing with 0@S doesn't give you the 0th element. However, if the 0th element should be 0, then it's all good, it will naturally evaluate 0@anything as 0.
Anyone got a sec to help me with AnyDice? How would I histogram a complicated roll 1dX into bins of the following sort: 0-21, 22-34, 35-44, 45-54, and 55+? I can do it with if-statements, but it's gross.