Showing posts with label ways to run a role playing game. Show all posts
Showing posts with label ways to run a role playing game. Show all posts

Tuesday, June 28, 2011

Decision Matrix for Games With Many Players

At a recent Pathfinder session, a friend introduced me to a mechanic to aid players in making difficult or complex plans. If your players run across a situation that requires them to chose one among a handful of options and there is differing opinion as to which is the best, you may find this "decision matrix" works well for you.

Advantages include being impartial and democratic, revealing the group's general consensus out of individual responses to simple questions, uninfluenced by input from others. In groups of more than four players, this decision matrix can be especially helpful in streamlining decision making.

The main disadvantage is speed. The decision matrix does take a bit of time to get through, and the more players, the slower it works.

Step 1: Determine the choices at hand. The players know what their goals are, and the dispute should be over the route to achieve those goals. This step takes two parts: identify important factors and identify main choices. Important factors are things like party safety vs. party speed, factors that have to be juggled. Main choices are things like which route to take toward an objective or which approach to use when striking down an unknown foe just over the next hill.

Step 2: List both factors and choices. Write them down on a piece of paper such that they form a grid, which factors down one side and choices along the top.

Step 3: Interview the players. Go around the circle of players and ask each to individually answer. Forbid other players from interfering. Ask each player for their vote on the best course of action for each given factor, and on the second best.

Step 4: Tally the results. The majority decision should be visible. If there is a tie, repeat the process with only those choices that were tied, and ask only for the top choice from each player.

Example:
The players are investigating a mysterious island. They know from earlier reconnissance that there is a supposedly abandoned town on the island's far side that is now active with people, and that the woods between their current location and the town are filled with hostile creatures. They do not know if the people in the town are friends or foes, but they do know that there is a large and dangerous disturbance in a crater southeast of the town. The players cannot reach a group decision after several minutes of decision, so the GM decides to try using the decision matrix method.

She talks with the players and determines that they all agree that all of the following factors are important:
1. The safety of the group.
2. The speed with which they can reach the town in order to warn potentially innocent people of their danger.

There are three possible routes to take to the town:
1. Using the road that leads over the island to the town.
2. Using the most direct overland route through the woods.
3. Sailing the characters' ship around the island to a reef-free bay within sight of the town.

She begins asking each player the following questions:
"Which of the three routes do you think is the safest? Which is the next safest?"
"Which of the three routes do you think is the fastest? Which is the next fastest?"

She begins to tally the answers, asking each player in turn. In the end, she adds up the tallies and determines that the group's general consensus lies with taking the ship around the island. This will sacrifice a good deal of speed, but is much safer than the danger of the woods or the lack of cover on the road.

I hope this helps you to resolve disputes about the next course of action the next time you have a game with a lot of players.

Thursday, April 14, 2011

I love to run non-standard versions of games. It gives me a chance to personalize an established setting to better reflect the kinds of stories I like to tell with my players. But on a more practical level, it really broadens the spectrum of games I find myself interested in trying out. I'll confess right now that I never met a RPG I fully liked as-presented. Usually there's some small aspect of it that I wish were different, and the beauty of being the game master is, of course, you can change anything you want to suit your needs. After almost a decade of running games, I've noticed there are five general ways I tweak a game in order to make it more interesting. I invite you to try using one of these techniques as a way to experiment with a game you might otherwise not run.

From least amount of work prior to starting a campaign to most, they are:

1. Emphasize Elements You Like: Read through whatever the core book of the game or campaign setting is and note all the phrases and ideas that grab you the most. If you're into lists like I am, you may even want to prioritize yours once you're done so you know what the top handful of ideas are. Then design your campaign in order to explore those elements and ideas in-depth.

Example: In the Forgotten Realms campaign setting for Dungeons and Dragons, magic is caught up in something called the Weave. This is the most interesting aspect of the setting for me, so if I were to run a Forgotten Realms game, I would most likely make it a spellcaster-focused campaign in order to explore the history and ramifications of the Weave. Where did it come from? How many different ways can you use it? How would the rise of Renaissance-like ideas about science and technology impact it?

2. Play With the Mythos: "Mythos" refers to the game's story backbone - the big picture history of the game world, all the assumptions about how the game world came to be the way it is and where it's going. By adjusting specific "facts" within the game mythos, you can come up with an entirely different form of the game that's still recognizable.

Example: In Mage: The Awakening, the mythos states that mages can use magic because their souls are "awakened" to the true nature of reality as something supernatural and that they all inheret the legacy of the ancient fallen civilization of Atlantis. As a variant, I decided that, instead, mages could use magic because they are the descendants of humans crossed with dragons, and that it was the trace of dragon blood that "awakened" a mage. Atlantis was the place where dragons once ruled, until they were overthrown, causing Atlantis to fall. This had ramifications for who the various Orders were and what the different Paths represented. The Exarchs became the Old Wyrms - the surviving dragons seeking to reestablish dominion over the world, and the Oracles that established the various Watchtowers existed to thwart their plans.

3. Play in a Mirror Universe: A classic trope of science fiction is one that lands the heroes in a mirror universe where everything is the moral opposite of their own. All the "bad guys" are the "good guys" and vice versa. Sometimes it makes for a more interesting game to switch the "good" and "bad" sides in the game and trying to justify it with an altered game mythos.

Example: What if, in the Star Wars universe, the Sith were the good minority within a corrupt Jedi order? What if the Dark Side of the Force was aligned with freedom and self-determination through the expression of passion and aggression, pitted against another side that was more interested in a kind of galactic fascism in which were trying to turn everyone into the docile, accepting followers of a corrupt elite?

4. Play In a Different Period: Every game world mirrors some slice of human history. Some times it's fun and exciting to set a standard game in a non-standard time period. A word of caution - make sure the historical backdrop is just a backdrop. It's there for flavor. If you start to worry about historical accuracy, then the setting becomes the star of the show, not the players.

Example: Think of Pathfinder set in the Wild West, or Call of Cthulhu set in Middle Ages Europe.

5. Tweak the Rules: This is the trickiest to pull off. But sometimes you love a game but hate the game's core rules, or at least some aspect of them. If you feel experienced enough, tweak the rules with a big house rule that you make clear to your players before the campaign starts. If not, it might be best to just borrow from a set of core rules you DO like.

Example: Adjust the core die mechanic for GURPS so it works more like the d10 pool system of World of Darkness. Both are point-buy systems, but if you feel the d10 system is more elegant, why not use it instead?

Monday, April 4, 2011

Advice When Running an Intrigue RPG

If you've ever considered running an RPG based on intrigue rather than combat, here are some points to keep in mind.

What is an intrigue game? "Intrigue" refers to any genre of game you plan to run where the dangers, challenges and plots are all socially-based rather than action-based. Certainly, there will still be some fighting or at least backstabbing in the dark of night. But intrigue RPGs are all about politics and the lure of power mixed with the danger of murder and the scent of a good old-fashioned mystery.

To run a good intrigue game, I suggest these five pieces of advice:

1. Chart Your Tangled Web: As the one running the game, you know all the plot twists and dirty secrets. For myself, I find that having an actual map that details the relationships between PCs and NPCs helps me to keep the whole political landscape clear and consistant from session to session.

2. Focus on Character Desires: Goals may shift from session to session the way strategies in a chess game shift. But what each character - player or non-player - wants should ideally remain the same. As long as you stay clear and focused on what NPCs want overall, you can generally do a good job of adapting their goals to changing situations.

3. Use Memorable Characters: Intrigue games are character-focused morso than action games. Distinctive NPCs with distinctive names will help players remember and tell them apart, and will help you do the same.

4. Give Clues Socially: Most clues to any given mystery, situation, or NPC's true motives should be given through social game play, with a scattering of investigative work. But intrigue games are really about that fatal slip of the tongue that tips off an enemy moreso than about hunting down fingerprints. Weave hints and clues into NPC-to-PC conversations or into overheard NPC-to-NPC conversations that you've scripted out. If you do it right, you give your PCs that proverbial trail of breadcrumbs they can follow deeper into the game's plot.

5. No Red Herrings: Intrigue games are hard enough to keep track of without PCs constantly worrying about their clues checking out. I don't mean you can't have your NPCs lie. Far from it. But giving the PCs what seem to be important information only to have them find out they really didn't need to know it can get very frustrating. So be nice, and have any major clues you slip in be the truth of the matter.

6. Pay Attention During Player-to-Player Discussions: Chances are, they'll come up with some sort of theory about what's really going on, and it's not uncommon for some plot twist or hypothesis they come up with being better than what you'd planned. So why not run with their suggestions? They'll never know they're actually the ones creating the plot of their own game.

If you want more detailed advice on running this type of game, I recommend the World of Darkness - Vampire: The Requiem supplement Damnation City. Specifically, pgs. 208-225. Their advice is largely plot-based, not systems based, so you can modify it to fit any game system you're using.

Tuesday, March 29, 2011

Styles of GMing That Cut Preperation Time

This article is about different ways you can run a role-playing game. Different "styles," if you like. These styles are slightly different than the standard "prepare all the statistics beforehand and hope the players don't do anything unexpected." They're all designed to cut down on GM indecision when it comes to what happens next in a given session. I've put them here on a continuum from lowest to highest preparation time.

"No GM" Style Gaming
Works Best For: GMs who run out of time to prepare for a session.

How It Works: This is inspired by the Mythic Game Master Emulator. All you have to do as the GM is decide how likely or unlikely it is that a player's question has a "yes" for an answer. All questions in the game are broken down into "yes or no" questions and you roll a d100 to see whether the outcome is true, false, very true or very false. The likelihood of something being true vs. false is set by the GM, given the circumstances.

No Chance 20/80
Highly Unlikely 30/70
Unlikely 40/60
Equal Chance - 50/50
Likely 60/40
Very Likely 70/30
Obvious/ Sure Thing 80/20
Exceptional: A roll of 90-100 is an exceptional. A roll of 0-10 is an exceptional.

Benefits: No or minimal prep time needed. You just sit down with a premise for the session and a plot hook and away you go.

Drawbacks: It can get tedious to try and break everything down into yes and no questions. Combat can be especially tricky.

Tips: You should probably track when someone with a certain level of combat skill scores a hit, since another person scoring a hit with a similar roll would be almost certain to also hit. It might also be a good idea to instead roll up at least the combat NPCs ahead of time. At the very least, you should decide how many "Yes" hits an enemy can receive vs "Exceptional Yes" hits before they're killed, and adjust this according to the combat skills of the various PCs. Also, try to be a little more interesting in your interpretation of the results than just a "Yes" or a "No." Make the answers detailed. ("Do I find a key?" "Yes, you find an old iron key with a curious handle lying amid the rubble.")

Freeform Fudging
Works Best For: Games that don't have a set difficulty number to beat on a roll, games without "rules lawyers," games that are based around stories and plot rather than combat and skills.

How It Works: Forget stats and rules when writing up your sessions. Just write out the plot and the events to run the players through. When the dice start rolling, you fudge. You make it up. You look at what the players have rolled and if it's reasonably high, they succeed. If it's obviously low or bad, they fail. If it's in the middle, decide what would play out most dramatically for the story and make a note of what exact numbers were rolled so that your rulings appear consistent enough to avoid suspicion.

Benefits: Takes a lot of the headache about of game preparation and lets you focus on the fun, storytelling aspects of GMing instead of turning it into one long math assignment. You can be ready to run a game in hours or even less time rather than days.

Drawbacks: Combat is really tricky using this method. You don't have any actual stats for your enemies, so it becomes crucial to know as much as possible about the PC's stats. If players think you're "cheating" in combat, I wash my hands of what their reaction might be.

Tips: Notes, notes, notes! Write down everything. Write down what number was rolled, what it was for, what the outcome was, who rolled it. Keep notes on which PCs are best at doing what so you can reward them for the time they put into bothering with statistics that you didn't! With luck, they'll never know you didn't have any actual enemy stats.

Modular Encounters
Works Best For: Site-based sessions. The session takes place within a single area or location. Also works best for providing a maximum variety of challenges during a given session.

How It Works:  Gather together all the possible individual encounters you might want to throw at your players - enemies, traps, puzzles, clues, everything. But don't tie them to any specific event or location. Think of each as an "element" and imagine it's on a playing card that you can slap down to activate during the game. You might even want to use some sort of cards if you feel it would help. You throw them their first challenge and watch the moods and reactions of the players. You decide what tone and pace the session takes by which challenges you activate and how often to use them in the same way a DJ decides the tone, pace and mood of a dance by what songs are played.

Benefits: Gives you maximum flexibility with regard to the shifting moods of the players. If they look like they're thirsty for a fight, they can have one. Too much combat? Throw them a few environmental hazards or puzzles instead. Players feel the session is getting predictable? Throw down a general plot twist you've written up and interpret it according to what's currently going on in the game. 

Drawbacks: You might feel a lot of your prep work was wasted time if you don't use half the things you created for potential use during a given session.

Tips: Keep unused "elements" and reuse them in later sessions with minor adjustments to make them context appropriate. Remember - all the players see is a baby dragon. They don't have to know the stats are actually those of a goblin they never encountered during the last game.

Choose Your Own Adventure Flowchart
Works Best For: Event-based sessions. The session is following a specific plot outline or series of events rather than all taking place at a single location. Over the long term, this model can be used to plan whole campaign arcs that shift depending on the pattern of the player's choices.

How It Works: Every player action can be broken down into one of five basic categories: Combat, Dishonest, Search, Socialize, Spells. Your job is to create five appropriate reactions to player actions for each encounter in the session. Then, when the players react to those reactions, it leads to the next encounter in the sequence, and so on.
Combat: Any action that is physically aggressive or leads to a fight. Might also include non-violent contests.
Dishonest: Sneaking, spying, attempting to lie or disguise, trying to poison or other devious acts.
Search: Any investigative act from looking for clues or traps to interrogating an NPC for information.
Socialize: Any action that is a social action. Engaging NPCs in conversation, giving a performance, etc.
Spells: A player tries to use one of their super-human abilities, magic, powers or technology.

Benefits: You always have a pre-planned response to all but the craziest player actions. It frees you up to focus on rules interpretation and combat rather than scrambling to respond to unexpected player actions.

Drawbacks: If you aren't careful, the branches of possible outcomes will spiral exponentially out of control. This technique is tricky to implement for large-scale sessions, such as sessions that take place with a complex plot line or a lot of different characters.

Tips: Give players the illusion of choice. When it comes to a key clue or scene or encounter, make sure that all possible actions lead to a variation on the same result. This will keep the branching possible outcomes form getting out of control.

Sandbox
Works Best For:  Site-based sessions, that all take place in the same location or area. Or for GMs who like to give a very realistic portrayal of a living, independent world around the PCs. Also works well for running a session that's based around solving a crime.

How It Works: You break the session into specific sites and keep careful track of the passage of in-game time during the session. Each site will have a time-specific description written for it, so that the players can go anywhere in the game world and have a unique encounter wherever they go. Your NPCs will have their own agendas and actions, all run by the timer and modified as needed based on the player's actions. Even things like the change in weather can be tracked. Think of it as a series of miniatures plays all going on at different stages. Your notes are the script for each play.
Example: The PCs are going to enter a villager of 4 houses. Divide these into Sites A-D.  The basic plot is that a menage a trois between a former lover and a lady's husband leads to the murder of the village priest.
Site A: Mother's House:
8 AM: Mother wakes up and bathes.
9AM: Mother does dishes and cleans.
10AM: Mother leaves to visit Priest, discovering him dead at 10:15.

Site B: Father's House
8 AM: Father wakes up, shaves, bathes, cooks.
9AM: Father eats breakfast.
10 AM: Father leaves house for fields.

Site C: Priest's House
8 AM: Priest awakens and begins morning prayers.
9 AM: Villain enters. Priest has a long argument with Villain.
10 AM: Priest is murdered. Villain flees

Site D: Villain's House
8 AM: Villain wakes up and eats breakfast.
9 AM: Villain is absent, gone to the Priest's house. He leaves for the Priests at 8:55 AM.
10 AM: Villain is absent, gone to the Priest's house for the first 10 minutes. Then returns here.

Weather:
8 AM: Predawn. Foggy. Chilly
9 AM: Dawn. Clearing, birdsong.
10 AM: Morning. Becoming overcast. Distant thunder.

Benefits: It can be greatly rewarding to have such a "God like" perspective of everything going on and be able to watch your players explore and discover and piece together the plots in the world around them. You'll easily be able to give vivid descriptions, even of the individuals that pass on the street. The players will definitely get the sense that they are in a real place, where things are happening even if they don't see them happening (because they actually are theoretically happening!)

Drawbacks: All it takes is a little bit of unanticipated mayhem from the players and you can be left scrambling to put your beautiful little web back together. It can be a real headache and a game-slower if you're not used to major multitasking or if you're running a very large location with multiple sites. In addition, players might become caught up in more than one subplot and not realize the two are totally unrelated. This can lead to a sense of frustration and betrayal if your players are the type who have no patience for mysteries or intrigue. Finally, players might become frustrated if they keep missing encounters by a matter of minutes and all they see is a bunch of unknown people walking around and empty rooms with nothing going on.

Tips: You'll have to fudge artistically to keep things moving. If the players are 'early' or 'late' to a place, adjust the clock a bit. Leave plenty of clues to guide them and help them sort out what's important from what's not. Take a look at how video game dialogue and cut scenes guide the player from goal to goal. Finally, if the players get way ahead of a major consequence to their actions and you're afraid they might get too reckless or even forget about what they've done because they don't see any obvious consequences within a few days of the act, then fudge realism and confront them with appropriate consequences as a cliffhanger to the next session.