Monday, June 30, 2014

Not every game problem can be solved with game mechanics

I think board game designers would learn a lot from playing a few rounds of Fiasco.

Fiasco is a story-focused one-session roleplaying game, in which you collaboratively tell a story about a wacky heist gone bad. In various sessions I've been a tea importer who dressed up as a mall Santa to destroy my competition, a cat who tried to convince the other cats to start a nuclear war with Russia, and a severed hand trying to stop my brother's clones from winning a bowling competition.

The key thing about Fiasco is that there is no win condition. By the rules, no individual can lose, nor can the group as a whole lose. Certainly there are end conditions, which determine whether your character's life turns out good or bad at the end of the story -- but it would be dysfunctional and counterproductive to the game for someone to treat those as "win conditions," organizing their approach to playing the game around achieving a specific sort of ending for their character. The rules of the game exist to support a group of people in doing something fun together.

Too often, I think that board game designers become fixated on the mechanical aspects of games. Don't get me wrong -- having solid mechanics in a game is essential. It's important to think about what kind of strategies your mechanics make possible and reward, and to adjust them if they produce dysfunctional results. But there's a limit to how much game mechanics can do. Not every problem in a game can be solved through game mechanics. If we get fixated on the idea that any undesirable strategy must be prevented or severely disincentivized within the mechanics of the game, we can lose sight of the larger picture.

A classic example of this issue is the problem of "captaining" in cooperative games -- the phenomenon of one player taking over and directing other players' moves, creating an essentially solitaire game. There are some cooperative games that inherently rule out captaining, as a natural consequence of their core gameplay (Hanabi does this beautifully). Others tack on rules to try to exclude captaining by fiat (e.g. forbidding players to explicitly name the cards in their hand, as in Shadows Over Camelot). But I've had an enjoyable time playing actual solitaire games of Pandemic and Forbidden Island -- something that would be impossible if they were mechanically captain-proofed. And I've had fun playing them with people I trusted not to captain, in social contexts that discouraged captaining. We didn't need something in the rules to force us to play nice.

Different groups will play the same game in different ways. The designer can't, and shouldn't, exercise complete control over the gameplay experience. A big part of playing most games is the informal social negotiation that occurs around the question of which strategies are legal but jerky. For example, in a recent game of Keyflower, we agreed that while it was legal to win two turn-order tiles (thus getting two ships and leaving another player with none), that it was kind of a jerk move and would be treated as such. When one player proceeded to bid on two turn order tiles, the rest of us stepped up to stop him, even when it might not have been a strictly optimal move in terms of maximizing personal victory points. We were all invested in maintaining the spirit of the game. (I should add that the person bidding on multiple turn order tiles wasn't doing it to be a jerk -- the move was taken, in context, as a sort of teasing.)

Bringing this back to Fiasco, someone could be a jerk in Fiasco. They could refuse to go along with the story, they could nitpick the allocation of white and black dice at the ends of scenes, or they could simply "check out" during the game. I've had all these things happen, and they make the game less fun. There's nothing in the rules that prohibits this kind of behavior.

The overarching goal in playing a game -- even more than racking up victory points -- is having fun together. And no game mechanic can guarantee success at that.

Monday, June 16, 2014

Updated Fiasco: You Are A Cat playset

I finally figured out the correct fonts and made a cool cover image for You Are A Cat, my Fiasco playset about being a cat. Download it here!

Monday, May 19, 2014

Game Chef 2014: Spy Party

A hand with red nails holds a bottle of nail polish bearing a hammer and sickle, with the text SPY PARTY

This year I decided to take a shot at Game Chef, a 10-day game design contest. This year the theme was "there is no book," and the ingredients (of which 2-3 should be included in your game) were absorb, wild, sickle, and glitter. My entry is titled "Spy Party."

Spy Party is a one-shot RPG in which players are communist (hammer and sickle) spies who have come to a makeover party in suburban Washington DC in hopes of exchanging intel with their undercover contacts. They must absorb fragments of knowledge from other players to figure out the USA's secret plans and weaknesses, while keeping up their cover of frivolous gossip and trying out glittery nail polish. Players paint each others' nails different colors to indicate levels of trust, while certain color combinations trigger in-game events. At the end, the colors of players' nails allow them to determine each others' fate (e.g. who is put on trial for espionage? Who is rewarded by your home country?)

Download Spy Party

Saturday, May 17, 2014

Fiasco: YOU ARE A CAT

On a whim I created a Fiasco playset titled YOU ARE A CAT. We tried out a three-player game that went well.

Our story began with nearly-identical fluffy tortoiseshell cats Robin (male) and Arthur (female) stuffed into the same cat carrier on the way from the animal shelter to their new forever home. Their new human had intended to adopt Arthur, but due to a mix-up at the shelter, both cats had gotten put in the carrier. They arrive home and the human -- a single woman -- discovers that she now has two cats. Robin decides to act extra adorable to try to convince the human to keep him and not send him back to the shelter. He's in luck, as the human is unable to get through to the shelter on the phone to complain about the mix-up.

Arthur soon discovers a third cat in the house -- this one also a nearly identical fluffy tortie -- emerging from the dryer vent. The new cat introduces himself as Killer, Robin's future self come back to warn his past self against making a grave mistake. He demonstrates his future knowledge by telling Arthur not to eat a certain tasty-looking houseplant, as it is poisonous. The human discovers Killer and assumes he is Robin.

Later in the day, Arthur is curled up in the human's lap being adorable when Robin enters the room. Arthur tells Robin about Killer, but Robin is unconvinced. To try to prove Killer wrong, he eats a big bite of the tasty looking plant -- and immediately pukes all over the floor.

The next day, Robin is sitting in the human's lap while she does some work on the computer. He sees her log into something labeled "TOP SECRET HIGH SECURITY," and the screen shows "Nuclear Launch Code: password123." Robin bats at the keyboard, accidentally initiating the launch sequence, which the human quickly cancels and then shoos Robin off her lap.

Killer confronts Robin, explaining that he is Robin's future self come back from a terrible post-apocalyptic dystopia with a dire warning. Killer insists that Robin should forget all about the nuclear codes he saw. Robin denies this, and loudly proclaims "password123! password123!"

Arthur wanders by and overhears the nuclear code and asks Killer about it (though she can't remember whether it's "password 123," "password 456," or "password321"). Arthur completely believes Killer's story and becomes very concerned about what Robin might do with the nuclear codes.

That night, Robin goes back on the computer to research what "nuclear launch codes" are. He Googles a bunch of information about the Cold War, and -- lacking any knowledge of historical and geopolitical context -- becomes convinced that Russia is located just around the bend in the road that they can see from the front window of the house. He is also certain that Russia intends to attack and destroy them, and that Killer is a Russian double agent.

Killer offers to take Robin and Arthur around the bend to show them that it is not, in fact, Russia, and to convince them of the terrible fate that awaits them if they do not forget about the nuclear launch codes. They all slip out through the dryer vent and walk around the bend. They meet another cat, named Coby, who knows Killer. Robin accuses Coby of being a Russian agent and asks him how to spell his name in Cyrillic (to which Coby replies "spell?"). Robin sees a teddy bear inside one of the houses on the new street and takes this as proof that this is in fact Russia, since Russia's symbol is a bear.

Killer leads the other two cats through a crack in the fence into a junkyard in order to show them what kind of future awaits them. He kills a mouse, to show what they'll have to do for food after the nuclear war. Arthur is worried because the mouse has no sauce on it (unlike good wet canned food). Robin dismisses the concern, because he finds an old pizza box with cheese stuck to the lid.

Back at the house, Robin decides to launch a preemptive strike on Russia. He gets on the computer and starts logging in to the nuclear launch site. Just before he is able to enter the launch password, Killer chews through the computer cord, shutting it down. He runs away as the human -- hearing the ruckus -- comes downstairs to find Robin typing on a dead computer. She takes him upstairs and shuts him in her room to prevent further mischief.

Killer talks to Arthur about a more long-term solution to Robin's insistence on starting a nuclear war. They decide that they can get him in trouble by peeing on everything, since that is a male cat behavior. They pee everywhere in the house -- except in the bedroom where Robin is sleeping.

When the human comes out in the morning, she initially blames Arthur. However, Robin emerges and takes the pee as a sign that he should pee everywhere too. The human gets upset and takes both Robin and Arthur back to the shelter. The shelter personnel figure out that Arthur was the cat she meant to adopt, and they take Robin back.

In the end, Robin is given several rounds of gross medicine for his urinary "problem," but is then adopted by a new family. They do not have access to the nuclear launch system, but he discovers that "password123" gets him into their bank account, Amazon account, eBay, etc. With their finances ruined by Robin's meddling, they are forced to send him back to the shelter.

Arthur lives a nice life with the human. He overhears Killer telling Coby about how he tricked these other cats into believing he was from the future, and so Arthur drops a flower pot on him. The human discovers Killer and takes him to the shelter, where he is promptly adopted by a nice family.

Monday, March 10, 2014

RPG night: A Tragedy In Five Acts

Tonight we played A Tragedy in Five Acts. This was a first for everyone at the table -- I knew of the game because the designer is a friend, but I had never played it.

Our setting was a farm in Quebec in the late 1960s. The Canadian government has decided to try to beat the Soviets and Americans to the moon, and to that end has funded the building of a rocket.

Our characters were:
Rosie, the Daughter -- a competent engineer whose talents are overlooked because she is a young woman in a low position in the project hierarchy. (Fatal flaw: Fortune's Fool)
Dougal McGuire, the Lover -- an aspiring astronaut whose true love is the Moon. (Fatal flaw: Arrogant)
Farmer Pierre, the Foil -- on whose land the Canadian space program is building its rocket. (Fatal flaw: Jealous)
Werner von Grupp, the Parent -- a German janitor who pretended to be a rocket engineer so he would be pardoned at the end of World War II. (Fatal flaw: Ambitious)
Clarence Bishop III, the Authority -- an overly-trusting government bureaucrat overseeing the space program. (Fatal flaw: Overly Trusting)

With appearances by Frank the real engineer, Jacques the cow, and Francois the cow.

ACT I

Scene i: Farmer Pierre comes to the rocket-building site to inquire what is happening, as he is afraid his cows will fall into the giant hole that the rocket team is digging. Clarence arrives to check on the project, concerned about where the government's money has gone. He is given an order for steel tubes in a confusing mix of metric and imperial units that suggests they have no idea what they are doing.

Scene ii: Rosie and Dougal have lunch next to the tanks of corrosive acid that are being used in the rocket construction. Rosie insists that Dougal needs to read the astronaut training manual she has prepared for him, but he demurs.

Scene iii: Werner calls Pierre into his suspiciously opulent office. Because Pierre has some practical engineering experience from repairing his farm equipment, Werner wants him to join the rocket team. Appeals to patriotism fail, but Pierre is convinced by the opportunity to defraud the government of more money.

ACT II

Scene i: Clarence goes to check on the receipts for the project, and instead comes across some correspondence between Werner von Grupp and his hero Werner von Braun. Unable to read German, he takes them to Rosie for translation. In the letters von Grupp shares his rocket ideas and von Braun assumes he must be a rather dim third-grader. Rosie is alarmed, but lies to Clarence and says they are merely social correspondence.

Scence ii: Werner proposes building a 1/16-scale test rocket. Pierre insists a certain connection needs 10 wires (to bilk the government out of more money) while Rosie explains it only needs three. Pierre concludes from this that he misunderstood the numbers in English -- 10 is actually 3 and vice-versa.

Scene iii: Pierre and Werner launch the test rocket, which crashes into the paddock where most of the cows are -- leaving only Jacques and Francois alive. Dougal is upset at being left out of the launch.

ACT III

Scene i: Having realized things are not quite right, Clarence has called in a competent engineering team, led by Frank. Dougal is upset that they are making him do real training and eat real astronaut food, Pierre is upset that they won't let Jacques and Francois be his interns, and Werner is upset that Frank is upstaging him.

Scene ii: In his office, Werner cuts and pastes to swap the authors' names on his and Frank's rocket schematics. Then he goes to Clarence's office and shows him all the flaws in "Frank"'s schematics. They agree that Frank needs to be fired for his incompetence.

Scene iii: Pierre and Rosie are working on the rocket while the new team takes their union-mandated lunch break. He tells her he is jealous that Dougal is going to get to go to the moon. He shows her how, if they upgrade from "10" fuel tanks to "3", they will have enough thrust to add an extra pod to the rocket that will hold himself, Jacques, and Francois.

ACT IV

Scene i: Clarence confronts Frank, who calmly explains that the names have been switched on the schematics, then tears them up so nobody will mistakenly use them. After Clarence leaves, Werner lures Frank outside with a fake apology. While he's distracted, Dougal (on Werner's orders) sneaks up behind him and, after some hesitation, kills him with a wrench. Werner and Dougal dispose of the body in the acid tank.

Scene ii: Rosie finds the correct set of schematics, but seeing Werner's name on them she thinks they are the old plans and rips them up so that nobody will mistakenly use them. While she is doing this, Dougal -- who has been drinking heavily to dull the guilt from murdering Frank -- wanders in and begins to babble to her.

Scene iii: Werner panics upon finding both sets of schematics have been destroyed. He calls Pierre in to re-draw the plans from memory. Pierre does so, adding his cow pod to the design.

ACT V

Scene i: Dougal drunkenly confesses the murder to Rosie, and tells her "von-not-supposed-to-tell" put him up to it. She goes to confront Werner. He manages to talk her down.

Scene ii: Pierre convinces Dougal that they should launch the rocket early (so Dougal can escape to the moon, and so that nobody can stop Pierre from loading Jacques and Francois on board). Pierre plans to surprise Dougal when they get to the moon. He counts down (3, 9, 8, 7, 6, 5, 4, 10, 2, 1, liftoff!), then pushes the launch button and the rocket takes off. But because it is unbalanced (from the udder-shaped cow pod attached to the side), it comes crashing back to Earth and explodes in the acid tanks, killing Pierre, Dougal, Jacques, and Francois.

Scene iii: A month later, Werner, Rosie, and Clarence appear before a parliamentary inquiry. Their incompetence is laid out for all to see. Werner loses all credibility as a scientist and has to go back to being a janitor. Clarence and Rosie are exiled to the USA to work on the US moon landing program.

Our winner, with a score of 210 (to second-place's 88), was Pete, playing Werner von Grupp. He named this monstrosity "Maple Moon Cows: The Untold Story of the Canadian Space Program."

Sunday, February 16, 2014

Playtest -- The Last Two People On Earth

One of my projects is to create some roleplaying games that are specifically designed for just two players. I won't claim an extensive enough knowledge of the RPG market to claim that such games are rare, but they certainly present a unique challenge. For my first attempt, I took on a post-apocalyptic theme. The two players are, so far as they know, the last two people on Earth.

The mechanics are pretty obviously inspired by Fiasco. For the setup phase, players each roll a pool of dice, then use the numbers shown to pick items out of a table to create the scenario. The scenario defines things like the nature of the apocalypse, how the players' characters survived, and how they met. For the main game, the players re-roll their dice and use them to select scene prompts which the other player must then work into their scene. At the end, the players use their remaining dice to select their characters' ultimate fates.

In our game, we decided that the apocalypse had been caused when the government finally tried to control the minds of everyone who had been drinking fluoridated water their entire life. This didn't go so well, and so everyone died, and now packs of wild dogs roamed the ruins. Our characters were Justin Bieber, who survived due to prodigious consumption of vitamins, and Lieutenant Colonel Dolores Gripley, who had just emerged from several years in a secret government cryogenics experiment. They met while scavenging in the ruins of the Cedar St. Giant Eagle in Pittsburgh. Justin appealed to Dolores for help, because while the store was still full of food, he (as a pampered pop star) had no idea how to cook it. Dolores didn't recognize him (having been frozen during his entire career), but she took pity on him.

Accompanied by Justin's trusty dog Artie, the two set off to the park by the river to eat, when they came upon the corpses of Justin's fans who had been leaving his show at PNC Park when everything went wrong. They both fled onto the 9th Street Bridge -- Justin because the bodies were covered with bugs, and Dolores because she hallucinated that they were coming back to life. Upon hearing Dolores's story, Justin tried to go back, thinking his fans would help him. Instead of his fans, though, he encountered a pack of wild dogs. Artie ran ahead, and somehow charmed the wild dogs. Justin reasoned that just like he was famous among humans, Artie must be famous among dogs, and so the wild dogs were his dog fans.

Dolores was increasingly confused, so Justin turned on his radio, hoping to hear one of his songs so that he could show Dolores how famous he was. Instead, the radio picked up a bulletin calling for any survivors to rendezvous at the WESA studio in the Southside.

Justin, Dolores, Artie, and the wild dogs proceeded to the Southside where they found the WESA staff as well as several visiting NPR personalities barricaded in the studio. Carl Kasell was guarding the entrance with a machine gun. He confessed that he was Justin's father. He had wanted to reconnect, but he couldn't afford a ticket to one of Justin's shows. In order to verify the identities of anyone seeking refuge in the studio -- to make sure they weren't part of the government conspiracy -- the studio dispatched a team of crack investigative reporters. Steve Inskeep, who had for some reason been turned into a minotaur, came out to check out Dolores and Justin. Justin grabbed Steve's microphone and sang an impassioned concert all night, proving his identity and bringing tears to everyone listening.

In the end, everyone from the studio set out down the Ohio River on the Gateway Clipper (renamed the Gateway Bieber). Justin reveled in his new NPR-listener fan base, and Dolores fell in love with Carl Kasell.

Draft rules -- The Last Two People On Earth