Roleplaying games can vary a lot in how lethal they are for player characters. And, perhaps even more importantly, they can vary a lot in how permanent death is when it occurs.

This can even be true within a single system. In some classic versions of D&D, for example, PCs can begin in an ultra-fragile state (in which any hit in combat could automatically kill them) and then level up to a point where death is just a minor inconvenience.

But let’s assume that we’re playing a game where death really is the final frontier: If your character dies, then they’re dead. No take-backs. If you’re playing in a campaign with a game like that, how can you handle death?

One way is to duck the question entirely with script immunity. In campaigns with script immunity, PCs simply can’t die. This may be a feature of the rules (as in Magical Kitties Save the Day), but is often a metagame conceit openly or silently respected by the table. There are a number of techniques that are useful for making script immunity work, but the two most common approaches are to either disallow the mechanical outcome of death (NPCs will always miss the final blow) or to interpret the mechanical outcome of death to mean something other than death (e.g., the PC is instead knocked unconscious). These are often combined with a caveat which allows the PC to die if their player wants it to happen. (This is because script immunity is usually a technique favored by dramatists, and being able to have death occur only when it is dramatically appropriate and satisfying is desirable. But I digress.)

What I actually want to focus on is not how to avoid PC death, but rather what comes next.

The first option is to actually remove the player from the campaign. The PC was their agent in the game world. Now that their agent has been destroyed, they have no ability to participate in the game.

This is, in some ways, the opposite extreme from script immunity — where immunity completely removes lethal consequences from the game, the all-or-nothing approach makes those consequences about as meaningful as they can be. On the other hand, script immunity and one-PC-only both recognize how momentous and important death can be to a narrative and simply emphasize it in radically different ways.

Personally, I’ve never seen one-PC-only used in a multi-session campaign. (And I could only really imagine doing so if it was very deliberately the focus of experimental play.) But it’s far from unheard of to see it used in one-shots, and it can be built into games like Ten Candles and Dread.

The far more common approach, of course, is to replace the player’s PC with a new PC. Your character is dead, so create a new one that can join the group.

BACKUP PCs

There are two impediments to consider when using replacement PCs.

First, the time required to create the new character. This can range from trivial in some systems to laborsome to baffling (in games which feature interconnected character creation mechanics but neglect to account for how new PCs could be added to the group).

Second, how to organically integrate the new PC into the existing group. Even when the group leans into the metagame conceit of the replacement (“we trust this newcomer implicitly because we know Mark is playing her”), there can still be the question — when the group is in the middle of a vast dungeon or lost in the untracked wastes of an uncharted jungle — of how and when this new character can actually show up.

Sometimes these two problems can nicely cancel each other out (the time taken to create the new character neatly covers some or all of the time it takes the rest of the group to reach a point where a new character can be naturally introduced), but there can still be logistical and logical hurdles to clear.

The core tip here is that you can solve the first problem by preparing a backup PC. In other words, before your character dies you can already have the replacement character prepared and ready to go. This obviously simplifies things, as you can simply pull out the new sheet and get back to playing lickety-split.

Tangential Tip – Inheritance: If you’re playing in a game where gear is important (e.g., D&D), make sure backup PCs don’t come fully equipped for their current level. You need to work from the assumption that they will either directly or indirectly inherit the wealth/gear of the PC they’re creating. Otherwise every dead PC becomes an incredibly rich looting opportunity and death, rather than being a failure to be avoided, paradoxically becomes a payday which dramatically rewards the group.

You can extend this technique to begin addressing the second problem by giving the backup PC a clear connection to the group. This will often be through the PC who died. For example, “I heard my brother was killed! I have come to avenge them!” (Early versions of D&D actually included rules and guidelines for handling PC-to-PC inheritance and probate.)

BEFORE YOU DIE

Now that you have a slate of backup PCs waiting to step up if a current PC should die AND those backup PCs have existing relationships with the PCs (sisters, apprentices, old college roommates), you can incorporate the backup PCs into the game while the current PCs are still alive.

In many ways, this just makes sense. If you’ve prepped an apprentice who can replace your character Obi-Wan if they die, it makes sense that the apprentice would be part of the story before Obi-Wan’s death.

Of course, once a backup character comes onstage like this, it’s certainly possible that the evolving narrative will make them unavailable or inappropriate for being a PC. That’s fine. (Obi-Wan survived long enough and things went crazy enough with their apprentice that they ended up giving the apprentice a son and just copy-pasting their stat block onto it.)

Tangential Tip – Promoting NPCs: You can flip cause-and-effect here by letting a player of a dead PC take on the role of an established NPC. Even though the NPC wasn’t intended to become a PC, they have an existing relationship with the other PCs and are already integrated into the narrative.

Onstage backup PCs can be played by the GM, but it’s often more effective if the player takes on the role “prematurely” when necessary. To that end, it can be most effective for your backup character to have a connection to a different player’s PC. If you’re playing your own apprentice, there’ll be lots of moments when you’d have to roleplay with yourself (which can lead to skipping or abbreviating those scenes). But if you’re playing Alejandra’s apprentice, then you’ll both be able to frame up interesting scenes and small interactions that will enrich the game.

A variation of this is to create a common pool of backup characters, rather than having each player create their own. You might have one or two or three such characters, and whichever player’s PC dies first (if any) simply grabs whatever character is most convenient from the pool.

These backup characters might also just be temporary roles, which can be played until it’s convenient to create and bring in a fully fledged new PC. (In old school D&D, taking on the role of another player’s hireling is an informal version of this.)

These backup PCs can even account for Total Party Kills (TPKs). “So-and-so has mysteriously vanished/been killed and I’m looking through their notes” is a well-established trope in Lovecraftian fiction, for example, and can easily be transferred to other genres. Laying the groundwork for this sort of insurance policy can be used to frame epistolary play and bluebooking, encouraging note-keeping and enabling different forms of roleplaying that greatly augment a campaign.

You also don’t have to wait for a PC to die in order to swap to your alternate PC. Any number of circumstances might suggest it: Your primary PC might want to retire, be called away on a family emergency unrelated to the main thrust of the campaign, disappear into the Fairylands, or go into a witness protection plan. Or maybe you just want to switch things up.

In fact, you can swap back and forth between your PCs. Or across multiple characters. If your group has established a common pool of PC options, you might even find yourself playing the same character that was previously played by a different player.

TROUPE PLAY

… and we’ve just reinvented troupe play.

First created by Jonathan Tweet and Mark Rein*Hagen in the Ars Magica roleplaying game, troupe play can be broadly defined as a campaign in which the cast of player characters is larger than the number of players and the expectation is that the players will take on different roles for each session or scenario.

This style of play is, of course, quite impervious to the question of, “What does Naito do when his PC dies?” because it has already eschewed the one-to-one relationship between player and PC. More importantly, however, troupe play techniques unlock a lot of unique opportunities at the game table.

Most notably, the constant shuffling of the current group creates a huge variety in personal dynamics and relationships. (You can get a similar dynamic with an open table. The distinction here is that you can get the same effect with a small, dedicated group of players who are sharing all of the experiences in common.)

Ars Magica notably uses the technique to create the dynamic found, for example, in The Hobbit: Gandalf is clearly a much more powerful character than everyone else in the adventuring party. Ars Magica solves the problem of, “Who gets to play Gandalf?” by letting everyone create their own Gandalf and then rotating who’s playing Gandalf and who’s playing the motley assembly of mortals each week.

Similarly, a Star Trek-style space opera can run into the question of, “Who gets to be the captain?” In troupe play, the captain could be a communal character shared by all the players (each of whom also has another bridge crew member as a PC). Each session, a different player gets to play the shared role of the captain.

Ars Magica also associated the concept of a rotating GM into troupe play. I think of this as actually being a distinct technique, but it does combine very well with troupe play. (Since the campaign dynamic already has characters constantly swapping and realigning, it’s easy enough for each GM to have their characters skip the adventures that they’re running.)

One of the GM’s most fundamental skills is description. The GM’s words are, after all, the players’ window into the game world. While some performance-enhancing work-arounds do exist (pictures, miniatures, maps, etc.), the bulk of the heavy-lifting boils down to what the GM says and how they say it.

I’ve given general tips for crafting effective descriptions in the past, but if you’re looking to boil things down to some basic procedures, here are some simple formulas. (Our goal here will be to create descriptions that are efficient, effective, evocative, and also easy.)

DUNGEON ROOMS

For a dungeon room:

1. List every notable thing in the room and its position. (“Notable” here can be broadly understood as “thing the PCs will interact with / check out / will inform their actions.” Check out The Art of the Key if you want to delve deeper here.)
2. Use the Three of Five rule by dropping descriptive tags on some or all of the notable things. (In short: “Think about your five senses. Try to include three of them in each description.”)
3. If appropriate, add a verb. (Add action to the scene; e.g., instead of “there is a waterfall,” there is “a waterfall tumbles down the far wall.”)

For example, a room has:

• wardrobe
• bookshelf with arcane tomes
• a goblin

Use the formula to generate:

A horrid stench [smell] emanates from a wardrobe off to your left. On the opposite side of the room, there’s a bookshelf stuffed full [sight] of thick tomes and tightly wrapped scrolls. There’s a goblin pawing through the books on the shelf, knocking them to the ground [verb]. Seeing you, the goblin gapes its maw and screeches [sound].

NONPLAYER CHARACTERS

Whether improvising an NPC on the fly or prepping a Universal NPC Roleplaying template, you can use this formula:

1. An action.
2. What are they wearing?
3. One physical trait.

For example:

Lady Silva is wearing a beautiful blue dress [clothing] that compliments her sapphire eyes [physical trait]. She taps her finger thoughtfully on her chin while looking you up and down [action].

When using the Universal NPC Roleplaying Template, the NPC’s action may be drawn from the Roleplaying section of the template (i.e., the action may be the NPC’s common mannerism). But it doesn’t have to be. The key thing is that you’re establishing the NPC as someone living in the game world; you’re not describing their headshot, you’re establishing them in the scene.

MONSTERS

When encountering a monster:

1. Look at their abilities and attacks; describe how one or more of those are physically manifest.
2. Describe one non-ability-based physical trait. (Use ability scores as inspiration if you’re coming up dry.)
3. Add a verb.

Let’s pick some monsters at random and see how this plays out.

Hill Giant. They have a greatclub and a rock attack. Include the club in the description. You might mention that they’re standing near a pile of rubble (from which you can later describe them snatching up rocks to throw at interlopers). They’re a giant, so… they’re quite tall. (You don’t have to make this complicated.) What are they doing? Gnawing a bone, scratching their head, chatting amongst themselves, swatting giant flies swarming around their head? (Again, you don’t have to be particularly clever. Establish the idea and move into the scene.)

Revenant. One of their abilities is Vengeful Glare, so describe them as having eyes that burn with an eerie blue light. It’s undead and has 18 Charisma, so we can add that it’s an incredibly handsome figure with chalky gray-white skin. Simply add an action appropriate to the current scene.

(As with our other formulas, don’t get hung up on the order here. The description of the revenant, for example, can be: “A dark figure perched atop a rocky promontory, gazing out across the valley. The man’s features are handsome, but its eyes burn with an eerie blue light and its skin is a chalky gray-white.”)

Xenomorph. Their acid blood won’t be immediately obvious, but perhaps we could riff on the idea of bodily fluids by having their jaws slavering with some alien fluid. Their serrated tail whips back and forth, while the flickering fluorescent lights gleam off their black, chitinous exoskeleton.

A WORD ABOUT FORMULAS

Formulas are… well, formulaic. They’ll only take you so far, they can easily become repetitive, and it’s trivial to find examples where the generic formula will be a poor fit for the material. The role of these formulas is not to be the be-all or end-all of RPG descriptions. But if you’re stuck, you can use them as simple recipes to get your brain churning. In fact, you’ll often find that starting with a formula will quickly inspire you to spin out of the mold and create something completely different.

If it does?

Mission accomplished.

PERSISTENT DESCRIPTION

As you’re looking to expand beyond the simple formula, one thing to keep in mind is that description should persist throughout a scene.

I’ve mentioned in the past that the legacy of boxed text can condition GMs to think of description as something you only do at the beginning of a scene or when the PCs enter a room. But that’s an artificial limitation of published modules that you should try to move beyond as you’re running the game.

Add sensory details. You mentioned that there was broken glass on the floor [sight], but as the PCs move into the room you can add the description of the grass crunching under their boots [sound and touch]. The waterfall was described as roaring [hearing], but you can build on that by mentioning the cool mist it throws up [touch] or the fractured reflections of light dancing across the walls of the cave [sight].

Investigate to find new details. When the rogue heads over to check out the wardrobe, take the opportunity to describe the intricate carvings on its doors. After seeing Lady Silva for the first time they grab their drinks and head over to talk to her, and you can take the opportunity to add the color of hair as she turns to look at them.

In the case of a keyed dungeon room, this can actually be structured and prepped. Remember how we listed each notable thing in the room? When the PCs go to investigate or interact with a notable thing, that action simply triggers additional details.

Discover new things. In addition to finding new details about things you already know, the PCs may also discover entirely new things in the environment as they explore it. (What’s inside the wardrobe and causing that terrible smell?) Matryoshka techniques can be a powerful way of running this.

Introduce new elements. A cold wind blows through the cracked window. An otyugh shambles through the door. A police siren wails past the apartment building. A flickering hologram manifests in the center of the chamber. You don’t have to wait for the PCs to investigate to add something new to the scene. The world is a dynamic and active place.

Combine. All of these methods can be used in conjunction. Someone throws a rock with a note wrapped around it through the window. As Bryan goes to pick up the rock, describe the crunch of broken glass under his feet. The rock itself is black obsidian. As he pulls off the note, describe the texture of the vellum.

An image I find particularly evocative is to think of the description of the game world as being layered. You don’t have to exhaustively describe every single detail of an environment in one big glob of exposition. Make sure that the players have the key information they need to orient themselves and understand what’s happening; but then either peel back or add on (whichever visual analogy works better for you) additional layers of description as the scene plays out, slowly building up the mental image of the place like a painter laying down paint on their canvas.

EVOLVING MONSTER DESCRIPTIONS

Speaking of layers, here’s an extra tip when it comes to describing monsters.

The first time the players encounter a monster, you need to establish the monster’s basic visual image. (And you can use the formula described above to do that.) Once the players are familiar with a monster and are able to put a name to it – goblin, gelatinous cube, blood terror, little fuzzies, etc. — you don’t need to re-establish the monster’s basic description each time.

However, this can lead you into the trap of replacing evocative description with bland labels: “You see six goblins.”

What you usually want to do instead, once the players know what a monster is (when you can say “it’s a worg” instead of describing the worg), is to dig one layer deeper by customizing the monster.

These aren’t just six goblins; they’re six goblins dressed in opera dresses. This isn’t just a worg; it’s a worg with a bright red scar over its left eye. This yeti’s fur is matted and filthy. This ogre’s hair is tied up in a topknot. This ghoul’s left arm is broken; it’s hand flopping back and forth on a loose flap of sinew. This wraith wears an iron crown of Angorak.

When the PCs run into a mob, you don’t need to customize every single one of them. (And it’s usually counterproductive to do so.) As a rule of thumb, you’ll want to either customize one of them (it’s a group of yetis, and one of them is wearing a sapphire amulet) or focus on what’s notable about all of them (all of these yetis are missing a finger on their left hand).

(If you’re making one member of a group stand out, it will often be the leader. But this isn’t necessarily true. For example, one worg out of the pack might be limping and ostracized by the others.)

For humanoids, you might use the full formula for an NPC described above. But for monsters you often just need one salient detail to distinguish them.

“Never split the party.”

It’s a maxim of the roleplaying hobby.

There are two primary reasons why it’s a good idea not to split the party. First, it divides the party’s strength, making each smaller group weaker and more vulnerable. (This is a particularly bad idea if you’re playing in a paradigm in which (a) adventures are primarily a string of combat encounters and (b) those combat encounters are all carefully balanced to threaten your full group with destruction. Nothing good can come from splitting up in those situations.)

Second, the concern that splitting the party places an undue burden on the GM, who now needs to keep track of two separate tracks of continuity while making sure to juggle spotlight time between the groups.

There’s some truth to both of these, which is why “never split the party” is great advice for newbies.

But in actual practice, there are A LOT of caveats.

As a GM, for example, I absolutely love it when the party splits up. With just a modicum of experience, you’ll discover that running simultaneous scenes – which is the end result of splitting the party – is basically Easy Mode for effective pacing (which can be one of the trickier skills to master as a GM): You’re no longer limited to cutting at the end of scenes, and can now use interior cuts to emphasize dramatic moments and create cliffhangers. It also becomes far easier to smoothly cut past empty time and refocus on the next interesting choice. (I discuss this in more detail in The Art of Pacing.)

As for the players: If you’re in hostile territory… yeah, splitting your strength is generally a bad idea. But once your adventures leave the dungeon, there are going to be lots of times when you’re not operating in hostile territory and can gain huge benefits from multiplying your active fronts.

You can actually think of this in terms of action economy: If you all stick together, you’ll be stuck doing one thing at a time. If you split up, on the other hand, you can often be doing two or three or five things at the same time, stealing a march on your opposition or just moving quicker towards your goals. (This can also make it easier for different characters to pursue actions that play to their unique strengths, making it less likely for some players get stuck in “passive mode” watching other players do everything important. When two actions of the same type need to happen at the same time, it’s also a great opportunity for someone who’s second-best at something to get a chance to showcase their skills, whereas normally you’d usually default to having the character with the best modifier make the check.)

Two easy examples where splitting the party can be favorable are personal scenes (hard to woo your lady love with four wingmen/women hovering over your shoulder) and time-crunched objectives. I find this style of play is more common than not in urban adventures, where meeting with multiple people at the same time can be very advantageous; or one group can be handling the barter while another group is gathering rumors down at the Docks. Being able to pursue multiple leads simultaneously in a mystery scenario is another common example (you’ve got to catch the serial killer before they strike again!), but can be strategically a little more complicated as you run the risk of inadvertently stumbling into hostile territory on the wrong foot.

Now that we know why splitting the party can be awesome, here are some quick tips I’ve learned over the years when GMing split groups.

Tip: Split spotlight time by player, not group.

Regardless of splitting the party, you generally want every player to be contributing equally and to have an equal amount of time in the “spotlight” (getting to show off the cool stuff they can do, being responsible for the group’s success, etc.).

An easy mistake to make, though, is what I call the “lone wolf spotlight,” in which one PC wanders off by themselves and ends up getting fully half of the GM’s attention. This can sometimes be a symptom of disruptive play (with the lone wolf’s activities interfering with the other players’ fun), with the increased spotlight time inadvertently rewarding the bad behavior, but this is not always the case.

Solving the problem is just a matter of keeping in mind the general principle of everyone getting an even share of the spotlight: If one group has four PCs in it and the other group has one PC in it, you should usually spend four times as long focusing on the larger group.

(There can be lots of exceptions to this. Juggling spotlight time is more art than rigid turn-keeping. Maybe the smaller group is doing something much more important and gets a lot of focus in the first half of the session, and then you can make sure the other PCs get extra spotlight time in the second half of the session or at next week’s session. But the rule of thumb here is still to split spotlight time by player, not group.)

Tip: Put the PCs under a time crunch.

The party doesn’t have to be constantly facing do-or-die deadlines, but there are A LOT of benefits to making time relevant to a scenario. It makes every choice between A or B significant, because you may not have time to do A and then do B.

Bonus Tip: You don’t need to set a plethora of explicit deadlines to make time relevant. Just having a campaign world which is active – in which the players can see that significant things happen over time; that situations evolve – will create not just the perception, but also the reality that time matters.

One of the things that will happen as a natural result of this is that the players will be encouraged to split the party: Faced with a difficult choice between doing A or B, they’ll cut the Gordian knot by breaking into two groups and doing both.

So have multiple stuff happening at the same time: Two different patrons want to hire them for jobs on the same day. An unexpected crisis breaks out just as they’re getting ready to go do a thing. When they’re in the middle of doing something, use a cellphone or sending spell to have a desperate friend call them for help.

Tip: Cut in the middle of scenes.

I touched on this earlier, but it can be easy when running a split party to fall into the habit of playing out a full scene with Group A and then playing out a full scene with Group B. (Or, more generally, resolving everything Group A wants to do before switching to Group B.)

This approach can work (and there may be times when it’s exactly what you want to do), particularly if you’re blessed with a group who thoroughly enjoys audience stance and can happily sit back and watch the other players do their thing, but more often than not this will result in Group B becoming bored for half the session and then Group B becoming bored for half the session.

So read the room and cut before people start tuning out. In my experience, it’s almost always better to cut too often than it is to wait too long, so err in that direction.

Tip: Swap groups when you’re not needed.

Are the players in Group A discussing their options? Or rolling dice to make their skill checks?

Cut to Group B!

There are a bunch of more advanced techniques you can employ for effective, dramatic cuts, but watching for those moments when the players don’t need the GM to continue playing are absolute gimmes.

(It’s also another example of why splitting the party can be awesome: If Group A is roleplaying amongst themselves while Group B is resolving stuff with the GM, then everyone is magically getting bonus playing time in your session.)

Tip: Scale time to balance table time.

Another common pitfall is to think that you need to keep time between the two groups strictly synced. So if one group is staying put while the other is driving fifteen minutes across town, you would need to resolve fifteen minutes of activity with the first group before you could even think about cutting to the other group.

This can very easily make it impossible to effectively split spotlight time or cut between the groups.

The solution, of course, is to simply not keep time synced: Start running the scene with the first group, then cut “forward” to the other group arriving at their destination. Run a bit of that interaction, then cut “backwards” to the first group.

This can sound complicated, but in practice it really isn’t. You can stress yourself out thinking about all the ways that the PCs could hypothetically violate causality, but you either (a) say that isn’t an option or (b) perform a simple retcon or flashback to resolve the conflict (whichever is most appropriate for the situation). Your players will help you do this in a way that makes sense for everyone. (Plus, in practice, timekeeping in the game world isn’t that precise to begin with, so you’ve usually got a pretty wide margin of fuzziness to fudge things around.)

Note: What if the PCs have cellphones or some other form of continual communication unlimited by distance that can trivially breach the continuity between the two groups? Often, the net effect here is that the party ISN’T actually split: Even though they’re in two different locations, each group is able to participate in what the other group is doing (by offering advice, expertise, etc.). This makes it substantially less important to balance spotlight time between the groups, since players can grab a slice of spotlight for themselves over the comms line.

Tip: If the PCs split up and get into two fights simultaneously, make a single initiative list.

And then you just swap between the fights whenever the initiative order tells you to.

(This generally works regardless of what type of initiative system you’re using. If you’re using hot potato initiative, for example, you and the players can choose to throw initiative between the two fights. If you’re using the 2d20 System, in which PCs always go first each round but the GM can spend meta-currency to seize initiative for one of the NPCs, you can simply do that for whichever fight you want at any time. And so forth.)

Running two combats at the same time is often seen as one of the hardest possible thing for a GM to do with a split party; a kind of worst case scenario. But the structure of the initiative list can actually act like training wheels. If you’re trying to get a feel for what running simultaneous scenes should feel like – cutting between scenes, balancing spotlight time, etc. – I actually think running simultaneous combat is a great way to do it.

The Art of the Key breaks down how you can organize and format the room keys in your dungeon to make them easy to prep and run. But what do you actually put in the key? What do you fill your dungeon rooms with?

Every dungeon is a unique snowflake, but my general process is:

1. Make a list of ideas. “Section of dungeon that looks like a Mongolian temple,” “dracolisk hatchery,” etc. Often this is just a list of cool/necessary rooms that I want to include, riffing on the general theme or purpose of the dungeon. (You can use techniques like the Goblin Ampersand to juice a basic concept and help spur your creativity.)
2. Draw the dungeon map, making sure to include all the cool ideas. (This will often involve combining multiple ideas into a single area to make them cooler in combo.)
3. Flesh out the key.

“Fleshing out the key” covers a variety of sins, but our key tip today for making awesome dungeon rooms is to avoid having rooms that are just one thing*.

It’s not just the room with the goblins; it’s the room with the goblins and the bubbling stewpot and the chandelier made from kobold bones.

It’s not just a room with some bookshelves; it’s a room with bookshelves, a slate table with a hidden compartment, and a looted rug from the Cambarran Dynasty.

A good rule of thumb here is to include at least three interactive elements (i.e., things that require or reward the players for doing more than just looking at them).

There are a couple reasons why this is good praxis.

First, the interplay between the elements tends to result in gameplay that’s greater than the sum of its parts: A fight with goblins is interesting. A chandelier made from kobold bones is a nice bit of set dressing. Goblins swinging on a bone chandelier during a fight? That’s awesome.

Second, a room with multiple interactive bits (i.e., things that are worth checking out) will encourage the group to split up and all check out different stuff.

Lisa: I’m going to scan the bookshelves for interesting titles.

Roberta: Can I make a History check to learn more about the antique rug?

DM: Go ahead and give me that check. Sandra, what are you doing while they do that?

Sandra: I’ll examine the table in the middle of the room.

If each room just has one thing for the PCs to interact with, you’ll often find the group falling into a routine where one character defaults into being “the guy who checks out the one thing in the room worth checking out.” (Usually the rogue.) If you break that up with multiple, simultaneous interactions, over the course of the dungeon you’ll make it more likely that everyone in the group will feel engaged with the exploration.

* The exception are empty rooms. In my dungeons, empty rooms are rarely truly empty (in the sense of being barren and featureless). Instead, “empty” rooms commonly feature one flavorful thing which does not have a significant interaction. (“Cool mural! Okay, let’s go left.”)

The encounter creation guidelines in the Dungeon Master’s Guide and Xanathar’s Guide to Everything are both based on the idea that you know how many PCs are in your group. Then you do a table lookup, do a little math, and – presto! – you have a budget to spend on your encounter, expressed as either an XP amount or a number of creatures of a particular challenge rating.

But what if you’re using a published adventure with a party that’s a different size than the one recommended? For example, what if you’re running Curse of Strahd (“for four to six players characters”) but your group only has three PCs?

Going strictly by the book, you would need to deconstruct the encounters in the book to calculate the original XP budget, determine what difficulty the encounter was designed for (Easy/Medium/Hard/Deadly), calculate the correct XP budget for your PCs, and then rebuild the encounter using the new XP budget. (Which may or may not be possible with the original creature(s) used in the encounter.)

Here’s the tip: It’s a lot easier to adjust the level at which your PCs play the adventure than it is to redesign every single encounter.

• For Tier 1 & Tier 2 characters, increase their level by +1 for each “missing” PC from the party.
• For Tier 3 & Tier 4 characters, increase their level by +2 for each missing PC.

Or vice versa for additional PCs.

To put that another way, if a published adventure’s recommended level is X, then at Tier 1 & 2 use it for PCs who are level X + 1 per fewer PC and Tier 3 & 4 use it for PCs who are level X + 2 per fewer PC.

So if you’re running Dragon Heist, which is recommended for five PCs, with a three-person group, you’d either want to start them out as 3^rd level characters (instead of 1^st level characters) or run a prequel adventure or two to level them up to 3^rd level before using the published Dragon Heist campaign.

BONUS TIP #1

Challenge ratings are not that precise. They’re not designed to be a guarantee (nor can they be). They are a very rough approximation of “on average.”

Some “balanced” encounters will be easy. Some will turn out to be surprisingly difficult.

That’s okay. No game, no adventure, no session is about a single encounter.

The flip-side of this is that you don’t need to worry too much about getting an encounter exactly right. It’ll mostly get washed out in the general noise – the imprecision of the system, encounters being designed over a spread of challenge levels, situational conditions of the battlefield, and so forth.

This is also why Wizards of the Coast can release adventures “for four to six player characters” of a given level. Such adventures are designed for five PCs. They’ll be a little bit harder for four PCs and a little easier for six PCs, but it’ll be just fine.

BONUS TIP #2

In terms of strict math, the rule of thumb described here breaks down for very large groups of 9+ PCs. But there are more significant balancing issues based on action economy that make creating and running encounters for such large groups more of a special snowflake in any case. (Short version: Ten PCs, with all their attacks and all their special abilities, are able to wreak an amount of havoc that is out of linear proportion to a group of four. But, conversely, you can’t just use more powerful creatures, particularly at lower levels, because the monsters can one-shot individual PCs before they go down.)

For groups of 8 PCs, rather than running higher-level adventures, you can get pretty good mileage out of taking an adventure designed for five PCs and just doubling the number of creatures in the encounter.

For groups of 9+, adjust the encounter based on the difference between the PCs’ group size and a group size of eight, and then double the number of creatures. (This breaks down somewhere in the teens, but I would… uh… strongly recommend not running groups that large.)

This can create some weird narrative challenges if the encounter was, for example, with a solo boss or the like. But those are the types of encounters which really don’t work with large groups in any case, so you’ll just need to give them a little more TLC.

BONUS TIP #3

Whatever approach you’re taking to encounters — prebuilt, custom built, or otherwise — remember that you can always dial it in over time: If the encounters you’re building are too hard, trim the XP budgets in the future (no matter what the by-the-book math says). If you’re running a published adventure and the PCs are steamrolling the opposition, hold back on leveling them up. Or, vice versa, level them up faster if they’re struggling.

As you’re getting a feel for things, keep in mind that you have to miss by A LOT and for a very long time for “too easy” to not be fun.

You only have to miss once for “too hard” to be a campaign-ending TPK.

So erring on the side of easy is recommended. You can dial it up from there.