Tag Archives: preparation

Unfrozen DMs, Annoying Spells, Dynamic Battles, and More Insights from the Comment Section

4 Replies

Time for another trip to the comment section.

The unfrozen dungeon master

In The Plight of the Unfrozen Dungeon Master, I wrote about DMs returning to Dungeons & Dragons and adapting the changes in the way folks play the game.

Edgewise wrote “One thing everyone needs to learn is that there are many different legit styles of GMing. There is no single new and current approach, and if there was, it wouldn’t be ‘better.’”

My post highlighted a shift in play style from cooperating to overcome deadly challenges to a style aimed at developing characters and their stories.

Even in the same campaign, D&D can accommodate both styles. To span styles, DMs need to separate their roles in the game. Unfrozen DMs like me first learned to act as impartial referees who bring challenges and control monsters. Even in a story-focused game, that role remains important because compelling tales put characters through a wringer. We unfrozen DMs know when to tell players no(sometimes). The collaborative storyteller learns to say yes and become the character’s biggest fans. We can all learn to welcome the players ideas and weave them into the game.

This post also prompted some discussion of Matthew Finch’s A Quick Primer for Old School Gaming, a pamphlet I mentioned in A Lack of Ability Checks Shaped How People Originally Played Dungeons & Dragons. The pamphlet merits a read. Just as unfrozen DMs can learn from the game’s innovations, newer DMs can learn from D&D’s original style of play.

I failed to explain why a Lair Assault game made such a bad match for an unfrozen DM’s style. Thanks go to Marty from Raging Owlbear for making up for the lapse.

“Lair Assault was an organized play event where players were challenged to optimize a party build in order to defeat a specifically designed difficult scenario.

“It was not a home game. It was not Adventurers League. It was more akin to a cooperative board game where it was the players vs. the game with the DM acting as the ‘AI’ of the scenario.

“This means that the DM changing the Lair Assault scenario is breaking the whole concept of the Lair Assault. The whole point of Lair Assault was to stick to the rules as written to “win” the scenario. If the DM changes the scenario as written, it’s not fair to the players who signed up for that specific game mode. The DM is breaking the agreed upon play style.”

Preparing situations

Don’t Prepare Plots and Encounters—Do This Instead advised DMs to build games around situations rather encounters.

Grimcleaver offered an alternative approach that mixes specific encounters with some improvisation.

“Take your normal map with encounters scattered around, cut out all the same encounters and put them in a bullet point list. Then just sit back. When the time seems set for one of the encounters–run it. They need be in no preordained place on the map so long as the circumstances are right. They collapse the mine entrance with an avalanche? Fine, but a ways out they discover tracks–a warband of the creatures must have been out when the cave was sealed. If they do the expected thing and follow them into the woods then your first encounter can be whatever you’d planned, but in a clearing in the woods. If they come up with another crazy out of the box solution and subvert that situation? Well that’s fine, you have the encounter prepped and in your notes whenever you need it–and the PCs get to do something else clever.

“What I try to go for is to have a list of encounters that are both dramatic and balanced that I can drop in anywhere to use as filler or twists or kickoff points to further the action. If what the PCs are doing is proactive and interesting on its own, that’s better. I’ll stick with that. But when things slow down and the players need an external stimulus, bam I can throw down an encounter that works.”

This technique resembles the way I sometimes manage wandering monsters, so it makes a good addition to a preparation toolbox. But DMs who lean too heavily on the technique risk robbing players of meaningful choices. If options lead to the same encounters, do the players’ choices matter? See Illusionism: if player choices seem to matter, does it matter if they don’t?.

Character introductions

Replying to How to Get D&D Players to Make Unforgettable Character Introductions That Take a Minute or Less, Teos “Alphastream” Abadia reminded us that you don’t need a DM’s invitation to make an unforgettable introduction. “It may be worth mentioning that as players, we can also plan for a generic ‘fit anywhere’ scene. When a DM asks for a character introduction, you can drop it in. ‘My introduction isn’t about me standing here before you, but what led to my arrival. It started with a few shouts down the street, as I battled a pair of ruffians…’”

Spell templates

Regarding How to Create Wire Spell Templates for Dungeons & Dragons, skwyd42 asked a question: “I agree that wire templates are quite nice. However, these cones (and also circles) will have the issue of ‘partial squares’ when using a grid. I’ve yet to find a satisfactory solution for this issue. Any ideas?”

The Dungeon Master’s Guide gives this answer: “Choose an intersection of squares or hexes as the point of origin of an area of effect, then follow its rules as normal. If an area of effect is circular and covers at least half a square, it affects that square.” Likewise, if a cone fills half a square, it affects the square.

Alphastream offers a method suited to making square templates. “Should it be of help, during the 4E days I used a technique one of my friends had, using window screen tubing and wire. That same technique can be used for 5E.”

Gary Gygax’s plans for AD&D

In reply to Gary Gygax’s Thwarted Plans for Second-Edition Dungeons & Dragons, a couple of posters mentioned Joseph Bloch’s game Adventures Dark and Deep. This AD&D game attempts to capture the second edition Gary Gygax would have created, based on exhaustive research into Gary’s stated plans.

Joern Moller writes, “Isn’t Castles and Crusades (which Gary consulted on and supported) the game closest to his ideal version of D&D?”

Correct. In Gary’s later years, he favored his own Lejendary Adventure Game. But when an occasion called for a modern take on D&D, he ran Castles & Crusades.

Annoying spells

In a response to How new changes created the 4 most annoying spells in Dungeons & Dragons, Andy Walker succeeded at diplomacy, by the standards of Internet comments.

“I will try to be diplomatic here, and probably fail. I like some of the spells you hate in this post. Banishment? Sure it upsets the table temporarily, but the target gets a save, and IT WORKS BOTH WAYS. Try letting the villain banish the Barbarian or the Wizard as his opener, and suddenly the PCs are the ones on the defensive, pinata side. When a villain is banished, have him return invisible, or in Otiluke’s Resilient Sphere. Just because the baddie is gone, doesn’t mean he/she suddenly becomes stupid or helpless.

“Counterspell? One of the best spells in the game. If you want an interesting duel between mages, this thing rocks. Nothing is more dramatic than causing the evil necromancer’s Disintegrate Spell to fail, or a PC’s high level spell, carefully selected for just this foe, to fizzle. And counterspell against a counterspell (yup, totally legal)? Mage Battle Royale!!!

“This whole column seems like ‘things that annoy me as a DM because I didn’t prepare contingencies, and I’m too nice to use them against the PCs.’”

If I ran a regular game with players who enjoyed such reprisals, I would relish banishment. However, most players find seeing their characters sidelined by banishment or counterspell more frustrating than fun. Fortunately for most players, unless DMs opt to drop spellcasters into most encounters, and then routinely switch up the stock non-player character spell lists, the annoying spells rarely work both ways.

Tracking initiative

I discovered my numbered technique for tracking initiative from Alphastream.

To use numbers, create a set of tents numbered from 1 up. When initiative starts, the players compare numbers and take the card the matches their place in the order. The highest takes 1, second highest 2, and so on. The DM takes cards for the monsters’ place in the order. Everyone sets the numbers at their spot at the table so everyone can see their place.

“I have to give all praise to Paul Lauper Ellison, an amazing gamer and friend I first met during the days of Living Greyhawk 3.5 organized play,” Alphastream commented. “Paul came up with the idea of numbered tents (and made his first ones) for special Living Greyhawk events like Battle Interactives, where time was a big factor for success. We could shave off many minutes of the DM pausing to figure out who went when by using his tents.

“During the first round, Paul would simply start placing numbers as the DM called out someone’s turn. I do the same as a player. I must say that by the end of the adventure/event, 99% of DMs have stopped tracking initiative on their end and are letting us do it, because it is so much better. Every player knows when their turn comes up, no one gets skipped, and we know when monsters go (typically, we place a number in front of the DM for each group of monsters, so a DM might go on both 4 and 9). It really is a brilliant system. These days, you see the system used all around Adventurers League, and it is all thanks to Paul!

As for handling monster initiatives, Alphastream writes, “I still assign them a number. Because most encounters have a few types of creatures (a bugbear, three orcs), and cards are used for each group of monsters, the players are used to seeing the DM have several numbers at the start of combat. They don’t know if a number belongs to one of the orcs (maybe one of them is a spellcaster) or something else, until the initiative passes (and even then, they may not notice).

“It can also be fun to announce it. ‘And on number 5… nothing happens!’ It creates mystery and excitement at the table, as they wonder what will happen. If you use initiative numbers for things like traps and events (on every number 4, the volcano causes the ground to shake and all creatures make a Dex save to avoid falling), the players won’t always assume it’s a hidden monster. It really works well overall.”

Dynamic combat scenes

In response to D&D Locations and Tactics that Encourage Dynamic Combat Scenes Alphastream offered more suggestions. (As you see, Alphastream’s comments make half this post. Thanks, buddy!)

“One thing I would add is to give the characters obvious goals inside the room, to draw them in and give them things to do. Some examples: A monster is heading towards a lever, so it probably should be stopped. The treasure is in a clearly visible alcove, but a huge stone wall is dropping down to seal it off. A clockwork device begins to slowly count down.

“When it comes to foes, making them interesting really helps. Four goblins and a wizard… everyone will target the wizard. But when you have goblins throwing strange alchemical or mechanical devices at the party, or if the goblins control levers that activate traps, suddenly players won’t know where to focus fire, and the battle gets interesting and dynamic. Even vivid descriptions can be effective. A common outcome in my home campaign is that they don’t focus fire (despite being very tactical) because the monsters all demand attention.

“Terrain is also worth underscoring. Cover is important, but the design of the room itself will drive how players react. A ramp up the middle, elevated places, stacks of crates that can topple over, a chasm, a pit, a rope bridge with ropes you can clearly use to swing across, and other such terrain will all change the behavior of players and encourage at least a few of them to engage the battle in fun ways.”

My terrain post also drew suggestions for dynamic encounters from Timothy Park. He adds too much good advice to quote here, so go back to the post and read the comment.

In the same post, I faulted the adventure Hecatomb for a lack of terrain, which set up monsters for execution by sharpshooters and other ranged attackers.

Stevey writes, “I helped with Hecatomb last spring also here in Montreal. I was to be DMing Tier 3. Upon reading it, I immediately noticed the open battle field effect you mentioned. I proceeded to create a dozen ‘Claws’ and a huge box of scatter terrain to hand out to the 10+ DM’s to help with this. I really think it helped. We even used it to help raise money (the Epic was for a charity) and gave away the terrain to those that donated.”

Check out Steve’s stunning terrain props.

The terrain post led Duncan Rhodes from Hipsters & Dragons to create a list of terrain features that would improve a combat scene. See 101+ Terrain Features for Better Combats. I plan to draw from the list for inspiration.

From the authors of a 40-year-old adventure

Finally, during this site’s first year, I praised one of my favorite adventures, Escape from Astigar’s Lair, a 1980 tournament adventure Judges Guild sold for a mere $2. Authors’ Allen Pruehs and Ree Moorhead Pruehs, found my review and wrote, “Wow. Thank you for the compliments. We are blown away!” Their notice delighted me. Incidentally, I also listed Astigar’s Lair, among the 5 role-playing products that shaped how I play Dungeons & Dragons 1978-2000.

Event-driven D&D Adventures Aren’t About Events; They’re About Villains

2 Replies

The plot of every vintage James Bond movie resembles a role-playing scenario based on an investigation and events. A hook like the theft of an atomic bomb sets Bond into motion. In an investigation, he chases leads from one situation to the next. The events come when the villains’ agents attempt murder, usually while Bond pilots a gimmicky vehicle or skis downhill.

Lloth and Drow at Gencon

Event-driven adventures aren’t really about events; they’re about villains. Unlike dungeons or the classic situations, I described in an earlier post, event-driven adventures stem from dynamic villains working to achieve some goal that the players feel compelled to foil. “Villain adventures are, by their nature, more dynamic,” the Angry GM writes. “The players aren’t pursuing a goal so the game master isn’t completely reliant on the players to drive all the action in an otherwise static adventure setup. Instead, the villain can take actions and the adventure is constantly changing.”

To prepare and event-driven adventure, plan villains instead of events.

Villains require three elements:

  • a goal
  • a plan to reach their evil ends
  • assets that can help bring their goal

Every villain must have a goal. For bad guys, the usual aims include power, vengeance, and, in Dungeons & Dragons, to harvest souls for ultimate power. Any of these goals make the foundation of a sound villain, but more evocative goals can make more compelling foes. Strahd Von Zarovich aims for power and vengeance, but he also wants to win a woman who would rather die than return his love. She does, more than once. Such depth helps make Strahd a classic.

Every villain needs a plan to gain their desires. In D&D, they make plans to conquer kingdoms, bring worshipers to dark gods, and so on. Those plans shape adventures.

In a typical D&D game, most players will act to oppose signs of evil, especially if thwarting evil would also bring treasure. The game builds on such calls to action. But plots that affect the characters directly make more compelling conflicts. Look to the player characters’ bonds for inspiration. If a wizard in your game seeks arcane knowledge above all else, then a plot that threatens to burn an ancient library would provoke the character.

When some DMs develop evil plans, they imagine a timeline of how the plan advances if the players fail to intervene. Such plots can continue all the way to the moment when Dendar the Night Serpent devours the world. But the game depends on the players meddling, so steps 13 and up rarely show at the table.

A better plan starts loose and develops through play. At first, the players may only see signs of evil.

An offstage villain can develop into a compelling foe. “One of the key components to creating tension is the slow burn,” Courtney Kraft of Geek and Sundry writes. “Don’t show your villain fully right from the start. Perhaps there are mysterious things happening around your heroes. The mystery is fun, so take your time. Give your players small tastes of what’s to come. Leave them warnings. Send minions. Maybe even let them experience a fraction of the villain’s power.”

As a tool for introducing villains to a campaign, I like the concept of fronts. The idea comes from the games Apocalypse World by D. Vincent Baker and Dungeon World by Adam Koebel and Sage LaTorra, but the concept’s best lessons apply to games like D&D.

Fronts abstract villains. “Each is a collection of linked dangers—threats to the characters specifically and to the people, places, and things the characters care about. It also includes one or more impending dooms, the horrible things that will happen without the characters’ intervention.”

Game masters planning fronts imagine grim portents that expose a villain’s progress toward a sinister goal. You reveal these portents to raise tension, or when players need a call to action. I liken fronts to weather fronts, because with both, you spot a coming storm in a distance. The early portents start a slow burn without necessarily calling players to action.

The game rules describe another sense of the term. “‘Fronts’ comes, of course, from ‘fighting on two fronts’ which is just where you want the characters to be—surrounded by threats, danger and adventure.”

In a campaign with multiple potential villains, grim portents help introduce the group. Such warnings suggest villains without much preparation. See what captures the players’ interest, and then develop the foes behind the portents. The players’ response to multiple portents can help shape a campaign’s direction.

Too many fronts advancing too quickly can make players feel overwhelmed and under-powered. Much of the fun of D&D comes from a sense of potency, so second fronts work best on a slow burn. They suggest an active world full of peril and opportunity.

The players’ actions to thwart the villain will eventually force a reaction. Perhaps the enemy slays someone the heroes recruited as an ally or captures some magic artifact the heroes need. Suddenly, the adventure comes alive as the players face a dynamic foe.

Villains need assets that help advance their plans. Most D&D villains start with monsters ready to fight. These assets range from faceless mooks to lieutenants colorful enough to overshadow their boss. Think Odd Job or Darth Vader. In more nuanced scenarios, the villain may bring allies with their own goals. Such friends of convenience can bring depth to an adventure by making adversaries that the heroes can turn to their side, or at least against the villain.

To build an event-driven campaign, dungeon masters need to imagine a villain’s assets, plan, and goal. But you don’t need a final, personified villain. That creation can wait. Waiting to develop a lead villain can even bring some advantages.

When DMs invest time in villains, they start to dream of recurring enemies who appear though the course of a campaign and escape alive.

In D&D, villains don’t recur like they might in a book or movie. The game strips away plot armor. As soon as recurring villains appear onstage, the players will attempt murder. Sometimes DMs can engineer an escape without railroading, but usually villains just survive a round or two.

In D&D, recurring villains work behind the scenes. Players learn of their hand through their reputation, their servants, and the accounts of would-be heroes who fled for their lives. The characters may thwart a plan, but the recurring villain’s goal remains to inspire another, more diabolical ploy. Each scheme needs to escalate the stakes. At level 1, a villain’s first plot might act to corrupt the kindly, village cleric. At 3rd level, the entire village becomes the target. In a campaign, some of the plans may succeed, raising the conflict further.

In an episodic campaign, keeping the lead villain undefined can help set a recurring villain who resonates with the player and even develops a record of beating the heroes.

Whenever players confront a bad guy, think about making the scene an audition for the role of ultimate villain. In most episodes, some agent of villainy will work a plan, fail, attempt escape, and perish. But sometimes, the players suffer a setback, and the villain escapes or even succeeds and complicates the characters’ lives. Consider promoting that enemy to the big bad. Justin Alexander advises, “The real key here is to simply refrain from pre-investing one of these guys as the ‘big villain.’ Basically, don’t get attached to any of your antagonists: Assume that the first time they’re in a position where the PCs might kill them that the PCs will definitely kill them.” If someone survives or prevails, you have a villain the players can hate. That enemy may need more power for a lead role, but the game is D&D. Just back a winner with a dark pact, evil artifact, or battle-ready servants.

By preparing active villains with goals, plans, and assets, you can prepare adventures that follow an arc that resembles a pre-planned plot. But you prepare without assuming what the players will do or how the game will advance.

 

Dungeon Masters, Instead of Plots, Prepare Secrets, Clues, and Leads

4 Replies

Planning a Dungeons & Dragons game around encounters and plots leads to trouble. In my last post, I explained how preparing encounters proves less flexible than preparing situations.

Situations can take dungeon masters far. Every D&D adventure published before 1982 presented a situation ripe for adventure. These early adventures might include broad goals, like destroy the evil behind raiding giants, but these modules mapped out situations and then set characters loose. Nothing broke this mold until N1 Against the Cult of the Reptile God in 1982. Before N1, every published D&D adventure was site based. The choices that drove these adventures all amounted to a choice of doors or adjacent hexes. N1 paired an investigation with a scenario where events happened even if the characters did nothing. Since then, both features have appeared in countless adventures. (See How N1 Against the Cult of the Reptile God Changed D&D Adventures for Good.)


Such features make adventures resemble plotted stories, so dungeon masters preparing for events and investigations often imagine plots for their scenarios. Then they contrive ways to make players follow the plot. When the players’ choices upset the plan, the DM feels tempted to invalidate the diversion. Sometimes, to avoid railroading, DMs work to build player-proof plots by including contingency plans for every choice and outcome. The preparation effort can swamp a DM.

As an alternative to plotting adventures, DMs can turn to situations. Adventures designed around situations allow both investigations and events, but other techniques make preparing and running such scenarios easier.

Instead of preparing plots, prepare leads.

Leads go by other names. Some writers call them clues, secrets, or hooks. When they discuss clues and secrets, their terms cover scraps of information that may lead or may serve another purpose. I favor “leads” because the word matches my main purpose, but I’ll use the other terms too.

Suppose the characters investigate a string of bloody murders in a village, they might discover the following leads:

  • All the murders center on well, recently dug to replace one that went dry.
  • A farmer found blood on the clothes of family members, but believed their innocent explanations and hid the evidence.
  • Children have spotted parents wandering the woods at night and returning at dawn.
  • A forester who cared for the woods now spends days in a drunken stupor.

Clues like these leave many angles that invite investigation. Each could lead to more clues.

Leads serve as one way DMs direct players through a plot, so in a sense, planning leads instead of plots just represents a change of mindset. But leads encourage choices. When players find enough leads, they face choosing which one to follow. Making choices and seeing outcomes generates the fun of role-playing games. Leads also offer more flexibility than plots. DMs can reveal them whenever players need to find a direction or to face choices.

If situations form the obstacles in an adventure, then leads become the scraps of information that direct players through situations and from one situation to the next.

Most adventures begin with a lead that everybody calls a hook. The best adventures supply characters more hooks as they go.

Leads give players a sense of direction. They lure players through an arc that, looking back, will resemble a plot. Leads can guide characters to the locations that match their power. As clues, they help reveal a situation in an order that keeps players asking questions and craving answers.

Blogger and game designer Justin Alexander has a rule for giving clues:

For any conclusion you want the PCs to make, include at least three clues.

“Why three? Because the PCs will probably miss the first; ignore the second; and misinterpret the third before making some incredible leap of logic that gets them where you wanted them to go all along.”

By Justin’s three-clue rule, every step in the scenario needs three clues that lead to another step. The surplus clues make the scenario robust. In game, players never wind up so clueless that they lack direction. In life, they’re on their own.

The clues can lead in different directions. Such diversity gives options, breaks linear adventures, and sometimes creates tough choices for players. Justin builds on his three-clue rule to create a node-based system of scenario design.

Typically, I plan clues, planting them along the course of the adventure ahead of players. But Mike “Sly Flourish” Shea takes a looser approach. He calls his clues secrets. He prepares for each game by listing 10 secrets that the session could reveal. Some of his secrets reveal the game world, but others serve as leads for players. “Secrets and clues are the anchors of our games. They’re a simple way to build out an adventure, create meaning and story for the players, and connect people, places, and things. Secrets and clues are the connective tissue of an adventure—and, more often than not, a whole campaign”

Mike’s lazy technique skips planning where the clues lead or how players will find clues. “You know the characters will learn something interesting—but you don’t know how they will learn it. You get to figure that out as it happens at the table.” He prepares a list of evocative secrets, and then as he runs a game, he improvises ways to reveal the secrets. Mike’s secrets don’t even become real until the players discover them. After a session, he discards some unrevealed secrets, but revisits others for the next session. For example, in my game based on the murders, if I choose to reveal the secret of the well, then the well becomes important; otherwise, it’s nothing.

“Abstracting secrets and clues works particularly well with mysteries. You’ll have no idea how the characters might go about investigating a mystery. But as they do, you can drop in the right clues at the right time to help them solve it.” For more on secrets, consult The Return of the Lazy Dungeon Master.

The early fifth-edition hardcover adventures designed campaigns around situations that offered all the advantages of the situation mindset. The designs gave players maximum freedom and DMs the flexibility to cope. But these adventures tended to lack ready-made leads that helped players find direction and helped DMs anticipate and prepare for the players’ next destination. (For more, see Are the Authors of the Dungeon & Dragons Hardcover Adventures Blind to the Plight of DMs?)

Alone, situations can overwhelm DMs with information to remember. Campaign-sized situations make preparing for sessions hard on DMs because the scope of what players might do becomes vast. DMs who run published adventures suffer the worst of this problem. Chances for improvisation are more limited. And I can’t be the only DM who finds remembering lore from a fat adventure book harder than the product of my own imagination. Few DMs can master hundreds of pages of content that spans a region like the Underdark well enough to prepare for aimless wandering.

In my games, leads provided the secret ingredient that the campaign-sized situations lacked. They gave players clear options and narrowed their likely choices enough for me to focus my preparation.

Next: Instead of preparing events, prepare villains.

Dungeon Masters, Don’t Prepare Plots and Encounters—Do This Instead

12 Replies

Every dungeon master sometimes throws characters into a combat encounter, and then sees players do something unexpected. We never expect a peaceful dialog. Later, the characters reach a mountain outpost stocked with perfectly crafted encounters and the players show ingenuity by, say, triggering an avalanche that buries the place. Sometimes, every DM wants to say, “Come on, you all took intelligence as a dump stat. Just fight the monsters!”

Sometime in most dungeon masters’ careers, we plot a grand adventure for characters, complete with dramatic beats, treachery, revelations, and a climax. Then the players impulsively murder the traitor in session 1. In session 3, instead of escaping as planned, the evil mastermind dies too. The threat of such reversals tempt any dungeon master to railroad.

All these setbacks come from preparing encounters and plots that expect players to behave as expected. Often players do something surprising that leaves the plans in ruin.

Such planning misfires stem from taking the wrong mindset to prepare for a Dungeons & Dragons game.

For a better approach, follow two principles:

  • Prepare situations instead of encounters.
  • Prepare clues and villains instead of plots.

Situations form the bones of an adventure.

Game-world situations are the arrangements of locations and non-player characters that stand between the characters and what they want. The most elemental form of a situation includes (a) an obstacle, like a bridge blocked by a troll hungry for the party’s delicious gnome, and (b) a goal, like the other side. Often the difference between a small situation and an encounter is a mindset. An encounter starts as a situation with an assumed plot—perhaps as simple as (1) the characters fight and (2) they win. A situation stops assuming a plot and fills in other details like what the monsters want. (Hint: Not to wait in a room until heroes come to murder them.) A small situation might resemble a combat encounter complete with monsters to (probably) fight, but the situation mindset opens DMs for other courses of action. Maybe the characters talk, or sneak, or dislike the gnome.

Unlike combat, exploration, or interaction scenes, situations bring enough flexibility to play in different ways.

Larger situations often resemble dungeons. From a situation mindset, players could solve the Tomb of Horrors by excavating it from the top down—or by skipping it. Rather than grave robbing, real heroes should battle evil overlords. They have treasure too. (Perhaps by looting the tomb, the heroes can defeat the overlord by getting enough gold to cause runaway inflation. I want an adventure where evil is thwarted because it can’t make payroll.)

Tomb of Annihilation includes more modern takes on the dungeon as situation. Within the campaign, The Fain of the Night Serpent features factions, intrigue, and a McGuffin to recover. The Tomb of Nine Gods resembles the Tomb of Horrors, but with the time limit and an objective bigger than runaway inflation.

Situations can go beyond locations. For instance, a masquerade could be a situation where players need to uncover a spy. The characters might find their target through deception, magic, or by picking a suspect’s pockets to gain stolen plans.

The Prince of Murder’s network of covert assassins could form another situation. Instead of predicting which encounters the characters will face as they unravel the network, the DM invents a organization that reacts to the players’ actions.

As with combat encounters, a boring situation can lead it to dull scenes. Good situations include features that lead to interesting play. Mike “Sly Flourish” Shea has advice for creating situations. “Develop situations with lots of options, lots of hooks, and lots of interesting things the characters can interact with.”

So a situation that might feature combat may include a location primed for a dynamic battle. A situation that might include role playing may include memorable NPCs, but should at least include NPCs that want something.

I think of developing situations as piling kindling. Add enough incendiary ingredients so that if a spark flares, the scenes catch fire.

These details rarely require more work. Most dungeon masters will feel comfortable improvising some of the pieces. Plus, the situation mindset often frees DMs from worrying about contingencies. DMs who build situations spend less time preparing responses for every potential action because consequences stem naturally from the situation.

Mike touts the virtues of situations. “D&D is a lot more fun when we can watch scenes unfold in new and interesting ways well beyond what we originally intended. In order for that to happen, however, we need to build environments with all of the right elements to give characters, and their players, the chance to take things in lots of different directions.”

For situations, Tom “Dungeon Bastard” Lommel plans one extra element: He prepares a menu of potential outcomes. He lists wins that represent total success, complications that bring success at a cost, and setbacks that represent failure. “One thing I always get bogged down in is analysis paralysis,” Tom says. “This is a road map for me to respond to what the party is doing. I have a list of plausible options at my command and I don’t have to think about it in the moment.”

I like Tom’s strategy because, in the heat of a game session, I struggle to improvise reactions to sweeping victories and epic fails. Such grand outcomes often threaten to upend the game. An easy win can’t cut a 4-hour convention adventure to a half-hour assassination. Instead, I want to reward ingenuity with some success, and then add reasonable complications that keep one move from ending the game. A total-party kill shouldn’t abort a long-running campaign arc short of a satisfying conclusion. Instead, I want the characters captured, or to lose the magic key, or to suffer the gloating of the rival who saves them. (Forget bludgeoning, adventurers hate blows to their pride most because they wound the player too.) At the least, I always plan ways to turn total-party kills into setbacks that spare the campaign.

Tom uses a storyteller’s sense of drama to help decide among outcomes. His choice results from the usual factors of the player’s choices and the luck of the die, but also from what suits the narrative. Will an up-beat or a down-beat better add drama? Is the table spoiling for a fight or for a lull? Does the session’s pace leave time for complications?

Instead of preparing encounters, prepare situations. The mindset opens you to plan less for what the players might do, while making you ready for anything.

Next: Dungeon masters: Instead of plots, prepare secrets, clues, and leads.

Preparing to run an adventure as a dungeon master at a convention

9 Replies

In 1984 at Gen Con, I first served as an official dungeon master for a table full of strangers. I ran the adventure that would become I11 Needle. As I explained in “Running I11 Needle at Gen Con in 1984,” the session fell short of my standards. Frank Mentzer, please forgive me.

Needle Gen Con 17

Judges’ copy of Needle from Gen Con 17

In the years since, I’ve run many more convention games. I’ve improved. Sometimes I even meet my standards.

This year at Gen Con, I ran 8 D&D Adventurers League sessions. This post explains how I prepare these sessions.

I start by reading the adventure twice.

My first, quick read provides a high-level view. When I finish, I want to know the important characters, the expected course of events, and the clues that lead the player characters through these events.

Most adventures feature an overview intended to serve the purpose of my first read, but these summaries never seem to help me. When I take my first look at an adventure, I’m keenly interested in what leads the PCs through the narrative. But a typical summary just lists events: “After finding the casket of wrath, the characters go to confront Lady Frost.” I need to know what motivates the characters to go from one event to the next. Those leads become the most important clues I must communicate to the players.

The first read enables me to reread knowing which details merit careful attention. I can sift clues from set dressing, key characters from extras.

During the second read, I pay careful attention to the decisions the characters will face. When I run the adventure, I can miss a bit of color, but I must communicate the details that weigh on decisions. I tend to think a lot about the actions players might take during a session. Although I enjoy when players surprise me, I still imagine their likely choices and consider how to handle each one.

A 4-hour convention slot leaves little time for decisions that swing the course of an adventure. I want to present any real options to make them as interesting as possible. See “How running an adventure eight times can be fun and educational.”

Even the best adventure authors sometimes make bad assumptions about what the players will do. See “Actions players always take and choices players never make.” For example, Hoard of the Dragon Queen assumes players will join a caravan with some cultists transporting looted treasure and then travel for weeks—instead of just attacking the cultists and taking their gold. Like every D&D player ever. I wondered have the authors even played this game? (Answer: Yes. More than me, but perhaps not with so many strangers at recent conventions.)

Whenever I spot such an oversight, I plan on how to account for it. Will I reinforce the need to infiltrate the caravan? Will I present the cultists as too tough to confront? Will I let the players slay the cultists and then contrive a way to get the PCs to the next chapter. Sometimes I let players discover the risks of each option so players reach a dilemma. See “How to improve your game by forcing characters into tough choices.” Sometimes, I just make players understand the facts that make a bad strategy bad.

On my second read, I may mark up the pages. I cannot bear to mark up a hardcover adventure, but Adventurers League pages call for the red and blue pens.

Red and blue notes on page

Red and blue notes on page

In blue, I break the wall of text with sub-headings that flag key information. In play, I rarely scan my headings, but when I do, they can cut minutes of text skimming. Plus, the process of writing headings turns me into an active reader. I notice things that I might otherwise overlook. I remember more at the table, so I look down less.

In red, I write names and other bits of text I must find at a glance. Names always go in red, as do quotes that I might read as I glance down.

Annotated dungeon map for CORE 2-1

Annotated dungeon map for CORE 2-1

On any dungeon maps, I note everything I need to know. My captions include monsters, locks, objects of interest, difficulty classes and so on. Ideally, I can run all the rooms from the map.

When I first started running organized-play adventures, I would work from a packet of pages. This led to disaster. As I referenced maps, monsters, and descriptions of encounter areas, I plucked them from the pile. Half way through the session, I faced a shuffled heap. While I spent minutes hunting for that one sheet, I stammered apologies.

color reference sheets and player handouts

Color reference sheets and player handouts

Now, all my adventures go into a loose-leaf binder with tabs separating each module. Double-sided printing makes the best use of space.

I print second copies of the maps and monsters on single-sided sheets of colored paper. I can pull my green, monster stats at a glance and I never lose them in a stack.

Player handouts, including magic-item descriptions and story awards, also go on colored paper and in the binder. If I plan to run an run an adventure more than once, I use card stock.

Printed urban battle map fits the encounter

A pre-printed, urban battle map fits this encounter

For any of the adventure’s encounter areas, I look for pre-printed maps in my collection that suit the location. Many encounters rely on few specific details, so any map that captures a location’s flavor will serve.

When none of my existing maps fit, I might print or sketch a map in advance. If an adventure always lands PCs in a location, I’ll wind up drawing the map anyway. Drawing in advance saves time at the table. Plus, if I’m running an adventure more than once, more players can enjoy any effort I invest in maps.

Szith Morcane Unbound - Dengor’s palace

Szith Morcane Unbound – Dengor’s palace on Dungeon Paper

Maps go into sheet-protector pockets and then into the binder near the encounter description. (For more on printing maps, see “How to print map graphics as battle maps using free software.”)

Map in sheet protector paired with encounter

A map in a sheet protector paired with an encounter

After years chasing miniatures, I can match most monsters with suitable figures. If I lack figures, I may use the excuse to add to my collection, or even fabricate a figure.

Miniatures for an adventure

Miniatures for the CORE 2-2 adventure

No one leaves a D&D table annoyed because they needed to use imagination. So if you lack miniatures, you can bring tokens or even candy to represent monsters.

Finally, creating monster initiative tents in advance pays off at the table. When combat starts, ready-made monster tents avoid delay. Plus, pre-rolling gives me time to note key monster stats on the tents. This keeps things like Armor Class front-and-center rather than somewhere in a pile of green sheets. For my initiative tents and more, see “Everything I know about tracking initiative.”

How do you prepare for a published adventure?