- Gnome Stew - http://www.gnomestew.com -
Use PC Backgrounds as a Roadmap for Campaign Design
Posted By Martin Ralya On January 18, 2010 @ 2:32 am In GMing Advice | 9 Comments
I’m a big proponent of using everything my players give me, especially when it comes to PC backgrounds: If you put it in there, I assume it’s because you want to see it in the game, and I’ll do my best to make that happen.
But why assume?
As a player, I design character backgrounds this way. I include NPCs my PC would love to fight, fuck, or otherwise interact with; I build conflict into my characters’ pasts, and leave big, juicy pointers to future conflict. And I assume my GM will make the most of it.
But again, why assume?
The GM in one of my group’s two current games (both 4e D&D, oddly enough), Don, did something really cool with regard to pre-campaign prep: he asked each of us to send him a list of three things we wanted to see in the game.
Here’s my list:
1. The big one, from my background (where it has its own section): return to Damara, stop the Warlock Knights from invading, and reclaim the honor of my clan. That’s more than one thing, I suppose, but it’s Dox’s overriding character goal. The whole hammer thing is part of this, too — if Dox does good, the hammer recovers its magic. This sounds like something for later levels, which I think makes sense in-character — Dox knows he can’t do this yet.
2. Rebuild the Seven Swords. This is Dox’s new family, and honor demands that he clear this family’s name, too. The two real ex-Swords he’s met have been nothing but good to him, and he has a lot to prove. That said, this is likely our main campaign goal, so I’ll give you two more.
3. I’d like to take part in a siege as the besieged. I’ve never done this in D&D, and I love the concept. To get around the time constraints — since a traditional siege would take awhile — it would be fun to be the elite team tasked with sneaking through the cordon and bringing back the siege-breaking macguffin, which sounds much more like one or two adventures.
4. Something more appropriate to the heroic tier: I’d love to play a classic rooftop battle — chasing or being chased across the rooftops of a city, perhaps Waterdeep. (This might be a fun one to work a skill challenge into.) Moonlit night, skidding perilously close to the edges of roofs, coming up on trouble too fast to react to it — the whole nine yards.
And as the game has progressed, he’s worked them into our adventures: we just had our rooftop chase, and my hammer has been slowly improving. Ditto for the other players’ requests. It rocks, and it got me thinking: Why not combine this approach with my fuzzy philosophy about making the most of PC backgrounds?
That should take the assumptions and guesswork out of both sides of the equation, and when you have limited time to game that’s always a good thing.
This is a simple idea:
Systematize the connection between PC backgrounds and actual gameplay by asking your players to focus their backgrounds on what they want to do, not what they did before the start of the campaign.
There’s nothing wrong with having a robust backstory (mine usually run about 10 pages…), but a backstory that has no impact on the game is about as useful as conjugating verb tenses for orcish dialects — if it never hits the table, who gives a flying fuck? Not me — not as a player, and not as a GM.
Get on the same page: For this technique to work, you and your players need to be on the same page about what kind of campaign you’ll be playing. “It’s kind of like Star Wars” isn’t a bad start, but it’s not enough. (Which era? Which movie? Are we all Jedi, or Ewoks? Can we shoot Gungans on sight?)
Create characters as a group: You don’t need to go from zero to a fully fleshed-out party together, but at a minimum you’ll need to have an idea of what everyone else will be playing. (For tips, try this free PDF: More is Better: Group Character Creation.)
Write your character background however you like: Why reinvent the wheel? Just have fun writing your background the way you always do — the key step comes next. One exception: If your backgrounds always say “My guy is named Bob,” you’re going to need to do more than you usually do.
Turn that background into a roadmap: Once you have a background, look for hooks that point to fun encounters, storylines, recurring villains, or other campaign elements. (Having experience as a GM and a player helps a lot here.)
Then, transform those hooks into action items for your GM — things you want to see in the game — and ask for them explicitly. Don’t beat around the bush: just say “I want to do/see X.” Here are four examples based on the PC featured above:
Avoid writing the campaign: Take a look at my examples: none of them dictate the course of the campaign — though they all point to elements that could become major features of the campaign, if my GM wants them to be. The goal isn’t to hog the spotlight, it’s to contribute elements that will be fun for you, for your fellow players, and for the GM.
As a GM, I’d love to see this kind of roadmap from each of my players. There might be things I couldn’t work in, but even those would be great inspiration — and it’s entirely possible that I’d be able to craft an entire campaign just around the conjunction of the PCs’ roadmaps.
What do you think of the background roadmap technique? Have you used something similar? Will you be trying it in your next campaign (or even your current one)?
Article printed from Gnome Stew: http://www.gnomestew.com
URL to article: http://www.gnomestew.com/gming-advice/use-pc-backgrounds-as-a-roadmap-for-campaign-design/
All articles copyright by their individual authors. All rights reserved.