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.
I’m on vacation! Here’s when to expect the rest of the posts for June.
A well-designed, well-paced adventure hangs on the exit map. And designing a good exit map is more about incentives and psychological tricks than it is about walls and doors.
In our favorite fantasy games, recovering from injuries is instantanoeus and magical. But in real life, even a small cut can be healing for year. So, in the real Medieval world, who would you go to if you needed to recover from your injuries?
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.
Maps aren’t just maps. Maps are tools for organizing and presenting information. As a prelude to building an exit map, we’re going to organize our information and figure out just what maps our megadungeon needs and who they’re for. Also, we’ll do some mapping.
And so our three-part series on the history of sailing and seafaring draws to a close. We know we spent a lot of time on it. But it’s only fitting considering how the history of sailing intersects with the history of timekeeping.
Let’s talk about the mythical distinction between players and characters. Players are characters. Characters are players. And once you accept that, it’s a lot easier to run a fun game. Warning: this gets ranty.