It’s time for a random pile of bulls$&% from the brain of the Angry GM. Today’s steamer is about clock speeds, decision points, why D&D runs at two different speeds, and how the designers of RPGs really need to figure that s$&% out better. Don’t worry, this has nothing to do with Time Pools.
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.
Information management is one of the trickiest parts of adventure design. Our Megadungeon has a story to tell. We have to figure out how to tell it. And also figure out what that story actually 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.
Before we can build new modes of play, we need to admit that the core rules of D&D 5E have a few oddities and are lacking in a few things we’re going to need. So let’s get out our tweaking tools and tinker with the core.
I can’t help how my brain works. I get distracted from solving problems by solving totally different problems. But before I invent more goddamned game mechanics, it’s worth questioning whether I should.
Sometimes the weird is bonkers. And sometimes it’s just incongruous. Like the hippo-people of Spelljammer. Or as we like to call it, D&D in Spaaaaacccceee!