Tag Archives: railroading

How the Flawed Hooks in Descent Into Avernus Might Make D&D Players Feel Railroaded

Everyone giving Dungeons & Dragons advice tells dungeon masters how to start an adventure with a hook. This includes me, last week. That advice usually stops after the first hook, and it shouldn’t. Sure, adventures that lure characters into the unknown seeking treasure only need one hook. But just about every adventure with a more complicated premise serves hooks from start to finish. Those hooks offer choices and lure characters along a course that shapes into a story.

The hooks that come after an adventure’s start often go by names like clues, secrets, or leads. In earlier posts, I favored the term “leads” because the word matches one essential purpose: Leads reveal ways for the characters to reach a goal. (If the idea of leads seems unclear, see instead of plots, prepare secrets, clues, and leads.) The word “hook” emphasizes a second essential: Hooks entice players to chase a particular goal.

By either name, hooks and leads must accomplish two things: They entice characters to pursue a goal and they reveal ways to reach that goal. Skipping one of those parts causes adventures to stumble.

Leads point a direction, but sometimes they still need to sell a new goal.

When an adventure needs to point characters toward a new goal, the leads need to sell that new goal. Many adventures fail to close the sale. Most often, an adventure starts with a promise of gold, and then presumes that a band that may only include murderous treasure hunters will happily switch to, say, battling princes of elemental evil—for free.

My last post describes how Baldur’s Gate: Descent Into Avernus attempts this sort of flip. The opening hook appeals both to the treasure hunters and the do-gooders. Later though, the adventure asks players to send their characters to Hell for the slimmest chance of rescuing a damned city. The paladins might volunteer, but any sensible rogue would say, “I’m out.” Still, the rogue players want to play D&D, so their characters dutifully tag along.

In an adventure like this, either the dungeon master or the players can rethink the party’s motivations, smoothing the rough patch. Often, no one does. Many longtime players face such situations often enough to feel numb to the dissonance of having to do something their characters wouldn’t do just to keep playing. The rest feel railroaded.

Hooks sell a goal, but they need to offer a sensible direction too.

When an adventure runs short of hooks or leads, everyone notices. The party gets stuck and the DM finds a way to drop new clues. The adventure may stall, but the obvious trouble invites a solution.

Imagine trying to start an adventure by only revealing that long ago a mighty warrior hid a magic sword in a long-forgotten location. That tidbit would only leave players waiting for more, because without any clues, the incomplete hook rates as backstory. Every adventure starts with a hook that (1) entices the characters to follow some goal and (2) reveals ways to reach that goal. Number 2 rarely gets discussed because DMs seldom botch it. At the start of a scenario, no DM dangles a hook that lacks any clues the characters can follow to the goal.

The more insidious problem appears when an adventure offers clues that don’t seem to lead closer to the goal. The players see a lead, but no reason to follow it. Few players want to derail an adventure that plainly offers a direction, so the players dutifully follow the lead while ignoring that dissonance that comes from doing things just because the DM pointed the way. Following an apparently useless lead makes players feel confused at best, railroaded at worst. To the DM, the adventure seems to run smoothly, so the problem goes unnoticed by the person who could have corrected it.

Descent Into Avernus suffers from this trouble. (This discussion includes spoilers, but hardly more than the adventure’s title.) D&D blogger Merric Blackman writes, “The trip to Hell offers no reason for the characters to believe they can improve things. You stopped a threat to Baldur’s Gate. Why now to Avernus?

“‘If the characters think they have any chance to rescue Elturel, Liara strongly urges them to pursue that quest.’ That’s why the PCs descend into Avernus. Not great, huh? Why do the PCs think they have a chance?”

Game designer Justin Alexander is more blunt. He explains how Descent Into Avernus keeps asking players to follow directions just because they lead to more D&D. “The entire campaign is just this one structure repeated infinitely: A non-player character tells you where to go, you go there, and then find another NPC who tells you where to go.” This pattern works when the NPC’s directions show a way closer to the goal. The leads in Avernus fail that standard. “The problem is that the designers aren’t designing a situation. They aren’t thinking of the game world as a real place.

“Why does the adventure assume the characters will simply plane shift to Hell without having any reason for doing so? Because an NPC told them to! Why not also have the NPC give them a coherent reason? Because it doesn’t matter!”

The design only aims to route players from scene to scene. In play, the party sees a lead that they know the adventure expects them to follow, so they do. To the DM, the adventure appears to work, but unless players feel numb to dutifully playing DM Simon says, they feel railroaded.

Alternately, when hooks clearly point characters toward their goals, even linear adventures, even railroads, can work magic.

“A good railroad, at a certain level, is like a good magic trick: The players won’t really believe that magic is real, but a good magic trick will let them suspend disbelief just long enough to be amazed. The most important technique for the railroaded scenario is to frame the meaningful choices in such a way that the players legitimately want to make the predetermined choice.” writes Justin Alexander.

“The GM never forces a card on them. In the end, they do the magic trick to themselves. When a railroaded scenario pulls this off, the suspension of disbelief is perfect: Players never feel as if they were forced to do something. They’re able to remain completely immersed in their characters, feeling as if the world is unfolding in direct response to their actions.”

In a successful narrative adventure, the DM keeps laying track by dropping hooks. Each one shows a course that brings the characters closer to their goal, so the players willingly choose to follow. 

Good hooks power meaningful choices even better than linear scenarios. 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.

As for Descent Into Avernus, the adventure brings evocative locations and vivid characters to an unforgettable journey through Hell. Your heroes get to adventure in Hell! Fixing the weak connections merits a bit of creative work. For ideas, see Merric Blackman’s account of running the campaign, Justin Alexander’s Remixing Avernus, and my own post Improve the Start of Baldur’s Gate: Descent Into Avernus With These 2 Add-On Adventures.

Related: Why Dungeons & Dragons (and roleplaying) took years to leave the dungeon.

5 Situations That Tempt Every Dungeon Master to Railroad Their Players

If you believe countless Dungeon & Dragons adventure reviews, nothing ruins an scenario as quickly as a linear design. In a linear adventure every group follows the same plot thread, through the same scenes, to the same conclusion. At best, critics accuse linear adventures of eliminating the players’ choices between scenes. At worst, critics say linear adventures require dungeon masters to abuse their power to shunt players along a railroad. Instead of steering the adventure, players follow a fixed story.

In my last post, I explained that players don’t hate linear adventures as much as reviewers and dungeon masters think. We tend to judge harshly because we see the lack of options. In a successful adventure, players never see the walls.

Many gamers conflate linear adventures with railroading, but that mistake tars decent adventures. Players seldom mind linear adventures, but few players tolerate railroading. DMs who railroad deserve player complaints.

“Railroading is not linear prep,” Phil Vecchione from Gnome Stew explains. “Railroading is the game master’s reaction to a player’s action, in an effort to drive the game in a specific direction. That reaction is to typically negate, reverse, or shut down a player’s action, in order to get the game moving in the GM’s desired direction.”

A successful linear adventure invites certain choices and makes assumptions about outcomes, but it never forces a result. Some of the success of an adventure depends on the designer’s ability to predict choices and outcomes. (See Actions Players Always Take and Choices Players Never Make.) When the predictions fail, adventures tempt DMs to railroad.

In some game situations, when the players veer from the plan, the temptation to railroad becomes nearly irresistible. These situations appear in nearly every DM’s career. Instead of succumbing to temptation, what should we do?

1. When an action leads in a direction you never anticipated, improvise.

Every DM eventually faces a player decision that nullifies all the planning that prepared for a game. “If you can’t improvise, you’ll eventually hit a wall you can’t climb over, or find yourself trapped in a corner and unable to talk your way out,” D&D senior producer Chris Perkins writes.

“Improvisation demands equal measures of intuition and confidence. DMs who lack sufficient intuition or confidence tend to have trouble improvising at the game table. The good news is that DMs, being creative souls, rarely fall short in the intuition department. They know a good story from a bad one, a well-developed character from a cardboard cutout, and so forth. However, confidence is a far more rare commodity, and DMs who lack the confidence to trust their intuition often have trouble improvising behind the DM screen. I know because I’ve been there.”

Entire books aim to help game masters improvise, but often the trick comes down to making a leap into the unknown–or unprepared. If you find yourself stuck, call for a break, spend a few minutes finding inspiration, and then go with the idea that seems most fun.

2. When an action may deliver an easy win that cuts an adventure short, reward the ingenuity and then add complications.

Mike “Sly Flourish” Shea likes to note that we DMs match our one brain against the players’ six brains—a serious mismatch. Sometimes players invent a plan that threatens to skip the middle of an adventure and deliver an easy victory.

As one possible response, DMs can grant players an easy win. Players relish a chance to thwart the villain (and the DM) with an ingenious plan. Perhaps the characters built around deception or infiltration get to shine.

But an easy win can’t cut a 4-hour convention adventure to a half-hour assassination. If you want to spare more of your preparation, reward ingenuity with some success, and then add reasonable complications that make the plan unravel. Perhaps the players reach the throne room, but discover that the lich-king has left to sow terror and whatnot. Now the players must decide how long they dare to wait in the heart of an enemy stronghold.

Many ingenious plans start with the players impersonating the villains’ cohorts and seeking a free pass to the boss’s war room. In those scenes, I seek ways to help the heroes while also stirring trouble. Often some of the party must pass as prisoners or foreign allies. What if guards demand to take prisoners to the dungeons and allies to the rest of their delegation? Sometimes I add tests of loyalty. “We’ll take you to the Prince of Murder, but first help us execute your prisoners.” Even when a deception succeeds, such tests suggest that smart foes hold some natural suspicion.

3. When players try to start fights during an interaction scenes, pause the action.

Sooner or later, every dungeon master sees players stop a role-playing scene to start a fight. As the party talks with a scheming queen, a player blurts out, “I hit her with my axe!” Picking a fight during such an interaction typically causes problems because the adventure expects the queen to bridge the way to the rest of the adventure. The attack burns the bridge and leaves players running from her heir and her army.

These scenes tempt me to add a hidden pit trap between the charging barbarian and the queen. Actually, that makes some sense. If I were boss of some D&D land, my throne room would feature a trap door.

If the archer or warlock launches a ranged attack, every DM feels tempted to turn the queen’s guards into invincible minor minions who crush the party. Then the queen threatens to hang the characters unless they continue the scheduled adventure. Steal from the classics.

A better, non-railroad response includes 3 steps: (1) pause the attack, (2) learn the root cause of the attack, and (3) reroute the adventure.

Instead of letting the instigator roll damage, pause the action.

If only one player wants the fight, Teos “Alphastream” Abadia explains how he lets the party intervene in-game. “I’ll freeze time. ‘Everyone can see that your character is about to kill this person. Everybody has a chance to stop this. What do you all want to do?’” Teos makes it clear that the single player stands alone against everybody else in the party. See What To Do When A Player Interrupts A Role-Playing Scene To Start A Battle.

If the whole party seems eager for battle, look for the root cause of the attack.

Perhaps the players see the queen as a bad ally, so when the adventure leads to an alliance of convenience, the players rebel. Murder in Baldur’s Gate assumed characters would support one of three patrons who vied for power. The patrons start unsavory and, as they gain power, become worse. My players wanted no part of it. I needed to find a more agreeable patron.

Often, the players see the queen as a villain they will fight eventually. Why not solve the problem now? As DM, tell the players how their characters’ lifetime of experience in the game world reveals flaws in the players’ plan. “The reputation of the queens’ knights leads you to believe that they can easily defeat you.” If the players attack anyway, finish the fight, and then find another patron.

4. When plot features recurring villains, but the party blocks their escape, plan for escape, but prepare for a new villain.

Every DM loves a recurring villains. But to establish one, you need to introduce the villains and then somehow invalidate the players’ decision to murder them.

Typically, DMs underestimate the players, and so potential recurring villains die during their first scene. Our odds stand at 6 brains to 1. As a slim advantage, we have time to plan. Don’t make a potential recurring villain the most threatening target in an encounter. Don’t leave the villain exposed between their turns. Plant a potential barrier along the escape route. (I’m not above an escape via spinning bookcase.) Start the escape while minions remain to block pursuit and while the villain still has enough hit points to survive the players’ biggest attacks. Accept the (probably) inevitable premature death. Prepare to call another foe from the bench.

In the interest of story, Monte Cook’s acclaimed adventure Dead Gods requires villains to escape the players. “It’s crucial to the story that some of the cross-trading khaasta escape with the thief of charms and some of the stolen beauty. If necessary, the DM can increase the number of khaasta in the encounter or rule that some of the creatures have already escaped through the portal by the time the PCs arrive in the alley (and make it clear to the heroes that this has happened). The latter option foils the use of a gate ward or surelock spell to stop the khaasta.” Unfortunately, once the DM sees the need for such measures, it’s probably too late.

5. When the story includes the players’ capture, but the players win instead, wait for another chance.

The most egregious crime of railroading comes when a DM wants players taken captive. In adventure fiction, heroes get captured regularly. So DMs dream up similar stories, and then try to force a capture despite the players’ determination to never get taken alive.

Notoriously, A4 In the Dungeons of the Slave Lords starts with the players’ capture. This adventure originated as a tournament adventure where players adopted pre-generated characters already imprisoned. When the authors adapted the adventure for home campaigns, they anticipated complaints. “It is likely that [the players] will be angry at the DM for putting them in such an ‘unfair’ situation.”

The Adventurers League adventure Shackles of Blood depended on players getting captured. Some players went along for the ride, but others resented it. I tweaked the adventure so players who thwarted capture could choose to become captives as a heroic gambit. No one resisted that.

To engineer a capture, DMs needs to hide an encounter’s threat to the players, block the characters’ attempts to flee, beat any signs of an unexpected rally, and so on. During all this, if the players see signs of their DM bending the odds to thwart their escape, they will feel railroaded. You can’t plan for a capture.

None of this means your players’ characters will never be captives.

Use capture as an alternative to a total party kill. Save your escape-from-the-dungeon scenario for a time when players ignore warning signs, make bad choices, suffer setbacks, and ignore any chance to run. Those times happen—trust me. Then, instead of rolling new characters, have the old characters wake in chains. The players will feel grateful for a second chance.

Do Dungeons & Dragons Players Hate Linear Adventures? Not When DMs Avoid Two Pitfalls

A linear adventure is written, or at least planned, so every play group follows the same plot thread, through the same scenes, to the same conclusion. In Dungeons & Dragons, linear dungeons set the pattern, with walls and doors that channel players along a single route. Without walls, a linear adventure only ever shows players one course of actions to a successful end.

At best, critics accuse linear adventures of robbing players of choices between scenes. At worst, critics say linear adventures require dungeon masters to abuse their power to shunt players along a railroad. Instead of steering the adventure, players follow a fixed story.

Despite the criticism, players don’t hate linear adventures as much as DMs think. We tend to judge harshly because we see the lack of options. But in a successful adventure, players never see the walls.

When the walls become plain, players may complain about a lack of freedom. Linear dungeons, with their obvious walls, always risk criticism. Adventures without walls can also flaunt a lack of options. Imagine an adventure where players follow a patron’s plan or a commander’s orders from scene to scene. Unless catastrophe upsets the plan—or assassins reach the commander—the adventure would feel scripted and less satisfying.

Linear adventures work best when success in each scene brings the clues that lead to the next scene. Then, for all the players know, a different choice in the scene or unseen clue could have spun events in a different direction. To players, each success leads to the clues needed to set a new objective. Players favor one choice over an overwhelming number of choices, and certainly over feeling stuck without a direction.

Make no mistake, players still like to face a few, clear choices. Linear adventures grow better when they include decision points that pose options. (Of course, such adventures no longer qualify as linear.)

For adventure creators, linear adventures bring advantages. They’re compact. Authors can devote their energy—and a published adventure’s pages—to developing content that reaches play. No DM with an ingenious dungeon room wants players to miss it.

The limits of a convention time slot makes linear adventures particularly common in programs like the D&D Adventurers League. Linear adventures can consistently fit in a convention time slot. Players in organized play tend to forgive the limits imposed by a 4-hour session, but some do complain when adventures reveal a lack of choices.

But organized-play adventures with more options draw complaints too.

Adventurers League administrator Claire Hoffman explains that when adventures offer more choices, some DMs gripe about prepping content that may not reach play.

Most DMs understand the value of extra prep, but some players fuss too. Those who enjoy the accomplishment of clearing a dungeon or of completing every quest feel frustrated when an adventure teases them with more options than they can explore. The Howling Void by Teos Abadia sets a brilliant example of a 4-hour adventure with a wealth of options. In an elemental node, Earth motes float like aerial islands. Players must choose which to visit. Teos explains that some players left the adventure disappointed because they could not explore every location. The adventure proved so fun that players wanted it all. Still, adventures shouldn’t cater to completists. Better to leave players wanting more.

Linear adventures may fall short of an ideal, but if they avoid flaunting their limits, players seldom mind. One exception bothers players. When the only choice suggests a style of game that players dislike, they will resist.

During these rebellions, the players telegraph what the want to do in the game. In a podcast, Mike “Sly Flourish” Shea explained, “If the king is speaking, and the barbarian charges him, maybe you ought to start the players in the dungeon.” Clearly players crave a fight. “I’ve seen it the other way too, where in my DM-head I’m thinking, now they’re going to fight 12 orcs, and the players are doing everything they can to negotiate with the orcs. ‘Just fight the orcs!’ But the players are telegraphing their desire to have an interaction.”

If your players dislike intrigue, and the next clue in a linear adventure suggests they infiltrate a masquerade, that’s when they rebel.

You can avoid such problems by setting up situations tailored to the style your players favor. If you know your players, such tailoring probably becomes natural. If not, then an ideal episode lets players choose styles. Let players enter the castle by infiltrating the masquerade, sneaking over the walls, or battling through a secret entrance into the dungeons below.

Players don’t hate linear adventures; players hate being driven into a style of game they dislike. Players who read gaming blogs may resist by accusing your adventure of railroading, but the rest will start a fight at the masquerade.

Running Shackles of Blood: Making the good adventure into a great session

The free, issue 4 of Dragon+ includes the Dungeons & Dragons module Shackles of Blood by Joshua Kelly. This adventure comes from the Adventurers League Expeditions program. Normally, this program only lets you play such adventures in public venues such as game stores and at conventions, so the download introduces home players to the program. Shackles of Blood features a turning point in the Rage of Demons storyline, and concludes with an unforgettable final battle.

Shackles of Blood flooded arena

Shackles of Blood – the finale in a flooded arena

At this year’s Gen Con, I ran Shackles of Blood several times. Now, I will tell you how to make this good module into a great play experience.

If you plan to play this adventure, stop reading now. But if you intend to run it as a dungeon master, or simply want to peer under the hood with me, keep reading.

The dungeon master’s dilemma

The thorniest aspect of Shackles of Blood stems from the way leads characters into a virtually unwinnable encounter. The set up serves the aim of capturing the PCs so they wind up in that great final battle. During one session I ran, when the players’ capture left them feeling defeated, one said, “Don’t worry, this just leads to the last encounter and, trust me, you want to play the last encounter!” He had already playtested the adventure.

At Gen Con, the dungeon masters running Shackles felt conflicted about sending players into an encounter they could not expect to win or even avoid. Most DMs feel that railroading ranks as the worst abuse of their power. To be fair, none of the players at my tables felt railroaded. They had never read the adventure, so they never knew it was a setup.

The setup

The adventure begins with PCs charged with finding a family of halflings, the Tinfellows, who disappeared from a valley near the city of Hillsfar.

Meanwhile, a group of Hillsfar’s Red Plume guards plots to capture the PCs so they can be forced to fight in the city’s arena. Even if the PCs avoid an ambush, their investigation leads them to be overwhelmed by Red Plumes firing crossbow bolts laced with sleeping poison.

Tactics for the Red Plumes

When the Red Plumes battle the PCs, they fire crossbow bolts until one of the PCs fails a save and falls unconscious. Then a Red Plume can bring a knife to the sleeping character’s throat and the demand surrender in exchange for the character’s life. Of course, he’s bluffing, but the players will typically stand down. Because they chose to surrender, they feel like heroes opting to fight another time. Any PCs who call the bluff become the focus of attack.

In the battle with the Red Plumes, avoid letting the PCs scatter so that some escape. Hold a few Red Plumes back at the perimeter of the battle. Some PCs may still use invisibility or other tricks to get loose. If they succeed, a divided party makes running the adventure a bit more challenging, but the free PCs will trail any captives.

Plan B

If the players manage “the impossible dream” of escaping the Red Plumes, the adventure supposes that the party will return to their patron. (They probably won’t. See “Choices players never make.”) She tells them to get captured intentionally. After the players win against impossible odds, they must go back to lose on purpose. How unsatisfying!

Normally, players would trash a lousy plan that puts them in shackles and deprives them of their gear, but for the sake of the adventure, they will abide. Then you, as the DM, must improvise a narrative that puts players into chains.

Dismantling that unseen railroad requires a better plan B. Here is what I recommend.

In the unlikely event that the players escape capture during their investigation, they cannot rescue the entire family of Tinfellows. In my tweak, the players can rescue some of the Tinfellows, but most have been sent ahead to the arena at Hillsfar. Now, whether the players get captured or not, they must return to Hillsfar to rescue Tinfellows from certain death.

This pursuit leads the PCs to a meeting with Margery “Mags” Thrier outside the Hillsfar arena.

Unless your table features the first-ever all-human band of adventurers since the era of little brown books, the party must find a way to get their non-humans into Hillsfar and to the arena. Some party members might adopt disguises—it works for Breex Vandermast. Others could pose as captives bound for the arena. If you prefer to avoid this challenge, move Mags and the slave market outside the Hillsfar gates.

Mags explains that she purchased the Tinfellows legally and refuses to relinquish her property without compensation. The Tinfellows languish somewhere deep under the arena, slated to fight, and undoubtedly die tomorrow. If the players would be willing to trade places in the upcoming battle, Mags will set the family free.

Mags’s pet Goliath tries to startle the players. When they prove their nerve, she questions them about their combat experience. Inevitably, some party members will rise to pose as tough guys.

If the players worry that Mags will betray them, she steps to a betting kiosk and places a bet on the PCs in the next day’s battle of the bell. “Now if you lose, I lose, but I have a feeling about you lot.”

Once the players agree to take the Tinfellow’s place, Mags warns that if they fail to fight, the Tinfellows will fight, and die, in an upcoming contest.

Because of the non-human PCs, the entire party must surrender to the guards and go to that cage on the arena floor.

Dismantling the railroad

Now that you have a plan B that leads to the final encounter, you don’t need the PCs to lose to the Red Plumes. Instead, that confrontation can end in a draw or even a win. The Red Plume captain has no reason to see his men die in a fight with the PCs. If the players slay a couple guards, I suggest having the captain call a truce. He can tell the players that the Tinfellows have already been sold to Mags at the arena in Hillsfar. He might even promise not to take any more captives from the hills. You can decide whether he tells the truth.

Meeting Breex Vandermast

The half-orc sorcerer Breex Vandermast serves as the adventure’s final villain.

Whether the players find themselves on the arena as willing or unwilling fighters, they must meet Breex before the battle. This can happen as written, on the road to Hillsfar, or later with the PCs caged on the arena floor.

Either way, Breex tells the PCs how much he will relish seeing them die in the arena. He taunts the non-human characters for their filthy taint, and then turns his disgust on the humans for joining such rubbish. Describe Breex’s filed down canine teeth. Tell how his ears appear clipped to a human roundness, and how he wears a powder that lends his skin a more human tone. When the players identify Breex as half orc, I guarantee that his hypocrisy and bigotry will inflame them. During the arena contest, my players searched the stands for Breex, eager for a chance to strike at him.

The Bell in the Depths

The adventure ends with a battle in the Hillsfar arena that pits the PCs against a team of halfling gladiators. The contest spans platforms erected over the flooded arena floor. Both sides race to ring a bell atop a central tower.

Describe the battleground as fenced and flooded enclosure on the larger arena floor. That way, when blood-crazed spectators spill onto the floor to climb the pool’s walls and tear at its bolsters, its collapse and sudden draining seems inevitable.

Shackles of Blood - drained arena

Shackles of Blood – drained arena

In the battle of the bell, a 15-foot gap separates the halflings’ tower from the bell tower. The halfling thugs have a 15 strength, so they can jump that gap. This means that if the halflings win initiative, they could ring the bell before the players even act. Let the halflings’ overconfidence and their urge to preen for the crowd slow their assault on the bell. On their first turn, the thugs take positions on the bell tower.

The halfling spies can use Cunning Action to gain an extra dash action on their turns. If the halfling druid casts Longstrider on a spy, the ally can cross the arena quickly and assault any PCs who choose to stay on their tower. In my sessions, the druid never managed to concentrate on Barkskin long enough to matter, so Longstrider made a better buff. Because the druid lacks long-range attacks, don’t make him an easy target. Instead, he buffs allies and carefully advances into Thunderwave range.

A halfling who uses a dash action can swim the 4 squares from a starting tower to an assault tower in a single turn. That pace brings them out of the water before the quippers can attack.

Don’t bother holding Breex’s entry until all the halflings have been incapacitated. Bring him out when the contest starts to lull. The players will be eager for the showdown.

As the Red Plumes struggle to quell riots, the PCs will have no trouble rescuing the Tinfellows. After prevailing in the arena battle, the players will feel they earned this easy success.

How running an adventure eight times can be fun and educational

As I’ve mentioned in other posts, I run a lot of games at conventions. Sometimes I run the same adventure as many as eight times. You might think the repetition grows tiresome, but I like it. Rerunning an adventure brings three benefits:

  • I like the fun at the table more than I like preparing to play. If I run an adventure more than once, I can invest a lot of time in preparing, and then see my efforts pay off in more than one session.

  • With each run through an adventure, my delivery improves. I emphasize elements that players’ like best and I polish or avoid the rough patches. Sometimes I learn things. This process mostly works in the players’ favor, but as I perfect the monsters’ tactics, the fights get tougher.

  • I can experiment with my descriptions and characterizations, and then witness how small changes influence the players’ decisions.

Any game master knows that something as small as the amount of description given to each item in a room can sway a party’s choices. I enjoy seeing how even small changes can influence decisions.

ADCP5-2 Best Defense Battle Interactive

ADCP5-2 Best Defense Battle Interactive at Origins 2013

The lessons I learn make me better at influencing players’ choices. That sounds bad. I swear that I use any insights I gain for good rather than evil.

Running a convention game to satisfying conclusion within a strict time slot demands some finesse. I want to present the adventure so the players’ decisions just happen to follow the broad outline of the adventure. First, I never want to lead players off track. Every game master has seen bit of descriptive fluff lead players into a wild tangent. In a home game, you can run with a tangent, but not in a typical convention game. If players stray off track, I want to lure them back, gently. Despite all this, I never want players to feel railroaded. I would rather improvise than run a railroad.

Most adventures written for a convention time slot expect characters to follow a plot arc, but the good ones offer players some interesting decisions along the way.

I want the players to weigh as many choices as the adventure offers, and I want all the options to seem compelling. When players enter a discussion weighing the merits of two options, score one for me and the adventure. Whenever players speculate about how events might have changed if they had chosen differently, score another.

If the adventure offers a decision that the players’ never consider, then I need to adjust for the next table. For example, if the adventure intends for players to face a dilemma over whether to complete their objectives or to rescue some captives, but the players always choose one option without weighing the other, then I need to tweak things so the players face a thornier, more interesting choice.

If I do my job well, then during my next run of the adventure, the players surprise me and the session goes differently than the last. That is how the dungeon master wins Dungeons & Dragons.