I want to write adventures for tabletop RPGs, both for existing systems and for games of my own. What makes a module useful at the table, what should I avoid, and are there published adventures worth reading as examples?
How do you write an RPG module that's easy to run?
Answers
Write for the person running the game, not just for someone reading it. Put the information they need to make a decision where they will look for it. A location entry should make the exits, obvious features, threats, and useful discoveries easy to find.
Keep the opening overview short: what is going on, what the characters might want, and what could happen if they do nothing. You can save background history for the places where it actually changes play.
Reply to this answer
Don't assume the players will solve the adventure in one particular way. Give the referee situations, motivations, and consequences to work with rather than a sequence of scenes that only functions if everyone follows the expected path.
If a clue is necessary to move forward, consider putting it in more than one place. Also think about what happens when the characters negotiate, retreat, or make a mess instead of fighting.
Reply to this answer
I'd start small and test it. A handful of locations with a clear problem will teach you more about your writing than a huge campaign draft. Watch for the moments when the person running it has to stop and ask what you meant, then revise those sections.
Having someone else run it from the text is especially useful. They won't have the answers that were in your head while you wrote it.
Reply to this answer
For examples, look at The Lost Mine of Phandelver for a relatively guided introductory adventure and Tomb of the Serpent Kings for a dungeon built around teaching exploration. Compare how each introduces locations, dangers, and the next possible move.
Don't just read for plot. Pick a room or encounter and ask whether you could run it without rereading the whole chapter. Note what you can find quickly and what you have to hunt for. A useful example can still have things you'd organize differently.
Reply to this answer
Match the detail to the game you're writing for. Include the rules, statistics, and other references a referee needs to resolve the adventure, but don't bury every location in mechanics. For a system of your own, explain any procedures the adventure depends on clearly enough that someone else can use them.
Reply to this answer
Add your answer
Answers are reviewed before publication.
scrimFill~Unlisted:
A quick reference sheet can help too, but test the main text first. A summary won't fix missing information.