Category Archives: adventure writing

Warts and All

Back at the turn of the century, I took a gig as part of the Living Greyhawk triad for the Texas/Oklahoma region (the notorious Bandit Kingdoms).  I learned a LOT about adventure writing during those two years.  But the most important lesson I learned was this: when you finish your draft, sit in an watch a different GM run your adventure for a new group.  This will reveal every unintentional red herring, weak spot, and broken element of your adventure.  It really is by far the best bang for your buck in the editing process.  You’ll be amazed at how much of your adventure is in your head and not on the page.

I remember sitting down and watching a new group tackle my first published adventure, The Bleeding Moon, which I’m still proud to say enjoys some notoriety in old Living Greyhawk circles (with its baby mimic and hasted-spider climbed-stone skinned zombies!).  I probably came away with 4-5 pages of handwritten notes after that session, including what happens if a player wants to learn necromancy from the villain at the end.  It was a humbling and eye-opening experience, and the final product was infinitely better for it.

Bloody Misadventures

Bloody Misadventures: Dramatic Battles on the High Seas

Of course, its easy to find playtesters when you are writing for a big organization like the RPGA. Flash forward 17 years to last year when I was putting the finishing touches on Bloody Misadventures: Dramatic Battles on the High Seas, a sea battles supplement for 7th Sea I published through the Explorer’s Society.  The playtest of the first draft with my group was an abysmal failure, with the whole thing falling apart inside of the first action.  The second playtest went better, but revealed a flaw in my thinking as the players were all to eager to pool Raises to unleash monstrous amounts of hits on enemy ships.  Meanwhile, I was seeding drafts with a handful of folks, trusting them to play out scenarios with their groups.  Each time I’d get little snippets of feedback, bringing the project closer and closer to completion.

In the time it took to write Bloody Misadventures, I finished three other products for the Explorer’s Society!  That’s how much fiddling I took with it.  An idea would hit me and into the book it would go, sometimes only to be ripped out and shredded days later.  In the end, I took Nancy Pelosi’s advice: I had to release it to find out what was in it.  So the project that started in April of 2017 was released from its cage in the lab in November!  Initial Sales were good and have remained consistent.

So last month, Tabletop Radio Hour did a review of Bloody Misadventures on one of their shows.  The Cast were positively intrigued and promised to feature a sea battle soon on their Actual Play podcast.  About two weeks later they delivered.  I was heading home on a road trip through the Texas Hill Country when the episode dropped and I listened.  Boy, did I listen!

I listened to every pause.  Every rules reference.  Every indecision.  Every shrug.  Every misstep.

Yeah see, its amazing what you find out when you listen to someone else run something you wrote.  You’ll be amazed what’s in your head and not on the page.

Oh don’t get me wrong.  It wasn’t bad.  Most of it played out really well!  Everyone seemed to have a good time (I’ve no doubt they’ll reveal all in a follow up review).  But there was way to much head scratching for my tastes.

So when I got back to the home office, I wasted no time doing additional edits to clarify the text where it needed it.  Because I didn’t want to waste this opportunity.  Because Bloody Misadventures was a lot of work to write and deserves to be the best set of rules for what it does that it can be.  Because I don’t want play to suffer for my contributions.  Because, as a 7th Sea GM, I still want to know what Cross the T! does in play, and hope other seekers to find the answer in something I wrote.

But the moral here remains: before you turn your baby loose, before you add that “-final” tag to the file name, before you send that master file on to Lulu or Drivethru or your publisher, hand over the keys to someone else to take it for a drive around the block while you ride in the backseat.  You won’t regret it!


From Dumas With Love

Last week while my wife is away at a conference, I spent my evenings catching up on the BBC’s The Musketeers.  My wife isn’t really a fan so when we got sidetracked halfway through the season, I figured it would be awhile before I got back to it.

Watching episode 5, the Return, I thought this would make a fantastic adventure for Witch Hunter, something in the mold of Countrycide (Torchwood season 1), where the mundane becomes a real threat.  Here’s an official synopsis of the episode:

When Athos is kidnapped and taken back to his estate of Pinon, The Musketeers go in search of him and find themselves in the middle of a battle against a nobleman, the Baron Renard, who is shocked by Athos’ decision to reject his nobility and is determined to seize the land for himself. As The Musketeers train the people of Pinon in combat and defend them against multiple attacks, Athos is forced to confront his past when he encounters an old friend whose life was ruined by his actions years ago.

Witch Hunter lends itself to the set up perfectly.  The characters have often renounced their former lives to embraced their new role as monster hunter.  All you need is a player with the Noble background and you are good to go.  Or perhaps an NPC witch hunter, with the cadre dispatched to find him.

The scenario offers several complications that would make it challenging for any group:

  • The main villain is a landed noble, with all the protection and privileges that go along with that station.
  • The villain also possesses a considerable fighting force.  They may be minions, but 100 threat 2 minions are going to hurt.
  • The heroes are at a real disadvantage here.  If they pull rank as witch hunters, the villain can just call in the church and have them branded as heretics.
  • Abandoning the peasants to their fate would certainly be worth a point or two of damnation.
  • The social complications and logistics of training and commanding a ragtag force of peasant soldiers will likely test several skills the PCs have been neglecting.

This scenario plays straight at the swashbuckling or even the colonial aspects of Witch Hunter.  So lets consider a few twists we might apply to really enhance the Witch Hunter flavor of the scenario.

  • Play It Straight: We don’t really change anything here.  The Baron and his son are both normal men (lieutenants), though arrogant, privileged and terrible examples of humanity.  The role of Catherine could easily be assumed by a childhood friend, an old lover, or even a former mentor of one of the witch hunters (not necessarily the noble) who has an axe to grind.  The Baron could be driven by an old grudge or rivalry.  That the witch hunter has walked away from his family obligations matters not; the matter must be settled in blood!
  • The Demonic Instigator: After a tragic accident befell his son, the Baron beseeched dark forces for the young man’s life.  He revived, but was forever changed.  Now he forces his father’s hand, consumed with avarice and greed.  There is something about the Noble’s land he covets, and no reason will deter him from his prize. (Sort of a toned down version of the Solomon Kane movie.) Alternatively, the Baron or his son (or both) have fallen under the spell of a witch or warlock who seeks vengeance on the witch hunter(s).
  • Sanctuary: The NPC standing in for the role of Catherine has a dark secret.  The Noble’s family granted her refuge as a child.  Now dark forces have sought her out and recruited the Baron to their cause.  How will the witch hunters respond?  Will they surrender her to her fate?  Will they shelter and protect her?  Perhaps the nature of the secret is such they must deal with her (or not) themselves.
  • The Beast: Something has been preying on the villages of both manors.  The Baron believes these criminals have found refuge within the Noble’s lands, while the villager’s place the blame squarely on the Baron.  The beast hides amongst them, eager to shift the blame away from itself.
  • The Dark Secret: The Noble’s manor holds a dark secret that, if discovered, could ruin the witch hunter and his family.  Perhaps the Baron is aware of it and uses it as leverage against the cadre, or perhaps his fate is tied to the secret as well.  Perhaps the secret is so terrible, the Noble needs to keep it from his or her Order, perhaps even the rest of the cadre.  This could be tied to the character’s Catalyst, or a startling revelation made early in the scenario.
  • The New World Order: The action is moved to the New World, to a colony on the fringes of civilization.  Replace the Baron and his men with agents of a competing country (French, Spanish, British, or Dutch).  The villagers could be colonists or natives.  The witch hunters could have ties to the colony (base of operations) or answer the summons of an old ally, a contact, or another Witch Hunter.
  • The Invisible World: The meddling of a heretic scholar or occultist has inadvertently opened a sustained gateway to the Invisible World.  What emerges is not the lone entity the occultist sought, but a warlord and his demonic army, intent on cementing a foothold in God’s creation!  These could be fae (unseelie), or something even more horrific.  Either way, the numbers are too overwhelming for a small cadre of witch hunters, and by the time others might be brought to bare against them, these invaders could have slaughtered hundreds (not to mention called in support from a few Forbidden Societies, making the job even more difficult).  The cadre’s best chance for success here is to rally the locals against this threat, but the risk is high.  (The last two recent Mummy movies would be good inspiration for this…if you can stand to watch them.)

Pacing Investigative Adventures

All to often, in my experience anyway, investigation adventures boil down to a pretty predictable formula:

  • About an hour of set up and introduction
  • Around 3 hours of Twenty Questions thinly disguised as “roleplaying”
  • A single boss fight that runs 30 minutes to an hour, but no one cares because everyone is tired

Now, there are probably a few people out there who read this and think, “Rolelplaying! Hooray!” I’m not one of them.  I find this whole process especially tedious and BORING.  Not only does it flow contrary to every other form of popular entertainment, but your game becomes very prone to disruption – probably from people like me!

What’s even worse?  I do it too.  And it pisses me off when I do.  Because at the very least we GMs should aspire to run games that we would enjoy.

And the real pisser is that breaking out of that formula is so damn simple the only reason we don’t is because we’re lazy…or, for you parents out there, tired.

But lets say you’re reading this and saying, “well what should I be doing instead, Mr. Know-It-All?!”  Glad you asked.

We’ll talk about pacing here in a moment.  But first, let’s give a hat tip to Robin Laws and Gumshoe, who put to print what we should have been doing all along (and plenty of non-published GMs were probably already doing).  When running a mystery or investigation, the first clue is always free.  No skill roll necessary.  Your game should never grind to a halt because of bad dice rolls.  Dice rolls can elaborate on clues, or find secondary (or tertiary) clues, but the first clue is there for anyone with the presence of mind to say, “I search the room,” or, “is there anything interesting about…”  Because as a player nothing is more infuriating than missing an “obvious” clue.  And because as a GM nothing is more irritating than arguing with a player about what is “obvious” or not.

But lets get to pacing, because that’s where everything really breaks down.  Games that trudge along from A to B to C do so because of poor pacing.  A well paced game should play out a bit like a good piece of cinema or literature, with peaks of tension followed by a bit of relief for the players to catch their breath and consider what’s going on around them.  It’s not exactly the same – because those are passive forms of entertainment while gaming is active – but the principles remain the same in both.

To keep the primary investigation interesting and tense, you need to break it up a bit.  You do this with sub-plots and unrelated encounters.


Any time I prep an adventure session, I have a pretty good idea what PCs (and what Players) are really going to take to it.  Rather than leave the rest of them to stand in the shadows, I make sure to set up a subplot or two for 2 or more of these players.  I don’t script these out, or even create a resolution.  They usually start out as nothing more than a hook: A young poet becomes enamored with Tamsin and is willing to risk anything for her.  Or Raphael meets up with someone important from his past.  These don’t have anything to do with Plot A, but interjected at dramatic points they give a different player a chance at the spotlight while the rest of the crew reflect on the last clue.  This keeps everyone involved in the game, not just the characters who are hyper optimized for the scenario.

Subplots work best when they focus on a single character or small group. You want to use them to jump away from the main action, giving the rest of the group a brief pause, either to relieve or heighten tension. In an RPG, it gives the other players a chance to think too, to ponder their next move. Used judiciously, this technique cuts down a lot of your “ummm” and “uhhs” time.

Done this way, subplots are sort of mini-solo adventures. And you want to keep them short. Don’t cut away from the group to focus on a single player for 30 minutes. This is about creating space and tension as well as moving the spotlight around. 10 minutes is probably as long as you want to spend on a subplot at any given time. Again, not a hard and fast rule, but you need to have a grasp of the drama of it.

Subplots can be completely unrelated to the main adventure, but they can also compliment or conflict with it.  This is another way to create a sense of tension at the table.  Since a subplot often focuses on one player, his or her actions alone can be a boon to the whole group or put one more hurdle in their way.  When you do this, do your best to keep table-talk to a minimum.  It doesn’t matter how good a grasp Jeff has on the mystery, if his character isn’t present he shouldn’t be allowed to interject.  This will almost always illicit groans or cheers from the rest of the table depending on how things play out, plus watch as the group performs all manner of logic gymnastics to “come to the rescue” as it were.

One last word on subplots: use them to spotlight and empower the player, not to create a damsel-in-distress moment.  That is, don’t use them as an excuse to kidnap, capture, or otherwise confine the player’s character from the rest of the action.  “Sorry guys, I wish I could help with exploring these mysterious ruins, but I’m stuck in this deathtrap,” is not going to be popular.  Of course, if the player’s actions lands them in hot water, that’s a different matter.  But you never want your subplot to derail your main plot, player agency notwithstanding.

Non-Related Encounters

You know what raises the stakes more than knowing the villains behind the conspiracy are out to get you?  Knowing that the mafia is to.  Because now you have one more thing to worry about.  It’s a distraction, and possibly worse.  So yes, in the middle of that high stakes race against time to diffuse the bomb, why SHOULDN’T PC A’s Enemy show up?  Why shouldn’t that street gang you smacked around two sessions ago come looking for revenge?  Why shouldn’t the Inquisition leap from the shadows (cue Monty Python jokes)?  Don’t overdo it.  These sorts of encounters work great with mooks and minions.  This isn’t about soaking the players’ resources, it’s about giving them something unrelated to Plot A to worry about and give them a brief break from that tension to knock some bad guys around.  That’s not to say these encounters can’t be dangerous, only that they shouldn’t overshadow the main goal.  You don’t want to hit your players so hard they decide to forget the investigation and go looking for revenge.

A Pacing Formula for Success

This isn’t hard science.  I’ve broken it down to times here, but that never works in practice.  Introduce things at dramatic intervals.  When every player at the table says, “holy crap, what does this mean?!”, that’s a pretty good sign its time to shift gears for a minute.  With that in mind, here we go.

  • Bonus Points: Kick off the scenario with an unrelated conflict, Indiana Jones style.
  • Break for a subplot every 30-45 minutes, or after a major clue has been realized.
  • Introduce an unrelated conflict about a third of the way through the session (in a 4 hour game, around the 1:30 hour mark).  Have a second one prior to the climactic encounter(s).
  • The “Big Fight” should actually happen just PRIOR to the confrontation with the big bad.  That’s why villains keep henchmen after all.  If you have complimentary subplots, this is where you tie everything together.  If possible, this conflict should be TOUGHER than the climactic conflict.  In resource management games like D&D, it means the group will not be going up against the big bad at full strength, creating even more tension and encouraging alternative strategies.
  • DO NOT give the group time to regroup, rebuff, or recuperate before the climactic encounter.  Time is of the essence.  If they pause to regain their strength, the main villain gets away or has time to implement plan B.  It shouldn’t mean the group fails, but their victory isn’t clean.

Formulaic or no, this approach is guaranteed to add spice to any investigation scenario you run.  Some of these tricks are easier to do than others, and its worth changing them up a bit once you get comfortable with them.  You never want things to get too predictable.