If you walked behind my DM screen during one of my D&D sessions, you might think I was running the wrong game.

My campaign is technically a Fifth Edition campaign. The characters, spells and items come from the 2014 5e PHB and DMG.

But the books I reach for while running the game are Old-School Essentials, Knave Second Edition, Cairn, and Shadowdark.

I do not use those books because I am trying to secretly convert my table to a different game. I use them because 5e gives me the player-facing chassis, while old-school and new-school revolution books give me the procedures that make the world move.

This is not a manifesto. This is a practical walkthrough of what is on my table and why.

I am not running one game

I am not a purist. I do not have system loyalty. What I have is a campaign I want to run well, and I have learned that no single book answers every question I need to answer during a session.

5e is good at what it does. It gives me character sheets, classes, spells, tactical combat resolution, and a shared language that new players already understand. I could run 5e with nothing but the Player's Handbook and get through a session fine.

But running a session is not the same as running a campaign.

A campaign, the kind I want to run anyway, asks a lot more questions than "what does the paladin roll to hit?" It asks what the dungeon is doing while the party is looting room eight. It asks whether the wilderness between town and the adventure site is actually dangerous. It asks what happens when the players decide to recruit hirelings, buy a boat, ignore a rumor for two weeks, or haul a monster corpse back to civilization to sell.

The Player's Handbook does not answer those questions. It was not designed to. And the Dungeon Master's Guide, frankly, mostly offers advice where I need procedure.

The books open on my table are not there because I am confused about what game I am running. They are there because each one answers a different question.

5e handles characters; OSR handles the world

Here is how I divide the workload.

5e handles character sheets, classes, spells, class fantasy, tactical combat, and player familiarity. If a player asks what they can do on their turn, the answer comes from a 5e book.

The OSR and NSR books on my table handle the world.

They handle dungeon time, travel procedures, wilderness risk, hirelings, mercenaries, treasure, town pressure, faction movement, wandering monsters, and what happens when the players delay, camp, shop, ignore a problem, or haul treasure back into town.

5e can tell me what the paladin can do. It is less helpful when I need to know what the town, dungeon, faction, forest, or expedition does next.

The division is not ideological. It is practical. I use the tool that answers the question I am asking.

Old-School Essentials is my dungeon machine

Old-School Essentials is probably the most straightforward book in my stack. It is a cleaned-up presentation of classic 1981 Basic/Expert D&D, which means it gives me access to a style of dungeon play where time, treasure, wandering monsters, empty rooms, traps, and hirelings all matter.

When I am stocking a dungeon, I am not designing a balanced combat sequence. I am rolling on OSE tables. Empty room? Cool, that makes the dungeon feel real. Trap? Better than a fight. Treasure with a guardian? Now the party has a real choice — fight, negotiate, trick, or retreat and come back later.

The dungeon turn procedure alone is worth the price of the book. It tells me exactly what happens every ten minutes of exploration: check for wandering monsters, mark off a torch, update light sources, note expiration of spells. The party can cover a certain number of rooms per turn. If they waste time, the dungeon gets more active. If they retreat, the dungeon resets.

5e gives me encounter resolution. OSE gives me the dungeon as a machine.

Cairn makes exploration dangerous again

Cairn is not always physically propped open at my table because it is not a hardcover. But its procedures are all over my prep notes.

Cairn is the book that keeps reminding me that wilderness is not supposed to be a loading screen. Its travel and exploration procedures are compact: you have supplies, you travel through regions, you make camp, you risk exhaustion and encounters. The GM-facing tools tell you what happens when the party runs low on food, gets lost, or pushes through dangerous terrain without resting.

I do not need a fifteen-page weather subsystem. I need one sentence of weather, one meaningful effect, and one choice.

That is what Cairn gives me. It is tight, it is fast, and it makes the space between towns feel real.

Knave 2e is a bag of sharp tools

Knave 2e is useful to me less as a complete system and more as a bag of sharp tools.

The random tables in Knave cover almost everything I might need to generate at the table: NPCs, dungeon contents, treasure, magic item effects, hazards, social encounters, and weird environmental details. When the party goes somewhere I did not prep, I can flip Knave open and have something useful in thirty seconds.

I am not trying to be pure. I am trying to keep the game moving.

Knave is also a useful reminder that old-school compatible design does not mean you have to run B/X. Ben Milton built a game that feels modern in its presentation but supports classic play procedures. That is the kind of design I am drawn to — tools that work at the table, not systems that demand conversion.

Shadowdark is the modern old-school book I keep meaning to use more

Shadowdark is the one I have used the least, which is funny because I still keep it nearby.

Right now, the thing I reach for most often is the random NPC material in the back. I ask players to roll dice for a race or a name, and then I almost never use exactly what the book gives me. I use it as a spark.

The point is not obedience to the table. The point is to get my brain moving quickly enough that the table does not stall.

Shadowdark's faction and settlement systems look promising, and I expect to lean on them more as the campaign expands. But I want to be honest about where things stand: it is a minor but growing part of my process, not the engine of the campaign.

NPCs come from everywhere

This is a good place to talk about how NPCs actually happen at my table, because it is the clearest example of my kitbashing approach.

A name is not an NPC. A voice is barely an NPC. But a role, a want, a flaw, a disposition, and a secret? That is enough to start playing.

I pull NPC material from several places. Shadowdark's quick tables give me a starting point. The Fated tarot system by Randall Nielsen gives me structured prompts around role, desire, flaw, disposition, and secret. There is an OGAS-style template floating around in my notes — I do not even remember the acronym perfectly anymore, but the point is simple: what do they do, what do they want, how do they act, and what are they hiding?

A random table result is a spark, not a commandment. If the table gives me "greedy innkeeper with a secret gambling debt," I do not feel locked in. I take the piece that works, drop the rest, and start playing.

What this looks like in Tower of Worlds

My current campaign, Tower of Worlds, is a 5e campaign run like a living sandbox on the volcanic island of Hizen.

Outlet City is the main hub. The party has a contact network, a reputation, and a growing list of people who want things from them. Outlet is not just a safe gear menu. It has brokers, banks, temples, magic item sourcing, property options, and reputation consequences. When the party comes back from a dungeon hauling treasure, Outlet is where dungeon loot turns into social consequences — people notice, people talk, people want a cut.

The Trailing Tail Hunting Camp and the Gilded Tusk Expedition are a good example of how this plays out. The expedition involves patrons, hunters, mercenaries, anti-ant smoke, a flickering camp barrier, a ward specialist under strain, a lure stone, trophy economics, ant pressure, predator pressure, and a bunch of NPCs who expect to get paid.

The monster is not just a stat block. It has a corpse, a trophy value, a rumor value, a labor problem, and a dozen people arguing about who gets paid.

The wilderness around the expedition is not a hallway painted green. The trip itself is the adventure. Supplies matter. Travel time matters. The risk of wandering into something you are not ready for matters. Cairn's procedures are the ones I reach for when I need to resolve that kind of pressure quickly.

Towns are not pause menus

One of the biggest shifts in how I run the game came from treating towns as pressure engines instead of safe hubs.

A town note is not useful to me because it has thirty paragraphs of history. It is useful because I can run one hour of town time with it. Law pressure, faction pressure, scarcity pressure, local trouble checks, consequences for delay, and reactions to player choices — these are the things that make a town feel alive at the table.

OSE's hireling and mercenary rules, Knave's social encounter tables, and Shadowdark's faction prompts all feed into how I run town scenes. The players are not in a pause menu. They are in a place with its own problems, needs, and timers.

The point is not nostalgia

I want to be clear about one thing: I am not using these books because old is automatically better.

I do not care about the golden age. I did not play in the eighties. I do not have nostalgic attachment to THAC0 or descending AC or any of the mechanical quirks that older editions demand.

I use these books because they solve live table problems.

The dungeon stocking tables in OSE save me prep time and produce dungeons that feel more interesting than anything I would design by hand. The travel procedures in Cairn make wilderness travel feel meaningful without requiring elaborate subsystems. The tables in Knave let me generate content in seconds when the party goes somewhere I did not expect. The NPC prompts in Shadowdark and Fated give me enough structure to improvise without panicking.

I like rules I can run more than advice I can admire.

That is the whole thesis. I am not building a retro shrine. I am building a campaign that is easier to run in the moment, harder to outpace, and more responsive to player choices. If the tool works, I use it. If it does not, I steal from somewhere else.

The books on the table

The books open on my table answer different questions:

5e tells me what the players can do.
OSE tells me what the dungeon does.
Cairn tells me what the wilderness does.
Knave helps me generate fast.
Shadowdark helps generate ad-hoc NPC’s.

Together, they make the world move.

Blog

I Accidentally Built a Real Estate System for My D&D Campaign

Welcome to Dungeon Masters Club

Why My 5e Table Has OSR Books Open

Recent posts

Blog

I Accidentally Built a Real Estate System for My D&D Campaign

Welcome to Dungeon Masters Club

Why My 5e Table Has OSR Books Open