Show Me in the Module
In ye olde A,D&D the rules said dwarves have a 1 in 6 chance to detect ‘sloping passages’. The idea was that some modules would trick players into entering the more dangerous lower levels of a dungeon with a long passage which sloped downwards so gently that nobody notices until they encounter a ‘high-level’ monster. But despite three decades of playing RPGs I have still never encountered this tricky sloping passage. The rule should never have entered the Players’ Handbook. The rule could have been used only where required - in modules which have such a sloping passage, just beneath the boxtext which says ‘this long passage continues farther than your lantern can see, but the echo suggests it goes a long way indeed’.
A great many rules could have served everyone better by appearing consistently in modules, where required. And more than rules - after focussing on this clearly minor quibble with A,D&D, I’ve given every general principle I could find a long stare with a suspicious eyeball.
White Wolf books harked on about the importance of ’theme’ and ‘mood’ more than the average English Literature teacher. But I can’t recall a single clear theme or mood in any White Wolf chronicles I paid for. Perhaps I missed them, but the ‘Storyteller’ should not have to read between the lines to find the deeper narrative. If a film’s director doesn’t have a good grasp of a story’s theme then the film certainly won’t somehow do better.
Those White Wolf books could have given us a clear theme within those chronicle books.1
The theme for Glasgow by Night is that poverty breeds violence. In the opening scene, football fans shout, chant, and vomit, then fights break out. The first story revolves around a new Young Team trying to establish a reputation. In the second act the rich instigate violence indirectly by employing people in poverty, and in the third act they instigate violence even less directly by creating mass poverty.
Showing the principle in action serves the reader far better than explaining the abstract principle and telling them to just go and figure it out.
Modules as Rules
With these thoughts whispering quietly behind my ears for a couple of years, I’ve found a few ways to move things inside BIND modules which would normally live only in the rules.
Standard Equipment
I grew up doing treasure like this:
- Today’s random encounter is ‘owlbear’.
- Get the Monstrous Manual, and find that owlbear!
- The owlbear had ’treasure type P’.
- Get the Dungeon Master’s Guide.
- Treasure type P has a 20% chance of a magical scroll.
It was bloody awful.
Instead of all that, I just put each statblock in the modules, and note equipment there.
| Name | Boblin |
|---|---|
| Race | Goblin |
| Stats | AP 4, Att 9, Dam D6+1 |
| Equipment | Javelin, mink-bone toothpick, hexagonal gold coin from the Northern Kingdom. |
Rations get the same treatment. There are no generic rations. Instead, non-player characters have items like ‘auroch tongue’ and ‘salted basilisk strips’ listed on their statblocks. This also tells players that in Fenestra, people eat basilisk meat; but it avoids asking them to read about the culture in the rule books - it’s all right there inside the modules.
Naming the Cheese-Sellers
Instead of listing the price for weapons in one book, then (when players of a ‘role playing game’ decide to actually talk to the person who sells them the weapons) asking the Judge to find and use a random name-generator, BIND just lists each seller’s name in a handout.
Using a handout for each market brings other benefits - you can make items actually rare. There’s no need to write down ’this item is rare (20% chance of finding it in a market)’; the item is simply listed rarely. Players will know that it’s a rare item from the fact that they’ve seen five market handouts and never seen this item before.
Food should become more expensive over the frosty Cycle known as ‘Sables’ (Fenestra’s Winter). But the books never mention that fact - the market handouts simply raise the prices for rations.
The market handouts also tell the players about who their characters are. A few shops will offer to buy ‘Ingredients’ for a high price, which will (hopefully) prompt the question ‘what are these ingredients this shopkeeper wants?’. The Judge will have found the answer to that question already on the first page of the Almanac; these Ingredients come from harvesting the bodies of monsters. The description of harvesting monster-bodies lists only the monsters in that particular Almanac, so if the only encounters are with bears and griffins, then the Almanac only notes how to harvest a bear’s heart and a griffin’s wings.
Players can find a strange item in the markets called a ‘dawn dolly’. People wave this doll-on-a-stick outside their front door each morning, in case some creature has sat on their roof overnight, waiting for them to exit. This could have been written in the book, but how would anyone introduce that fact to the table during a game? The markets show the players what kind of world they live in.
Modules as Introductions
Institutions
BIND’s Book of Judgement has all the details about guilds, but the information shouldn’t be necessary to run a game. Instead of expecting people to read all about the guilds, the modules introduce NPCs who work for a guild. The nature, structure, and culture of each guild appears through those non-player characters directly. As for the Temple of Beasts (which the player characters start in), the modules simply begin in a broch as someone plays pipes to try to attract a monster, or the player characters begin on the road, guarding a caravan.
In this case, having a few pages to describe the guild still provides useful information, but conveying basic information in the modules first means people can read about the guilds to fill in the gaps rather than reading about them for no particular reason and hoping the magic elf-game will make the homework worth their time later.
Basilisks Hibernating in Real Time
Every week in mundane time means thirty days have passed in Fenestra. Once you work out the date in Fenestra, you might find it snowing, which means that the basilisks have gone into hibernation. I could write this all down in the rulebooks, and remind people to adjust the modules to the current season by removing the basilisks. I could, but they wouldn’t, so I don’t.
Instead of writing out the fantasy calendar and explaining when breeding-season begins for basilisks, it all just goes into the modules, automatically. Currently, all BIND modules have expensive rations, lots of rain, and few basilisks. Last week, every module had snow and zero basilisks. And in two weeks, every single module will mention the punishing Sunshine, and then throw ten basilisks at the troupe every day.2
This lets people just download modules and use them without me having to tell them about the seasons. The players will still notice the passage of time through praxis, but any chance of homework has been averted.
Check the Almanac for a short example. Every week it refreshes with half a dozen pre-written (semi-) random encounters.
Don’t Tell Me about Elven Social Structures
One module shows two elven territories. It describes the territories and their wildly different cultures with a series of encounters with the people who live there.
You should not use this module because it’s entirely untested3, but you might read it, because it provides a better introduction to elven culture than abstract examples.
On the Trail of the Snail Lords
Spell Books
People enjoy looking through big lists of spells in RPG rulebooks. It’s fun to check out what the magic system can do. But it’s more fun to read about the spells you found in the game as real loot.
Check the link, or download the printable version then fold and bind it into a real spell book.
Making Appropriate Characters
The books have no need to plead with players to make a character which fits into Fenestra, and neither does the Judge. Players receive pre-made characters who fit into Fenestra just fine. Every module has a few of these characters.
If any character can cast spells then the player will find those spells written on the character sheet, so there’s no need to leaf through the rulebook. If players want to design their own character, they can spend one of their five Story Points to introduce an ally, and spend some points to buy whatever Skills they want.
By the time players notice they have ‘Story Points’ on the character sheets, and introduce an ally, they will have seen a fair bit of Fenestra, and they can only spend the Story Point by explaining how their current character met with that ally in the first place.
-
If I still had my copy of New York by Night, I would do a long dissection of that book and how it seems to show a world, without actually handing over enough concrete, gameable things to do. The material is all there, but it somehow expects you to just riff off of it, live, and jump through the pages to find statblocks (which aren’t blocks - each one is a page long). ↩︎
-
And soon I may introduce the concept of the basilisk mating season with a basilisk fuck-knot right in the centre of a module. ↩︎
-
If anyone actually uses it, they are honour-bound to tell me all about their session so I can finally fix and publish it. ↩︎