Monthly Archives: December 2020

5 Roleplaying Products That Shaped How I Play Dungeons & Dragons 1978-2000

Leave a reply

Tomb of Horrors (1978)

In the early days, I enjoyed plenty of time to create my own adventures, so I had little interest in playing the published ones. But I still drew inspiration from them. Nothing inspired like Tomb of Horrors.

tomb-of-horrors-1e-coverBefore the tomb, dungeons tended to lack personality. Dungeon masters followed the examples in the rule books, serving players bland tunnels, square rooms, and monsters waiting to be killed.

The tomb overflowed with the personality of its fictional creator and its real-world author. Gary Gygax admits to “chuckling evilly” as he developed the tomb. His wicked fancy suffuses the dungeon. The tomb brought a menace unmatched by other dungeons. Its legend still draws players, despite its reputation for dead characters and tedious play.

The best part of the adventure might be the keyed illustrations that revealed its locations. The illustrations transported me into the tomb and tantalized me with potential clues to its the mysteries. I think writers sometimes avoid locations that demand long and unwieldy explanations, so adventurers encounter too many conventional 10’x10’ rooms with a pile of debris in the corner. With the tomb, Gary and his artists loosed their imaginations, and the place came to life. See Picturing the dungeon – keyed illustrations.

For more, see Tomb of Horrors tests patience, but still ranks as Dungeons & Dragons’ best villain.

Queen of the Demonweb Pits (1980)

You can fault some details in Queen of the Demonweb Pits, but not its big ideas. This adventure took the scope of Dungeons & Dragons and blew it wide open.

Q1 Queen of the Demonweb Pits CoverStart with the Demonweb, a web of pathways floating through impenetrable fog. The material of the path moves slightly. “Close examination will reveal faces, twisted and tortured, pressed against some invisible barrier, silently mouthing screams and howls.” These are the lost souls of the Abyss. Along the path, unsupported doors open into extradimensional spaces. At first, these doors lead to Lolth’s creatures. On the last level of the web, the doors open on alternate material planes that she targets for attack or other schemes. In unlocking these planes, the adventure made the world of Greyhawk and its kin seem like specks floating an a sea of creation.

Once players leave the web, they find Lolth’s stronghold, a colossal, steam-powered spider that walks across an alien desert. Many players disliked the spider-ship for its collision of fantasy and steampunk, but I loved it. A diet of Michael Moorcock books and Arduin had already shattered my reservations about mixing such elements. The spider-ship seemed like a fitting creation for a goddess whose power spanned a multiverse. The ship’s inscrutable purpose and destination suited her chaos.

Lolth’s spider-ship, the Demonweb, and its portals suggested a D&D game with a scope that felt breathtaking.

For more, see How Queen of the Demonweb Pits opened Dungeons & Dragons to the multiverse

Escape from Astigars Lair (1980)

In 1980, Judges Guild published Escape from Astigar’s Lair, a slim module that sold for just $2. The adventure so charmed me that after I ran it, I created a similar challenge of my own to unleash on players.

Escape From Astigar's LairThe action starts when the wizard Egad dons a cursed helm and becomes possessed by the evil spirit of the mighty Astigar. Players take the roles of the druid Danier and the ranger Therain, who begin shackled to a wall in Astigar’s dungeon complex. The escape encourages shrewd problem solving. How can you cross a chamber swarming with flying lizards as voracious as piranha? How can you force Egad to remove the cursed helm? The obstacles in the lair inspired challenges that I would add to my own game.

I loved how Escape from Astigar’s Lair showed that combining oddball powers with ingenuity could prove more fun than blasting away.

For more, see Little-known D&D classics: Escape from Astigar’s Lair.

Fez (1980-1985)

In 1981, my buddies and I, at our first Gen Con, stumbled into the Fez tournament and had a blast, more fun than we had in that year’s AD&D Open. For several years, even as our interests wandered from AD&D to other role-playing games, Fez remained the Gen Con event we most eagerly anticipated.FezI The Wizard’s Vale was originally printed as Fez I Valley of Trees

In this blog, I’ve shown how a reliance of skill checks tends to encourage players to focus on their character stats and to take focus from the game world. When a skill check solves any problem in the game world, the details of the problem become unimportant.

When I played Fez, little seemed to demand a roll. Behind the dungeon master’s screen, Fez was a D&D game complete with AC and HP. From my perspective, Fez factored rules out of the game, making immersion the game world all important. Normally, I would not want to play battles without character stats, but in Fez, the objective seemed to be to avoid fights.

Fez featured a play style different from the typical D&D game, and it blew my impressionable mind.

For more, see Little-known D&D classics: Fez.

Dungeons & Dragons third edition (2000)

Game historian Shannon Appelcline calls D&D’s original design chaotic modeling, with inconsistent game systems handling different parts of the game world. So Strength has a range of 3-17, and then 18/01 to 18/00, while other attributes range from 3-18. Thieves roll under a percentage to gain success, attackers try to roll high on a d20, and (in some versions) ability checks require a d20 roll under an ability score. “The fact that the game couldn’t even keep its core range straight (was it yards or feet?) says a lot.”

3E edition launch shirtIn Thirty Years of Adventure: A Celebration of Dungeons & Dragons, Steve Winter wrote, “By 1987, the science and/or art of roleplaying game design had progressed significantly since AD&D’s first appearance. Games such as Runequest, The Fantasy Trip, Chivalry & Sorcery, Paranoia, Pendragon, Warhammer Fantasy, Star Wars, Call of Cthulhu, and many others showed that there were innumerable ways to build a quality, innovative RPG.”

Second edition designers Steve Winter and David “Zeb” Cook did their best to sort out D&D’s “ugly little systems that didn’t integrate with each other,” but the system’s core remained mired in the RPG stone age. In a D&D podcast episode examining the second edition, Steve Winter said, “There were all kinds of changes that we would have made if we had been given a free hand to make them—an awful lot of what ultimately happened in third edition. We heard so many times, ‘Why did you keep armor classes going down instead of going up?’ People somehow thought that that idea had never occurred to us. We had tons of ideas that we would have loved to do, but we still had a fairly narrow mandate that whatever was in print should still be largely compatible with second edition.” So D&D held to chaotic modeling.

In 1997, Wizards of the Coast took over TSR and new head Peter Adkison set the direction for a new edition of D&D. In Thirty Years of Adventure, he wrote, “After twenty-five years D&D was due for a major overhaul, but that the changes to the game should make the games rules more consistent, more elegant, and support more possibilities for different styles of play.” Adkison gave lead-designer Jonathan Tweet and the rest of his team the freedom to bring 25 years of innovation into D&D. The centerpiece of the revamp came in the form of the d20 core mechanic that became the name of the game’s foundation.

Future_of_D+DIn addition to the chaotic rules, D&D’s characters suffered from limitations Gary had created either for game balance or just to make humans the dominant race. “My biggest beef with the older rules were the consistent limitations on what characters could become,” Adkison wrote. “Why couldn’t dwarves be clerics. Why could wizards of some classes only advance to some pre-determined level limit? Why couldn’t intelligent monster races like orcs and ogres pick up character classes? In my mind these restrictions had no place in a rules set but should be restrictions established (if at all) at the campaign-setting level.”

I shared Peter Adkison’s beefs. When Wizards of the Coast made their big announcement leading to the third edition, they produced a shirt giving a taste of the barriers that the new edition shattered. For me, this shirt showed how third edition would embrace 30 years of role-playing game design ideas, and how it swept away senseless limitations. After years often away from D&D, mostly playing other games, third edition welcomed me back.

Related: 1977–1978

5 Roleplaying Products That Shaped How I Play Dungeons & Dragons 1977–1978

6 Replies

Holmes Basic Set (1977)

The blue box of the 1977 Holmes Basic Set introduced me to D&D. To 99% of Dungeons & Dragons players, the edition that introduced them to the game stands as their most important. Why should I be different?

Dungeons & Dragons Basic SetPlayers who came later never saw how revolutionary the game and its brand of fantasy seemed in the 70s.

Then, games sold as toys and they were all terrible. They suffered from stupid, and random mechanics: Roll a die and move that many spaces. These games offered minimal choices. In them, the winner became obvious well before the end, yet they took forever to finish.

Before I saw D&D, I heard of the game in a 12-year-old’s lunch-room pitch. After school, I sat with a sheet of graph paper and tried to imagine how the game would play. I got nowhere. From my experience rolling a die and moving that many squares, I had no clue how a game could allow the things the kids claimed.

So in a mere 48 pages, the 1978 basic Dungeons & Dragons rule book edited by J. Eric Holmes shattered my notion of what a game could be.

As a kid in the 70s, All the fantasy I knew came from picture books. Stories where trolls lived under bridges and bugbears under beds. Nothing prepared me for a game inspired by Appendix N.

For more, see 4 Pop-Culture Assumptions That Dungeons & Dragons Destroyed.

City State of the Invincible Overlord (1977)

When I discovered D&D, TSR had yet to publish any setting information other than the hints published in the Greyhawk and Blackmoor supplements. For a break from dungeon adventures, the original rules suggested wandering the hex map boxed in Avalon Hill’s Outdoor Survival game and rolling encounters.

City State of the Invincible OverlordSo when the City State of the Invincible Overlord reached me, the scope of my game exploded. The $9 setting included a huge 34″ x 44″ map in four sections, and 11″ x 17″ map of the castle of the dwarven king backed with a sprawling dungeon map, three booklets detailing over 300 individual locations and the non-player characters who populate them, maps for ten more dungeon levels, plus players’ maps.

The package shows remarkable creative output. No locations in the sprawling city rate as too mundane for descriptions. Even with five bakers, the guide finds something interesting to say about each.

Instead of adopting the entire City State, I cherry picked stuff I liked. My 1977 copy of the city state still contains the pencil marks noting my favorite bits. The best inspiration came from the rumors seeding every location. Now we would call them adventure hooks. In an era when most players just wandered, these ideas suggested a way to steer the game from aimless looting to plot.

For more, see A Butcher, a Baker, and Naughty Nannies in D&D’s First Setting Book: City State of the Invincible Overlord.

Arduin (1977).

Inspired by the Greyhawk and Blackmoor supplements, Dave Hargrave printed his house rules, lore, and advice in 3 little, brown books named after his world, The pages of the Arduin Grimoire teemed with fresh ideas. When I discovered the books, I became enchanted. I haven’t found a game book that proved as enjoyable to read.

In an era when state-of-the-art setting design consisted of a map paired with encounter tables, Hargrave opened a world with detail that rivaled any setting that came later.

The Arduin TrilogyDave Hargrave’s campaign world of Arduin was not built; it was piled. To create Arduin, Hargrave took every fantastic element he dreamed up or fancied and piled them into one work of love. He preached bigger imaginary playgrounds. “The very essence of fantasy gaming is its total lack of limitation on the scope of play, both in its content and in its appeal to people of all ages, races, occupations or whatever,” He wrote. “So don’t limit the game by excluding aliens or any other type of character or monster. If they don’t fit what you feel is what the game is all about, don’t just say ‘NO!,’ whittle on them a bit until they do fit.” (Vol. II, p.99)

He tore up the D&D rules and offered wild changes. His specific rules hardly mattered. The message mattered: Hargrave encouraged me to own the rules and my games and to create a game that suited me and my players.

For more, see The Arduin Grimoire: The “Coolest RPG Book Ever,” also the Book Gygax Mocked As Costing Readers 1 Int and 2 Wis.

Melee (1977) and Wizard (1978)

Over my first years years of playing D&D, the fun of the game’s battles waned. My games drifted away from the fights, and toward exploration and problem solving.

Advertisment for Melee and WizardGame designer Steve Jackson understood the trouble. In Space Gamer issue 29, he wrote, “The D&D combat rules were confusing and unsatisfying. No tactics, no real movement—you just rolled dice and died.” Steve turned his desire for better battles into elegant rules.

In the late 70s, ads in Dragon magazine convinced me to spend $2.95 on Jackson’s combat game Melee and $3.95 on the magic addition Wizard. I half expected to be disappointed. Role playing games required hefty books, and Melee and Wizard were not even full role playing games, just tiny pamphlets with paper maps and cardboard counters. (Melee and Wizard would become The Fantasy Trip roleplaying game.)

I loved playing the games so much that they changed the way I played D&D.

The revelation came from the map and counters. You see, despite D&D’s billing as “Rules for Fantastic Miniature Wargames,” I had never seen miniatures used for more than establishing a marching order. From local game groups to the D&D Open tournaments at Gen Con, no combats used battle maps, miniatures, counters, or anything other than the theater of the mind. Miniatures struck me as a superfluous prop, hardly needed by sophisticated players. The idea of bringing a tape measure to the table to measure out ranges and inches of movement seemed ridiculous.

I failed to realize how much battle maps would transform the game. Without a map, players struggle to follow the action unless things stay simple. In virtually ever fight, players just opted for the front, swinging a weapon, or the back, making ranged attacks. Two options. If you were a thief, you could also try and circle around to backstab. As Steve Jackson wrote, “You just rolled dice and died.”

Melee and Wizard included hex maps and counters and simple rules for facing, movement, and engagement. After just one game, I felt excited by all the tactical richness that I had formerly snubbed.

For more, see Melee, Wizard, and learning to love the battle map.

Runequest (1978)

With Dungeons & Dragons, Dave Arneson and Gary Gygax invented the role-playing game. With Runequest, Steve Perrin and Ray Turney showed how to design a role-playing game.

Runequest second edition

Steve Perrin first entered the hobby when he distributed his D&D house rules, The Perrin Conventions, at DunDraCon in 1976. This led to Runequest, a game that replaced every aspect of D&D with more flexible, realistic, and simpler alternative: Skills replaced the confining class system. Experience came from experience, not from taking treasure. Armor absorbed damage from blows that landed. Combat simulated an exchange of blows, dodges and parrys. Damage represented actual injuries. Rather than a hodge-podge of mechanics, Runequest introduced the idea of a core mechanic that provided a way to resolve every task. Rather than the game setting implied by all of Gary’s favorite fantasy tropes, Runequest supported Glorantha, a unique world built as a consistent, logical setting.

Suddenly, D&D’s rules seemed as dated as gas lights and buggy whips. I enjoyed an occasional D&D game, but I switched to electric lighting until D&D adopted much of the same technology for third edition.

Today, simulation seems less important than in 1978. I now see that rules that made D&D unrealistic also added fun by enabling the game’s combat-intensive dungeon raids. For more, see The Brilliance of Unrealistic Hit Points and The Fun and Realism of Unrealistically Awarding Experience Points for Gold.

However, elegance remains as important as ever. Aside from earlier D&D editions, D&D’s current design owes more to Runequest than any other game. Third-edition D&D’s lead designer Jonathan Tweet called Runequest the role-playing game that taught how to design RPGs. Actually, Runequest taught everyone how.

Jonathan Tweet credits Runequest with a long list of innovations that reached D&D.

  • prestige classes (rune lords, rune priests, and initiates)
  • unified skill-combat-saving-throw system
  • ability scores for monsters
  • 1 in 20 hits are crits
  • ability scores that scaled up linearly without artificial caps
  • a skill system that let anyone try just about anything
  • armor penalties for skill checks and spellcasting
  • creature templates
  • faction affiliations
  • hardness for objects
  • chance to be hit modified by Dexterity and size
  • iconic characters used in examples throughout the rule book
  • rules for PCs making magic items.

Next: 1978-2000

Getting Players Moving, Especially When No One Wants to Drive

2 Replies

If you game master enough roleplaying games, you will eventually land a session that keeps stalling because no one wants to drive—no one wants to speak for the group. For instance, if the party has to pick a restaurant, then everyone spends 10 minutes saying “I don’t care. What do you want?” We’ve all been there, just probably not while in a dungeon. Most often, such tentative groups form when strangers meet for a game, often at conventions. But any group can lag, and the techniques for nudging a party ahead can prove useful beyond a convention hall.

To be clear, not every lull in a game needs an intervention. If the group enjoys slowing to roleplay, let it flow. If a group starts planning for the challenge ahead, then sit back and relish it. These situations show a group immersed in the game world. Score a win for the dungeon master.

Sometimes folks in a group of strangers feel presumptuous speaking for the whole group. When everyone keeps hesitating to call shots for the group, many DMs smooth the way by asking for individual decisions. “Making a choice for your character seems less daunting than making one for the group. Low stakes choices can break the ice,” writes Louis Bamberger. “Recently I ran a group that was pretty quiet. Their characters were at a town carnival, so I asked them what game they would play and what food or drink they would order. After each person explained their choices, a snowball of enthusiasm grew with each person’s answer.” By the end of the session, a group of players new to roleplaying games felt eager for another go.

Die rolls, even inconsequential ones, make another good ice breaker. Teos “Alphastream” Abadia gives an example. “In a marketplace, have an arcane character make a bogus check to point out a vendor’s wares could be spell components, just to get them to talk. Data tends to help us make decisions, so skill checks, even granting minor information, tend to help move us to action.”

When I serve as DM for tentative group, I tend to make two adjustments.

First, I pose more choose-your-adventure-style choices.

This helps narrow a limitless range of options to a menu of sensible actions. At worst the table can vote. Often I nominate one player as caller-for-the-moment to make a decision. DM Tom Christy sometimes selects the most charismatic character—the natural leader. You can also nominate a leader based on circumstantial qualifications. Underground, let the dwarf choose the way. At a masquerade, the bard would lead.

Second, I may increase the amount of information I give before I ask the players what they want to do. This decreases the number of minor, often inconsequential, choices slowing the group.

With a typical group, when the players meet a character with clues to share, or when the players enter a new location, I withhold some easy discoveries. This gives players more to learn as they talk and investigate. This rewards action and leads to a more interactive game. So if the room has a mosaic, I’ll assume someone will take a closer look. If a wizard’s apprentice reveals that the archmage sought reagents, I’ll assume the party will ask for details. For most groups, this technique leads to a better game.

But if a tentative group needs to know that the archmage intends to make a golem, then the apprentice may become chatty. And I’ll just tell a hesitant group that the mosaic shows a priestess burying a scepter under a mountain with three peaks.

I don’t welcome such adjustments. They can feel like I’m dragging a particularly halting group to the finish, but no one wants a game that lags.

Phil Vecchione notes that groups become indecisive when they lack enough information to make a choice. He suggests bridging that information gap. Start by recapping what the players already know. Players feel confused more often than they ever admit—and more than we DMs care to admit. Share any useful information that the characters may know based on their in-game expertise. The characters live in the game world; the players just visit.

As an ultimate remedy, Phil suggests upping the urgency by adding new developments in the game world. So if the party continues to dither at the door, have something open it from the other side.

Use the Small World Principle to Build a Better Game

9 Replies

Before you introduce a new non-player character to your game, seek to reuse an existing character who can fill the role.

I think of this as the Small World Principle, because I sometimes extend it beyond NPCs. Other writers call it the Law of Conservation of NPCs.

The Small World Principle brings a few benefits:

  • NPCs become more memorable and better developed because players spend more time with them.
  • The smaller number of characters creates more interaction, conflict, and drama within the cast. Drama builds rather than dissipates.
  • Game masters save the work of creating new and potentially interesting NPCs by relying on proven ones.

When I run one of the published D&D campaign adventures, I may consolidate the cast to focus on the non-player characters that I favor. Many DMs prefer to audition lots of NPCs in play and see who players fancy. Watch how players react to the characters they meet. If one sparks interest, then look for ways to expand the character’s role. See How to Make Non-Player Characters That Your Players Will Like.

The Small World Principle extends beyond NPCs. Instead of letting the game sprawl, look to circle back to existing locations.

Creators of fiction rely on the Small World Principle, even when they work on larger canvases. The Star Wars tales span a galaxy, but somehow everything happens to the Skywalkers, usually on Tatooine. In Marvel comics, almost every hero and villain lives in New York City. What are the odds? Sure, the Hulk spends time in the desert, but he seems to visit New York monthly for a team up or two. People notice the unlikeliness, but few seem overly bothered by it.

Sometimes an NPC brings some qualifications to a role, but seems disqualified for some reason. For example, perhaps the character last appeared a continent away. Or maybe they were dead. Before you conclude that the existing character won’t fit, reconsider the NPC in the part and ask, How could this be true? See Ask this question to create ideas and mysteries that grab players’ attention. Perhaps the character’s reappearance just requires a line of explanation. Perhaps it sparks a mystery that enriches the game.

Related: How to Create Loveable Non-Player Characters While You Supercharge Your Sex Appeal

The 4 Unwritten Rules No Dungeon Master Should Break

39 Replies

In Dungeons & Dragons the dungeon master gets to break the rules, but only so much. The amount of breakage varies from group to group. Some DMs stick to the rules as written, only overriding them when they defy the logic of the game world. Other DMs never track hit points and just declare monsters defeated when it suits the drama of a battle.

Despite a DM’s dominion over the rules, D&D includes some rules DMs must never break—at least if they want their players to stick with the game. Oddly, these rules never appeared in print, so successful DMs learned them by observation and insight. D&D co-creator Gary Gygax made these lessons difficult for many early DMs to learn. He set an example that seemed to encourage dungeon masters to beat players. As soon as players gained an edge, Gary created something to foil them. He and his players enjoyed the battle of wits brought by this style of play. Still, Gary just aimed to challenge players and he mostly stuck to these rules that he never wrote down.

Meanwhile, struggling DMs never deduced the unwritten rules, and often unknowingly broke them to defeat the players and to “win” D&D. Eventually, these DMs either lost all their players or they learned.

What are the dungeon master’s laws of fair play?

1. Never confront characters with threats they cannot either defeat or avoid.

The avoid part of this rule is important.

In D&D’s early days, players controlled the game’s difficulty by choosing how deep to delve into the dungeon. Certainly Gary introduced tricks aimed at luring characters deeper than they intended, but he saw such traps as avoidable tests of mapping skill. The early rules made fleeing easier and clever players knew when to run. See The Story of the Impossible Luck that Leads D&D Parties to Keep Facing Threats They Can Beat.

In today’s game, DMs more often contrive threats that the party can beat. DMs can still throw deadly, even lethal challenges, but not without giving players a warning or a way to avoid the peril. See How to Scare D&D Players—Even When They Play Mighty Heroes.

An outrageous violation of this rule appears as a living hill monster described in Booty and the Beasts, the 1979 collection of monsters and treasures co-authored by legendary D&D artist Erol Otus. Living hills look like normal, grassy hills. “They feed upon unwary travelers who camp upon their seemingly benign summits.” Campers only have a 1 in 6 chance of noticing a lost—and digested—party member. Blogger Mr. Lizard writes, “This is a perfect example of the classic ‘gotcha!’ monster. Basically, unless you actually go out of your way to check to see if you’re on a living hill, your character is dead.”

2. Assume players have taken reasonable actions.

Imagine this rule worded in a more amusing way: DMs should always assume the characters are wearing pants, even if no players said that they put them on. Obviously, this guideline exempts the anthropomorphic ducks in RuneQuest.

In the more adversarial days of D&D, some DMs insisted that players announce their intent to draw a weapon before attacking. If the battle started without weapons drawn, characters wasted a turn pulling out blades. Frustrated players took to readying weapons at every sign of danger, as if just entering a monster-infested underground death trap fell short of a sign.

3. Never let players ignorantly take a substantial risk.

We all love when players stake their characters’ lives on some reckless, nearly impossible stunt. Whether they succeed or fail, such moments make unforgettable gaming. But before any foolhardy undertaking, make sure the players know (1) the odds and (2) the result of failure. I typically share difficulty classes before players roll. These DC numbers help span the gulf between a character’s vivid sense of the game world and what a player learns from a DM’s description. DCs prevent misunderstandings.

As for risks, make sure players know that, say, falling from the Earth mote means plunging into a sea of lava. That works better than rewinding the action for a player who heard “sea” and not “lava.”

4. Never plan to take the players’ freedom or stuff to support your plot.

In the early days of D&D, some gamers coached DMs to deal with excess treasure by having thieves steal it as the characters slept. Often the caper succeeded because the players never listed the reasonable precautions they would take to protect their treasures. (See rule 2.)

Early spells like Leomund’s Secret Chest seem designed to thwart thievery, so perhaps Gary indulged in such thefts. Gary had an excuse: He invented most of the game’s magic items and wanted to test them in play. His players grew accustomed to seeing gear won, lost, and melted by fireballs. Also Gary’s players probably stole from each other—they played to win back then. See Did Dave and Gary’s Gift for Finding Fun in Dungeons & Dragons Lead Them Wrong?

None of this applies to today’s game. Never take the character’s hard-won gear. They will resent the loss.

Often DMs who steal gear aim to create a powerful hook, which leads players to chase their treasure through a campaign arc. Those good intentions may make the theft seem permissible, but those schemes only make the situation worse. Such rough hooks make players feel railroaded.

The same rules for gear also apply to the loved ones players invent for their backgrounds. Those casts count as the player’s stuff. Never kill such characters to create a cheap motivation.

The most common and egregious violation of this rule 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.

Sometimes DMs opt for capture as alternative to a total party kill. While a fair exception to this rule, don’t violate rule 1 in the process by confronting characters with a threat they cannot defeat or avoid. 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.

What unwritten rules have you spotted in D&D?