Lessons Learned Running West Marches

Long-time WaHNtHaC... readers will remember that from 2018 to 2022, I ran a West Marches campaign. The other day, some folks in the TTRPG Finder: Korea Edition group chat (KakaoTalk...it's like What'sApp for Koreans) were talking about West Marches, asking if anyone was currently running one. I of course mentioned that I had run one, but I don't have the time to start it up again. 

It did get me thinking about the campaign I did run, though. I've been going over what I did right, what I did wrong, what I did different than Mr. Robbins' original WM campaign that worked, and how I might do it again if I were to do it again. I'm sure a lot of this is in the various posts I made about the campaign over the years. I should probably read over those posts myself. I'm sure they'll jog a few memories. 

Well, I'll get what I'm thinking down now, and maybe edit in some insights if I find time to re-read those old posts. These are in no particular order, just as they come to mind. 

Change: I'm not a bachelor in my 20s working a McJob. I've got a wife, kids, and a sometimes demanding job. The original WM campaign happened when a group of players got together, picked a time that worked for them and the DM, and made it happen. Not so for my game. It happened on my schedule.  That meant bi-weekly in-person games (usually every other Sunday), and occasionally (regularly during the pandemic) online games using Roll20. This meant that the player planning aspect of the original game was lost, and I tended to have a stable core of players that attended most sessions, but it still worked out OK in the end. 

Mistake: Starting the campaign with 5E. Not that there's anything wrong with 5E per se (yeah, some people will argue that point), but I wasn't an expert on all the spells, monsters, etc. I picked it because it was the current edition and I knew I could get players for that. But in the end, all the feats, spells, class abilities, monster abilities, and whatnot that I couldn't recall from memory slowed down the game and made it a pain in the ass to prep for. 

Correction: Switching to Treasures, Serpents, & Ruins (basically BECMI with my house rules) made it something I was much more familiar with, easier to prep, and easier to run at the table. Yeah, I lost a few players, but gained a few players as well. And I enjoyed it a whole lot more that way. 

Lesson: Next time, start with a system I know well. With random encounter tables being a big part of the game, and a rotating cast of players/characters, I need to know the system much better. Yesterday, I was even considering using BECMI/RC (minus the weapon mastery rules) to make it even simpler for players to drop in, roll up a PC, and game.

Change: Ben Robbins would provide the players with the AC and hit points of creatures they were fighting. I didn't do that. Even with 5E rules, which are a bit more tactical, I kept those secret. And the game worked just fine. 

Mistake: Working inside out. Obviously, I started preparing content for stuff close to the starting town (mine is called Silverwood), and prepping areas further out as we went along. I'd try to stay at least a session's worth of play ahead of the players. The problem is, not knowing exactly what was further out made it hard to include clues to things farther on in the Marches. I was often dropping rumors when the PCs went back to town, rather than letting them discover clues within the locations they were exploring. 

Lesson: Work outside in, at least on the big picture. THEN work inside out to flesh things out. If I do this again, I'll create a map and note the dungeons and special locations throughout it FIRST. All I really need to know is their location and a general idea of what they're about. Then I can plant seeds in areas closer to home that lead the PCs to explore further. 

My abandoned plan for a East Marches (using TS&R Jade) was started this way. I've got a map with dungeons and special locations scattered all through it, all named and with a bit of description. Of course, I used some of them in my current campaign, so if I did restart that project, my current players might be bored going over dungeons they've already pillaged. 

Change: Safe Havens. Rather than enforce a return to Silverwood at the end of every session, I had certain areas that could be found (or converted) into safe havens, where a session could end outside of town.  The next session, different PCs might be in the party, but we didn't worry about "continuity errors" like that. It allowed the players more confidence to explore, knowing they would only have to retreat a short distance to the closest safe haven at the end of a session, rather than save time to get all the way back to town. 

Lesson: I dropped a lot of TSR modules in my West Marches. Quasqueton (B1), the Caves of Chaos (B2), the Moathouse (T1), Castle Ravenloft (I6), White Plume Mountain (S2), the Steading of the Hill Giant Chief (G1), Xak Tsaroth (DL1), and plans to use more (like placing the Tomb of Horrors somewhere!). I wouldn't say it was a mistake using these module dungeons. We had some great sessions exploring them. But at the same time, having these generally large dungeons meant multiple sessions would be spent on them. And the PCs didn't always want to get to a safe haven to continue their explorations. So I broke the rule of always ending a session in Silverwood or a safe haven several times. 

If I were doing this again, I'd skip the modules. Sure, they allowed me to get a lot of content in one hex, and the players did have fun exploring them. But smaller dungeons specific to the campaign are better and easier to implement.  

Improvement: In addition to XP for creatures slain and XP for treasure (at least after switching to TS&R), I included XP for exploration. Every new hex explored, every hex crossed (explored or otherwise), and each dungeon or special location found were all worth XP. And the XP awards scaled up the farther out the PCs went. What I could have done better, and will strive to do better if I run this gain, is telegraph these awards more. Often, I'd just tally all the XP for a session at the end and award it, rather than let the players know how much was from each of the three sources. I think if they'd known how much pure exploration gained them, they might have pressed deeper into the "white space" on the map. 

Representing the OSR

Next month, Scott, Rowan and Shane are hosting Busan Con 2026, a two-day (maybe three with the Buddha's birthday being a holiday on that Monday) event. Aside from volunteering to help out with whatever needs doing, I'll be running a Star Wars d6 game for sure (This is the May), and probably a Missions & Mayhem game if I can get something together in time. The deadline to sign up to run games in the 19th. 

A guy named Dave, who I've only interacted with online, wants to run a workshop for new GMs. He asked for any experienced GMs to volunteer to be on his panel. It seems like most folks in and around Busan these days run very story-centric games, whether they're using 5E, PF2E, Daggerheart, or any of a myriad of indie games. And most people who'd sign up to share their GMing wisdom would be in that school of gaming. I signed up to be the OSR guy on the panel. 

Unlike some die hard OSR folks, I don't mind the more story-focused gaming crowd. It's not exactly my thing, as I've blogged about before. But at the same time, I see lots of people having fun with a game that prioritizes the PCs' character growth and playing out a storyline. Honestly, my Star Wars game has been fairly story-oriented, although not so much about a PC living out their "story." Missions & Mayhem is also very mission based, obviously, so each session I'm pretty much dropping the players into an ongoing story. I'm not demanding any particular sort of ending for the missions, though. That's up to the players to determine. 

For the workshop, Dave and I chatted a bit yesterday. He said he'd like each GM on the panel to give a 7-8 minute presentation on their DMing style, then he'll have us field some questions from him, then open it up to the audience. And if there's time, maybe one of the GMs can run a quick impromptu game with the folks to show off their style. 

Being an OSR representative, I'll probably be focused on the notion that sandbox play doesn't need tons of prep like many people think. Random tables and stocking procedures can save you a lot of time. And making an open world with situations, rather than story lines. I'll probably also get in a bit about backstory getting in the way of action, and how Gygax is reputed to have said something like "The first three levels of your PC ARE your backstory." 

I should look up to see what Gygax's actual quote was, or if that's even something he said and not just internet apocrypha.  

It should be fun! 

Are You Missing the Forest for the Trees? Plant an Orchard.

Recently, JB at BX Blackrazor wrote a long post (he does that) on why he doesn't like "rules lite" , primarily OSR/NSR style, games. Adam at Barking Alien wrote a reply on why he does like rules lite games (OSR or otherwise). I'm somewhere in the middle. 

I like enough mechanical crunch to make the game feel like I'm actually playing a game, not just doing some group story exercise with a bit of die rolling. But I don't need an excess of systems that bog down the flow of the game, either. Hence my preference for TS&R, where I take the simpler (but not rules lite) BX/BECMI D&D rules, and graft on the bits and pieces of OD&D, 1E, 2E, and even more modern games that I like to it. Along with a few of my own house rules, of course. Just enough complexity for me, without getting too burdensome to run.

That's all preamble to what I really want to write about today, though. These two posts, along with Adam's follow up on there being too much combat in old school fantasy games, got me thinking about something I'm sure I've addressed before, but probably years and years ago. 

One of the big strengths of original D&D and the Classic D&D line, in my opinion, is that is is explicit about the procedures for each stage of game play. Dungeon exploration turns -- spelled out and given a checklist to follow. Wilderness exploration -- also spelled out and given a checklist to follow. Encounters (both dungeon and wilderness) -- spelled out and given a checklist to follow. Combat rounds -- spelled out and given a checklist to follow. Reaction rolls and morale -- you get the idea. 

These are something that has been lost in a lot of newer games. Now, I haven't checked out every single OSR/NSR game out there, so I'm sure there are some that do these things. I know retroclones like Labyrinth Lord and Basic Fantasy still have these procedures spelled out explicitly. But WotC D&D, any version, really only does this for the combat side of the equation. And even then, some areas like Reactions and Morale are done away with for the most part. And it seems like many of the newer, rules lite games like Into the Odd, PbtA, and Black Hack derived games lack these as well (but I've mostly experienced these games from the player side, so I could be wrong here). 

I looked through my 1E books, and was surprised that the dungeon exploration turn doesn't seem to be spelled out explicitly anywhere. The process for wilderness exploration is described in the DMG (but not with handy checklists like BX and BECMI have), including for maritime, airborne, and planar adventuring. Combat procedures have maybe too much detail (those pummeling/grappling rules for example). But a simple explanation for the DM or players about how to structure an exploration turn for a dungeon seems to be missing. Maybe I was looking in the wrong place. Most of the guidance for that is in the PHB, but how to run a turn doesn't seem to be spelled out. 2E seems similar. Each individual mechanic is described with how it operates, but how they all fit together in the exploration turn or encounter seems to be more vague.

Procedures provide structure. Games need structure. Without structure, you can have game elements. You have mechanics for action resolution. You have mechanics for advancement. You have mechanics for spells/items/abilities. But you need a frame to hang them on. Without procedures for game turns, it's like you have a big box of LEGO pieces for your RPG, with an incomplete or missing manual to tell you how they fit together. 

Now, plenty of older games also fall into this trap. I'm loving playing and running d6 Star Wars, but while it gives you lots of good advice on setting up situations within the fictional world and a mechanic for action resolution, it is a little light on procedures for running non-combat activities. I get that combats need to be the one area of the game where the mechanics are most clear and transparent to the players, so they feel like they win or lose fairly. But the rest of the game should be transparent in that way, too. 

I know I've had times where a new player didn't understand how the procedures worked, and since they were joining my game which included veteran players, I didn't fully explain them. And then things are a mystery to them. I need to be more aware of this, and explain not just how to make a PC or how combat works, but how exploration and interactions work step by step. 

I like having those procedures spelled out, even if I don't always follow them to the letter. They are there when we need them. And of course, as old grognards, those of us who've been running these games don't need them spelled out. I know I personally used a lot of Classic D&D procedures when I ran 5E. The game lacks them, but I knew what to do because of my earlier gaming experiences. I imported the procedures that 5E lacked, but eventually tired of trying to shoe-horn in these elements to a game that fundamentally didn't want you to use that sort of procedure. WotC D&D, some old school non-D&D games, and a lot of the recent "lite games" seem, from my estimation, to want DMs to just present players with encounter situations and get to the skill checks/combat to resolve them. 

It's not railroad play in the traditional sense that players have no choice in what to do and where to go. But it is a sort of stunted play, where tactical choices are limited to "how do I do the most damage in this situation?" or "who has the best skill modifier to complete this task?" With set procedures, that are known to players as well as the GM, players can make more informed choices. GMs can tweak the procedures for special occasions, but most of the time will rely on them to keep the game moving. Players can engage in all the play-acting of their PCs they want during this, and that can be fun. But the procedures keep us from getting too bogged down in the role play or the mother-may-I style exploration interactions. 

Now I know some play these games FOR the role play. The more free "describe what you do, I'll tell you what happens" style play is also popular, and I can see why. I think it's good to have both in your games. But you need to enforce some order in the game to have choices matter. Procedures for exploration and interaction do that. I think it's a shame that most games have gone the path of only providing these procedures explicitly for combat. 

Individual game mechanics are like trees. An RPG that doesn't show you how the game mechanics connect and work together to make the game advance is like a forest. A game that connects and orders the various mechanics in a way that gives players choice and GMs flexibility to use or modify them as needed at the table -- that is an orchard. And it will bear the most fruit.  

Treasures, Serpents, & Ruins Game Master Guidebook is Now Available!

 I have just completed uploading the GMG to my Hidden Treasure Books store on DriveThruRPG. 

Here's a link!

It's got advice and rules for running a game the way I do it (mostly), including what I feel a new GM should know about running a game, or advice for people trying out old school style gaming for the first time. 

Most of you veterans who read this blog probably won't find much use out of most of it, but I do have some home-brewed modifications to the BECMI domain and war machine rules, and a different system for creating artifacts. Also my own version of the planes of existence. 

So there are some nuggets that might be useful even to the old, jaded gamer who's seen and done it all. Or at least I hope so. 

It's fully compatible with both my Ruby (standard Euro-D&D) and Jade (Asian D&D) sets. Oh, and I've made a few updates based on the past year of gaming with these rules to both the Jade and Ruby Players Rules books and the Bestiary & Treasury books. 

If you've already downloaded them, you might want to get the updated versions. There aren't many changes, but some mistakes have been fixed and a few things have been modified.

OD&D As a DM Instruction Manual

I've never really read through the OD&D books thoroughly. I only have them in PDF, and I've mostly just looked at sections here or there as a reference. I've referenced Men & Magic and Monsters & Treasure a lot more than I have The Underworld & Wilderness Adventures. So today, I went through that fabled 3rd volume and took some notes on what it covers, and how. This is in regard to my previous post, suggesting that I take a look at how well each edition acts as an instructional guide for new DMs. 

Organization: 

Dungeon Design -- notes on how to create your megadungeon, including lots of examples of ways to screw over players and make it a true labyrinth. 

Distributing Monsters & Treasure -- fairly similar to later editions, with notes on how to restock/expand/modify your megadungeon to keep things fresh.

Movement -- The exploration rules: movement and resting, finding secret doors, dealing with regular doors, traps, listening, and vision/light. 

Underworld Monsters -- rules for encounters: distance, surprise, wandering monsters, avoiding encounters (most monsters usually attack, but reaction rolls for intelligent ones).

Example of Dungeon Play

Wilderness -- the map needs castles, ruins, the Dungeon, a home town. Town adventures briefly mentioned.

Outdoor Survival -- explanation of how to use that map for unplanned/impromptu wilderness adventures, Castle Encounters explained in much more detail than in BX/BECMI/RC.

Referee's Map -- explanation that you can make your own map (but no advice on how), which can be useful for domain game play, and rules for hex-crawling and filling in a blank player map while exploring.

Movement -- all movement rates by hex (later listed as assumed 5 miles vertex to vertex!) per day, terrain penalties from Outdoor Survival. 

Wilderness Monsters -- rules for encounter distance, surprise, getting lost (a bit out of place), wandering monsters. Name level NPC wandering monsters are given more detail than in BX/BECMI. 

Evasion -- pretty similar to what's in BX/BECMI

Castle Construction -- not so different from BX/BECMI, but there is a note suggesting adventures defending a stronghold from incursions by monsters/enemies. 

Specialist NPCs -- what you'd expect, types, job descriptions, prices

Rumors, Information, Legends -- suggestions for developing rumors, and rules for players paying to find more information

PC Upkeep -- 1% of XP (per month I assume) needs to be spent on daily living. 

Baronies -- No more upkeep, now you get income. It suggests 2-8 villages within 20 mile radius of stronghold. There are notes on making improvements that may bring in more income/population, but no rules on how to manage that. 

Angry Villagers Rule -- because torches and pitchforks are fun!

Other Worlds -- go crazy with the campaign world

Land Combat -- AKA mass combat, use Chainmail

Aerial Combat -- use counters/minis on map, modified Chainmail rules, pretty extensive!

Naval Combat -- while this also has Chainmail suggested for man-to-man action, the ship combat rules in BX/BECMI derived from this, but this is more extensive. Includes swimming/drowning rules, water monsters, etc.

Healing Wounds -- natural healing at 1 hp per day, but not on the 1st day of rest!

Time -- keeping time for the campaign: assume 1 week per dungeon delve (including prep/recovery time), 1 day per turn wilderness exploring, 1 week real time is 1 week game time for 'downtime activities' or inactive PCs. 

Instructional Value: 

While I did learn a few things, and get some ideas for incorporating a bit more complexity to TS&R by reading through this (something I should have done years ago!), I don't know how well this booklet does at explaining how to run a game. It does give plenty of details for preparing the dungeon (less so for preparing the wilderness or town/city adventures, and even less for high level domain play). It explains some systems in detail, others are just glossed over or hinted as possible. 

There isn't much philosophy or explanation of the Why of game play, just a focus on the How. There is also zero guidance on actually putting together a group to play, dealing with problem players, etc. Maybe Gygax assumed experienced wargamers didn't need this sort of advice. 

My take is that if I had been given this box set as a kid, with the preparation to game I'd gotten from things like Choose Your Own Adventure books and things like the D&D cartoon, I could have made some decent dungeon adventures. But without Chainmail and Outdoor Survival, much of the rest would have been fairly useless to me. 

Still, it's not as obtuse as many people claim it to be. Most of the rules confusion I think comes from various vagaries in Men & Magic, or incomplete notes in Monsters & Treasure that again assume you have Chainmail. I found The Underworld & Wilderness Adventures to cover most of what's needed, if explanation is a bit short in many areas, and the organization is pretty good overall. 

I can definitely see why TSR thought that the various Classic D&D box sets and AD&D were needed to help explain the game better, though. The rules as written assume experienced wargamers, not newbies. As such, it's a decent rule reference but not a great instructional text.