Tag Archives: improvisation

The No-Prep Way to Use Character Backstory In a Campaign

4 Replies

When dungeon masters connect the characters’ backstories to their campaign, the game feels more personal to players. Revisiting a backstory shines a spotlight on a character and includes them in a way that highlights a character’s unique importance to the campaign. Through character backstory, players contribute to the campaign world. Using that backstory in the game recognizes the value of the player’s creative contribution. That recognition feels great.

But the Dungeons & Dragons rulebooks include no advice for dungeon masters aiming to use these backstories in play. I’m here to help.

The easiest method for pulling a backstory into a D&D game follows the techniques of another type of real-time, collaborative storytelling: improv theater. “The first rule of improvisation is AGREE. Always agree and SAY YES,” Tina Fey writes in Bossypants. “When you’re improvising, this means you are required to agree with whatever your partner has created. So if we’re improvising and I say, ‘Freeze, I have a gun,’ and you say, ‘That’s not a gun. It’s your finger. You’re pointing your finger at me,’ our improvised scene has ground to a halt.”

Improv’s “Yes and…” principle enables DMs and players to work together to bring character backstory into scenes. Suppose the party visited Waterdeep and you, as DM, wanted to use something from a character’s backstory to draw them in. If a character’s backstory included a history as a gambler wandering from town to town, fleeing angry marks and gambling debts, then the scene might start like this.

DM: Zand, have you ever gambled in Waterdeep?

Zand’s player: Yes, and I’m keeping my eyes open for… (looks at hands) …Knuckles. I owe him.

DM: As luck would have it, you spot Knuckles going across a crowded market square. He looks your way.

Zand’s player: I walk to Knuckles and say, “Hello friend, I have an irresistible opportunity that will pay you back for what I owe.”

Sometimes players can contribute backstory to suit a scene without much improvisation, because they imagined more of their characters’ histories than the DM knows or remembers.

“Yes and…” builds creatively. The scene and the game moves forward instead of getting stuck finding agreement. Second City explains, “The basic concept of these two words is that you are up for anything, and will go along with whatever gets thrown your way.”

Unlike performers in an improv scene, players don’t need to be up for anything. When a DM elaborates on a character’s backstory to fit the campaign, the additions might not fit the player’s vision. In a game, players invest time and imagination in their characters, so they deserve to keep control of their proxies. Players can always pause the game and explain that a bit of invented backstory doesn’t match their vision.

This sort of spontaneous addition of character backstory resembles another technique where the DM has the players contribute to the world-building during a session. Examples range from asking the players to invent a distinguishing feature for a monster to having players describe the folks in the inn. That practice can become a jarring reminder that the characters live in a made-up world without any truth. Inventing or recalling backstory feels more comfortable because players feel accustomed to imagining that part of the story. The DM asks questions and the characters know the answers, even if the players have to dream up the details.

Of course just a few actors and storytellers understand this sort of in-game collaboration. Sometimes such offers stumble. The DM says, “As you eat your meal, someone you recognize from your battalion walks in. Which one grew up here?” And then the player locks up. I don’t remember anything about that, the player thinks. What do you want from me? You can nudge the scene along by spelling out the offer. “Would you like to expand on your character’s backstory by telling me the name of someone you fought beside in the last war? What do you remember about them?”

When the technique works, it feels like creative magic—the best case for connecting backstory to the game in progress.

Related:

Next: More on bringing backstory into campaigns.

Improve Roleplaying Investigation Scenes With These 23 Reasons an NPC Won’t Cooperate

3 Replies

Roleplaying scenes prove most compelling when players start with a goal and face an obstacle to overcome. Even encounters with the most vivid and fascinating non-player characters fall flat without these two essential elements. When characters lack a goal and a dungeon master launches a role-playing scene anyway, players wind up wondering they are supposed to do. When a scene lacks an obstacle, it bores. (See How to Use Scenes and Summaries to Focus on the Best Parts of a Role-Playing Adventure and Avoiding the Awkward D&D Moment When a Priest, a Wizard, and a Dwarf Enter a Bar and Nothing Happens.) So as a DM, when a roleplaying scene lacks a goal and an obstacle, either summarize the scene and move on, or add the goal or obstacle that the scene needs.

Typically, roleplaying encounters combine an objective of gaining information or help, with the obstacle of an uncooperative non-player character.

Sometimes the players simply try to persuade the NPC, succeed at a diplomacy check, and move on, but if every interaction amounts to a skill roll, the game loses interest. At times the bard’s honeyed words may overcome any objections; at times an NPC faces conflicts or repercussions that require action.

Just as the puzzles in a Dungeons & Dragons game have solutions, and locked doors have keys, NPCs can have keys of a sort too. Every NPC who stands unwilling to cooperate must have a reason for it. To unlock the NPC’s help, players must find ways to defuse or overcome the NPC’s objections.

If an NPC enters an interaction with a reason not to help the players, you should ultimately give the players enough clues to find a way past the objection.

The NPC may reveal the reason, but sometimes the players may need to figure it out for themselves. The key might not even be apparent on first meeting. If players learn something about a character that helps in a later meeting, then the world feels richer, the NPCs more vibrant, and the players cleverer.

To spark ideas and aid with improvisation, I created a list of potential reasons an NPC might have for refusing to cooperate with the player characters. Low-numbered items work best for ad-libbed objections from walk-on characters; they require less planning and fewer details about the NPC. Higher-numbered items work better when you have time to plan for your adventure’s most important NPCs.

Reasons non-player characters refuse to cooperate.

d100 Reason
01-05 Doesn’t want to get involved.
06-08 Doesn’t like your type. I recommend avoiding racism analogs in D&D games, so don’t select even a fantasy race or lineage as a type. Instead, choose a role like bards, adventurers, or meddling kids.
09-13 Doesn’t believe anyone can help.
14-19 Thinks the players will only make things worse and should leave well enough alone.
20-27 Wants something: a bribe, an errand done, or to be convinced that they stand to gain if the players succeed.
28-31 Was paid to keep silent or to stay out.
32-36 Insulted or offended by the players.
37-40 Thinks the players efforts are dangerous because they don’t understand what’s really going on. The NPC might know something the players don’t.
41-43 The players have unwittingly caused the NPC to suffer a loss.
44-46 Feels that helping the players will betray the NPC’s duties or obligations.
47-51 Needs more information to support the players case.
52-54 Knows or suspects that either the NPC or the players are watched.
55-57 Told not to help by someone the the NPC loves or respects.
58-60 Told not to cooperate by an authority.
61-65 Secretly involved with the other side.
66-70 The situation benefits the NPC, for example, by raising the value of the NPC’s trade goods, or by hurting competitors or rivals.
71-74 Fears the players might claim a treasure or reward that the NPC expects to get.
75-77 Is allied with rivals or competitors to the party.
78-82 Has been threatened.
83-87 Someone the NPC loves is threatened.
88-92 Someone the NPC loves is involved with the other side.
93-97 Not involved but might be implicated, perhaps for doing things that once seemed innocent.
98-00 Blackmailed for a misdeed unrelated to the players’ concerns.

When you play an uncooperative NPC, remember that the NPC may seem helpful. An uncooperative NPC can say all the right things while they lie or let the players down.

Still, I suggest feeding the players lies only when the deception leads to a new development. Lies that lead to false leads and dead ends will prove frustrating and un-fun. For example, the countess can lie and say than her hated rival stole the broach, but then the rival must reveal a new piece to a puzzle, perhaps a secret that the countess fought to hide.

22 Reasons why a non-player character won’t cooperate

2 Replies

In “a priest, a warlock, and a dwarf walk into a bar and…nothing happens,” I wrote about how most players only find role-playing encounters compelling when they have a objective to achieve and an obstacle to overcome. Even encounters with the most vivid and fascinating non-player characters fall flat without these two essential elements.

Typically, role-playing encounters combine an objective of gaining information or help, with the obstacle of an uncooperative NPC.

Sometimes the players simply try to persuade the NPC, succeed at a diplomacy check, and move on, but if every interaction amounts to a skill roll, the game loses interest.  At times the bard’s honeyed words may overcome any objections; at times an NPC faces conflicts or repercussions that require action.

I suggest an approach to role-playing encounters that yields more challenging and interesting encounters, along with more memorable NPCs.

Just as the puzzles in a Dungeons & Dragons game have solutions, and locked doors have keys, NPCs can have keys of a sort too. Every NPC who stands unwilling to cooperate must have a reason for it. To unlock the NPC’s help, players must find ways to defuse or overcome their objectives.

If an NPC enters an interaction with a reason not to help the players, you should ultimately give the players enough clues to find a way past the objection.

The NPC may reveal the reason, but sometimes the players may need to figure it out for themselves. The key might not even be apparent on first meeting. If players learn something about a character that helps in a later meeting, then the world feels richer, the NPCs more vibrant, and the players cleverer.

To spark ideas and aid with improvisation, I created a list of potential reasons an NPC might have for refusing to cooperate with the player characters.  Low-numbered items work best for ad-libbed objections from walk-on characters; they require less planning and fewer details about the NPC. Higher-numbered items work better when you have time to plan for your adventure’s most important NPCs.

Reasons a non-player character refuses to cooperate.

  1. She doesn’t want to get involved.
  2. He doesn’t like your kind, for example, strangers, elves, adventurers, or meddling kids.
  3. She doesn’t believe she can help.
  4. He thinks the players will only make things worse. They should leave well enough alone.
  5. She wants something: a bribe, an errand done, or to be convinced that she stands to gain if the players succeed.
  6. He has been paid to keep silent or to stay out.
  7. The players have insulted or offended her.
  8. He thinks the players efforts are dangerous because they don’t understand what’s really going on. He might know something the players don’t or he may simply know less than he thinks.
  9. The players have unwittingly  caused her to suffer a loss.
  10. She feels that helping the players will betray her duties or obligations.
  11. He needs more information to support the players case before he can act.
  12. She knows or suspects that she or the players are watched.
  13. Someone he loves or respects told him not to help.
  14. She is secretly involved with the other side.
  15. The situation benefits her, for example, by raising the value of her trade goods, or by hurting competitors or rivals.
  16. She fears the players might claim a treasure or reward that she expects to get.
  17. He is allied with rivals or competitors to the party.
  18. She’s been threatened.
  19. Someone she loves safety is threatened.
  20. Someone he loves is involved with the other side.
  21. He’s not involved but might be implicated, perhaps for doing things that once seemed innocent.
  22. He’s being blackmailed for a misdeed unrelated to the players’ concerns.

When you play an uncooperative NPC, remember that the NPC may seem helpful. An uncooperative NPC can say all the right things while they lie or let the players down.

Still, I suggest feeding the players lies only when the deception leads to a new development. Lies that lead to false leads and dead ends will prove frustrating and unfun. For example, the countess can lie and say than her hated rival stole the broach, but then the rival must reveal a new piece to a puzzle, perhaps a secret that the countess fought to hide.