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.
Here’s a Megadungeon article about why there isn’t a Megadungeon article. Paradoxically. Think of it as a project update and a preview of a very big, exciting development.
If you get over the bulls$&% notion that planning a plot is somehow railroading, you’ll discover just how powerful plot threads are as tools for designing adventures and campaigns. In this article, we’ll discuss the basics of plot points and how to build simple and complex adventures around them.
Just because you have a ship that can survive a voyage across the open ocean doesn’t mean you should voyage across the open ocean. First, you need a good reason. Second, you need to actually know where you’re going and how to get there.
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.