It’s all well and good to think through a whole bunch of conceptual bulls$&% when you’re designing a new rules system. But there comes a time when you have to sit down and actual write the rules themselves. So lets give that some thought.
Creating new rules isn’t as simple as coming up with a fun idea for a system and then making it. There’s a whole thing in the middle where you actually spend a bunch of time working out how not to accidentally make a turd. Too bad WotC didn’t know about that step when it came to their crafting rules.
Surprise! Here’s a preview of an upcoming article. It’s a set of rules I built for crafting nonmagical herbal items in D&D 5E using the herbalism kit (and proficiency therewith). Feel free to check out the rules and then come back soon to find out how and why they were created.
There’s lots of things GMs might hide in their adventures. For example, traps. But how does D&D handle traps? Why does D&D suck at handling traps? And how should it handle traps?
Before we can build any rules modules, we have to have a solid framework for those modules. Using the previously published core rules tweaks and the time pool – both of which desperately need some revision and correction and clarification, we’re going to build a master module for exploration. We’re also going to discuss exactly what the hell a “master module for exploration” is.
Everything in D&D is marked in 5-foot squares. So it makes sense that the whole game is meant to be played on a grid. But everything is also marked out in minutes and seconds and hours. Where’s the grid for time. That’s a weird question, I know. But answering it leads to a powerful tool.
Hacking is bad for your game. That’s an undeniable fact. So, if you’re going to hack your game, be prepared to fight for it. Even if you’re only fighting yourself.
We play games because we don’t know how they are going to turn out. And games use several tricks to keep us from knowing the outcome. The problem is GMs only ever use one of those tricks. And it’s the worst one.