12 January 2019

PinkFae Archive #27: How to GM Part 3: Designing Your Campaign (1st of 2)

The first post of 2019; a new year, full of hope and promise, and we start off with a doozy. Today is another PinkFae Archive, but this one is a two-parter. So today, we'll have part one, and next week, we'll see part 2. This entry was first posted on 24 July 2016.

A hand holding a marker appears to be drawing a flow chart, as if designing a gaming campaign, in midair, against a background of blue cogs.

Things are looking up for you; now you've chosen a game and have a group of players willing to play it. What do you do next? The first step, obviously, is to design the overall campaign. This sounds like a daunting task, so let's look at some advice and tips on how to do that in the most effective manner possible.

Please note that this section is going to cover a lot of material. I don't want to overwhelm you, though, so I'm going to break it up into two parts. We'll do part A today, and I'll finish with part B next week.

The Point of Your Campaign

The first thing you need to do is decide on your objective. What sort of story are you telling? Are you telling a story in the usual sense? Or will it be a series of gaming sessions that have little to do with one another? There are many possible approaches you can take with this step. Here are a few considerations:
  • Character Centred: the game will focus on the PCs, who they are, how they think, what they do, and how they grow and change over the story.
  • Event Centred: the campaign will focus on the things that happen around the PCs, and how they react to those events.
  • Goal-Oriented: the campaign will have a specific objective towards which the PCs are working, and once they accomplish this ultimate task, the game will end.
  • Episodic: each session will be a self-contained unit with little connection to any other session. Character development will be incidental if it occurs at all.
These are just a couple of the possible approaches you can take towards designing your campaign. First of all, in deciding which approach to take, you should look at the types of players you have (including yourself). If the group is mostly Butt-Kickers and Power Gamers, you might want to stick with the episodic approach. However, Storytellers will likely prefer event centred or goal-oriented games. Method Actors would rather be in a game that's character-centred. And of course, you can always tweak any campaign to better appeal to a gamer type that isn't normally interested in the overall campaign type.

Story Layout

Sometimes, you'll have a specific story idea already in mind before you even begin campaign design. Here are a couple of stories I've told that influenced the type of campaign I GMed:
  • A character has a dream about the Queen of Winter giving three crystal shards to three different humans. Whoever has all three shards gains the powers of Winter. The PCs embark on a quest to find the three shards. This was a goal-oriented story.
  • Five residents of a boarding house, along with the owner of that house, go on several adventures together. This was a character-centred story.
  • Someone has turned the residents of a menehune (Polynesian 'faerie') village to stone, and the PCs must find out who did it and how to undo it. This was an event-centred story.
  • A group of mercenary-types take on missions to help people in need. This was an episodic story, although I worked in a lot of details to make it a little more of a character-centred story.
When designing a game, you won't always know what the story is when you first sit down. That's fine. You can always look at what type of campaign you're going to be running and let that guide your story-designing choices (additionally, you can always look back at my post on creativity if you need help coming up with ideas).

One of the most important things, however, is organising the story. There are five primary ways of arranging the elements of your campaign (note that these come pretty much directly from Robin's Laws of Good Gamemastering):
  • Episodic
  • Set-Piece
  • Branching
  • Puzzle Piece
  • Enemy Timeline
We're going to look at the first two methods today, and then we'll finish up with the last three in part B next week.


Stories that make up an episodic campaign have little, if anything, to do with one another. Events in one 'episode' seldom, if ever, have any impact on subsequent stories. Examples of TV shows that follow this pattern include the original Star Trek, Quantum Leap, and The A-Team. To create an episodic campaign, just come up with different encounters and don't worry about their connections. So an episodic campaign might look like this:

Players accept a job to clear all the monsters out of the caverns near the town of Daelwyn.
Players are travelling north when a band of thieves ambushes them in Deadfall Forest.
In the Kingdom of Fairwinds, the constable accuses the PCs of murdering the king's son.
Players begin travelling west to find the rumoured treasure of the wizard Yanmar.

And so on...


A set-piece is a scene that stands out from the rest of the story. It's commonly used in film-making to refer to a scene that is both important and very memorable. The Matrix is an excellent example of a set-piece story. The opening scene with Trinity fighting the police officers and the Agents leads to Neo's encounter with Agent Smith. This then leads to the scene in which he is unplugged from the Matrix. We are then led to the training scene in which Neo fights Morpheus. The plot leads us next to the fight in the corridors of the Oracle's apartment building. We then see the famous lobby scene, which is the first in a series of combat scenes. Each of these is a high point in the story, with exposition and minor actions connecting them.

In gaming, a set-piece campaign uses several major scenes connected by one of several possible transitions. In other words, if you're using this design theory, you'll come up with a number of noteworthy encounters, and find a way to get the characters from one to the next.

I used this design in my 'World of Stone' game. I sat down to create several specific scenes, and decided I wanted my players to encounter the following:
  • An aerial chase scene on bizarre steampunk contraptions.
  • A battle with an enemy in a small steampunk tank that shoots fireballs which cause volcanic eruptions.
  • A rescue scene in which one of the players' enemy kidnaps that player's adopted child.
  • An underwater fight with a shark.
I arranged the order for those scenes and came up with ways to get from one to the next. When doing this, it's always a good idea to ensure that you have at least two ways of getting from scene to scene. A good plan is to have one way if the characters are successful in the current scene, and another way if they fail. So I mapped out the story like this:

In investigating the petrified village, the PCs come to a warehouse filled with strange devices. A pig-man is inside, and tries to escape in a steampunk ornithopter. The players must chase him using a hovercraft that looks like a giant fan.
Success: The pig-man tells them they can find his boss under water. Failure: The players find one of the pig-man's possessions and use a divination spell to learn that his boss is under water.
The players start swimming around off the shore of the island looking for an underwater base. One PC has a mentor who is a selkie; a passing shark attacks this mentor.
Success: The players fight off the shark, but learn that the mentor was really a merman using an illusion disguise to hide the fact that he was banished from the undersea kingdoms. Failure: the mentor dies.
The political rival of one of the characters kidnaps the PC's ward. The players must suspend their search for the pig-man's boss to rescue the little girl.
Success: The girl is rescued and the rival is punished. He reveals that the pig-man's boss is delusional, and sees a floating lake above her house; the 'underwater' base is actually under this illusory lake. Failure: The players rescue the girl, but the rival escapes. The girl knows about the hallucinatory lake, but doesn't realise that knowledge is important until later.
The PCs head towards the villain's hideout, but just as they arrive, the villain launches an attack with the volcano tank.

In this example, you'll see that failure doesn't prevent the characters from moving to the next scene. It might make it a little harder, because they have to do more work, or find necessary information in a less direct manner. But it doesn't make it impossible. That spoils the fun!


Ok, that's probably enough. We'll finish this article next week. Until then, have fun writing stories and playing games. Most importantly, of course, you should always remember to

Game on!

No comments:

Post a Comment

I'll be along soon to make sure your comment isn't spam. Until then, just sit tight! Unless your comment IS spam, in which case, bugger off.