Saturday, November 21, 2009

In Media Res

A thread started on Story Games about starting games in media res, or, "in the middle of things." This has particular interest for me, because I've tried to design the Fifth World to tell bioregional epics. The Wikipedia entry on "epic poetry" provides a list of criteria you'll find, more or less, in any discussion of what an epic means. I have my praepositio and invocation at the beginning. Like John Milton in Paradise Lost who turned the Greek Muse into the Christian Holy Spirit, I use the invocation to ground the epic by identifying the muse as the Spirit of the Place. The use of epithets requires a little more thought, but at present, I think having to invoke your name to start using the mechanics helps bring that element in. I'll admit, I still don't have a good idea on how to bring in more enumeratio. But for the moment, I have the problem of starting in media res more in mind.

From the playtests so far, I feel confident that the basic approach to story structure does work. Fluency play means introducing each rules element, one at a time. As an extension of that, you can control the pacing of the story by introducing rules elements in a deliberate order. I definitely need to tweak that order, but I feel confident now in the basic premise. Specifically, we consistently found that the coin-flipping mechanics came up too late in play. Many of the ritual phrases and so forth refer to that implicitly by costing coins, but without the coins in use early on, you have little idea of what kind of price you pay.

What if the very first scene had you confronting Trouble and flipping coins? You could begin in media res. Later, when we introduce the Memory mechanics, you can use those to establish how we got to this point. This would introduce the coin-flipping mechanics at the very beginning, and add the other ritual phrases later on.

I think this would definitely change the tone of the stories, too. It would make the stories fundamentally about confronting Trouble. I think I like that emphasis, since it also gives more room for players to cooperate. The current framework sometimes allows for the game to end in some clever consensus, which works especially well when characters end up with what they wanted, but not in the way they expected to get it. This approach, though, does seem to give gameplay an essentially player-versus-player quality. I think beginning in media res, with Trouble mechanics, would make gameplay essentially cooperative, about our heroes working together to solve the Trouble facing their people. I think that dynamic could work very well. I'll need to whip up a version of the poem that does that, and see how it plays.

Friday, November 20, 2009

Wrap It Up

In improv theater, knowing when and how to end a scene often poses a problem. Often, a show has an emcee who solves this problem by simply deciding when a scene ends. In traditional RPGs, GM's control all aspects of pacing: they frame every scene and determine when every scene ends. Collaborative storytelling means liberating players from GM's and GM's from their obligations—and that means exploring other ways of figuring out when a scene ends.

This came up in playtesting. We had some scenes that had a hard time finding their focus, and as a result, would ramble on for far too long. We need some way to signal when to wrap it up.

In literature, every scene has a specific purpose, and the scene ends when it has fulfilled that purpose. In a story game, though, we may not know a scene's purpose until we've finished playing it, so how can we know when it has fulfilled that purpose? More importantly, how can we know in that moment, that a scene has finished, with all the other things we have to keep in mind in play?

I've decided to take a page from a Norwegian game called "Until We Sink," which itself seems to follow the model of most plays. In "Until We Sink," a scene ends when two characters have left. This means that one character can't arbitrarily end the scene prematurely, but by the same token, one character can't keep the scene going, either. When the first person leaves, it probably signals to the others that this scene should end soon, sending that "wrap it up" message to everyone playing. As with so many other parts of the game, I'll have a ritual phrase to indicate this, which should help to give it some additional weight.

Thursday, November 19, 2009

Rules Are Made To Be Broken

I try to keep this blog in E-Prime, so writing that title pains me. Yet, that old slogan fits my topic today too perfectly to pass up. It seems to me that one of the primary functions of a rule in any RPG lies in the opportunity to break it. Who can break it, and when, becomes one of the primary means of defining a character.

I considered adding an idea to the playtests at GASPcon, but decided to try the simpler version without it first. I considered making several cards, allowing each player to choose one for his or her character. Each would announce a particular character trait, and with it, a specific rule that the trait allowed the character to break. So, for instance:
  • Ungrateful. You can have 12 Debt before you die, instead of just 10.
  • Contrary. Using the ritual phrase, "I have never heard of such a thing" costs you no Debt.
  • Wistful. Choose a Memory. You can use it twice in this game.
  • Famous. You have a bonus Name.

I don't know if it would fit into the poem, and part of me worries about including a list like this. On the other hand, it offers so much more room for people to define unique characters that I keep coming back to the idea.

When combined with an idea like Trouble, it presents even more opportunities. For instance, you could incur one more Debt to attach one of these to a Trouble. So, you take on four Debt. You take three coins of Trouble, and put them on a new Trouble called "Wandering Mercenary," with "Famous" attached to it. The person who eliminates that Trouble becomes "Famous," so he can gain another Name because of that victory.

I don't know if this idea will work, but it seems to open up enough opportunities to warrant playing around with it to see where it might go.

Wednesday, November 18, 2009

Causing Trouble

Consistently, the playtests so far have revealed a dearth of situation. People complain that they don't know where to take their characters. I included a step in character creation where, after you introduce your character, we go around the table, and each person tells you something that you want from their character, that their character won't give you. I thought this might provide some good opening tension—even if it might wind up pointing play into a player-versus-player mode—but that just didn't happen.

So, I find myself going back to an older idea, and finding a better place for it now than it had when I first conceived of it.

Right now, you start with some amount of Debt, based on your age. This reflects what the Land and the People have provided to you over your life. Older characters have lots of Debt; younger characters, much less. You use your Debt to accomplish things, so young characters may need to get more Debt. Thematically, it seems to make perfect sense that you'd get more Debt by causing Trouble. So, you can take as many coins of Debt as you like, if you put an equal number of coins into Trouble. Older characters, with plenty of Debt already, could get rid of their Debt by settling Trouble. Which also happens to present precisely the dynamic I'd like to see: older characters cleaning up the messes that younger characters start.

When adding Trouble, you write down something that Troubles the People in a central area, perhaps a sheet of paper in the middle of the play area. You put at least one coin on it. You can put more coins on it, to make that Trouble more troublesome. In play, characters can confront that Trouble. They invoke their Names, which lets them throw coins from their Debt equal to the words in that Name. For each head, they can return that coin, and one coin from the Trouble, to the bowl. So, you can work off your Debt by solving Troubles.

Yet, you can only get more Debt by causing Trouble somewhere else. When you start the game, you get a starting Debt based on your age. I think you should probably introduce some starting Troubles, too, with coins equal to your starting Debt. Since zero Debt makes you ineffective and cut off from the world, you can't really ever solve all the Trouble in the world: you can only solve some Troubles, some of the time, and try to arrange your Troubles in a way you can live with. I think that in itself says something powerful, especially in a pseudo-utopian game.

This has the added benefit of letting players guide the game in a direction they want. Giuli and I have both noticed, with some irritation, that a disproportionate number of our playtests involve cannibals, for instance. It makes sense: they fit so well into the tropes of post-apocalyptic fiction. They violate the positive vision of the future that the Fifth World drives towards, though, and that really gets at the heart of the design problem the game needs to solve. We don't want to lecture people about why the Fifth World won't involve short lifespans, raging cannibals, or high infant mortality, but how do you get people to move past those stereotypes otherwise? A Trouble mechanic allows us to define the problems we face. With it, I can introduce my missing brother, who went hunting and never returned, but instead became a wild man (see the part about "Bigfoot" in this blog entry from April). Or we can add the curse sent upon us by Deer, because someone killed a deer violently.

Conflicts between characters lead us into player-versus-player games. Conflicts left to emerge collaboratively may trend towards stereotypes. But letting people establish Troubles may mean that we can guide a game in a specific direction, with the kinds of conflicts that we at the table find interesting and meaningful.

It also has the added benefit that we can actually play a cooperative, GM-less game. Everyone at the table can work together to eliminate the Trouble.

Tuesday, November 17, 2009

Ganakagok

I've taken lessons from Ganakagok already, but only on Saturday did I get to play it. Bill came to GASPcon 10 to run it, and I made a point of getting into his game. I walked away with a book and a card deck; I hope to run it this weekend, and at the next regular GASP Games Day.

Something kind of magical happens in a game of Ganakagok, it seems. Bill's designed the cards so well that you could really believe in their divinatory power. So often, you get just the right card, that you might swear that someone rigged the deck. I think this involves more than just a common Barnum effect, where people naturally interpret a vague, general statement as something eerily specific, though that no doubt plays a part. Rather, Bill's designed the deck so well that the kinds of situations that the Nitu face come up in it regularly. More than just sufficiently ambiguous meanings, these cards have just the right punch and context to really make them matter.

Much of the game revolves around the interpretation of those cards. When we roll dice, we roll to see who will get to interpret the cards, and what consequences will follow from that struggle. That gives the game a definite momentum. Each interpretation builds on the last; the game gains a forward motion as we rush towards its climax.

Bill's called this the "Mythopoietic Edition," and I think he has picked just the right word for it. He's designed a game that really does seem to create myths, consistently and reliably. He calls it "a quasi-Inuit Silmarillion" (referring to the poetic elven mythology that J.R.R. Tolkien invented).

Issues of cultural appropriation do arise out of this, and while I, too, cringed at phrases like, "primitive and icy," overall, I admire how Bill has handled the situation—particularly upon reading his most recent blog entry, where he advised people who have enjoyed the game to donate to the Nunavut Arts and Crafts Association.

While the cards you draw will create a different world with each game, you can never get very far from the stars disappearing from the night sky, and the inevitability of the morning. Though the world you've known differs from one game to the next, that world always comes to an end. Your character stands out as a protagonist because you recognize this earlier than most others. You have your hope for what the change could mean, and your fear for what it might mean. You have the balance of Good and Bad Medicine in the world, amongst the People, and for yourself. Ultimately, this game really digs into how we cope with inevitable disaster. The real world lets you take your pick:—global warming, peak oil, mass extinction, et cetera ad nauseam. In this game, the coming change—the Morning—has definite positive aspects, as well as negative. You almost certainly won't succeed in having more Good Medicine than Bad for the world, the people, and all of your characters. Even one will give you a challenge. So this change will include some amount of tragedy. Yet it doesn't need to mean unmitigated tragedy. As much as this game deals with fear and resistance to change, it also deals with embracing change, and finding hope in it. For that, I think Ganakagok has some pretty powerful, good medicine for us all. It leads you through a myth all about how the world will change, and how we deal with the need to face that reality—pretty much exactly what we all need right about now.

Monday, November 16, 2009

GASPcon Playtests

GASPcon 10 expanded to three days, adding two RPG slots on Friday. I ran one of the two Fifth World playtests of the convention on Friday night. I wound up with a bit of an "all star" playtest group, including Jenn from the Trapcast, and "Mr. Teapot" Nick Wedig, designer of House of Masks, which won Game Chef last year. Ironically enough, the fourth fellow at the table—the one I didn't know—gave some of the best performances.

We returned to the Point. I must assume the Ferryman met a cruel end, since we now had a tribe living there who thought that the portal to the Underworld there required human sacrifice. They had taken Jossiah the Healer, and wanted to learn his secrets. So their chief assigned a teenager named Hawk Necklace to become his apprentice. My character, Sleepy Watch, had failed to protect Jossiah, so he enlisted Paws, who took the blame for that because of their uncanny physical similarity, to help him rescue Jossiah. Paws lived in exile in the ruins of Oakland. The panthers had returned there, and allowed no one to approach, but Paws had become kin to them.

Paws and Watch received the help of the people just for trying to fight the other tribe off. They even gave them their magical weapons (the last remaining weapons made of metal). Hawk Necklace met them while looking for someone his people could sacrifice in Jossiah's place, and hatched a plan to sneak Paws and Watch in as prisoners. Watch challenged the chief, and managed to kill him. Watch considered the tribe cannibals, so he ate the chief's ear; but, they didn't actually practice cannibalism, so the gruesome scene simply had the effect of frightening them with his apparent madness.

The slaying of their chief put their village into chaos. A new chief arose, concerned primarily with saving his people. He considered a war on the People of Watcher, Paws and Jossiah a task that could give them the purpose they needed. They looked for ancient propane tanks in Oakland, with which to burn the forests there to the ground and send the panthers back into the Underworld.

After slaying the assassins sent after them and learning of this plot, Jossiah enlisted the aid of the whole village in retrieving these tanks from the old tunnels. Watch kept solitary guard against their enemies, now overconfident with pride. When the enemies came, the panthers fell upon them, but Watcher made a sudden movement against one of the attackers, provoking a panther who scarred his face.

In the tunnels, the enemies swarmed the people. Paws stabbed his spear through one of them, and into a propane tank behind him. They all exploded, consuming most of their enemies. Those that remained mistook Paws for Watch, and began to scream, because the boy who had killed their chief could unleash a firestorm with the strike of his spear.

In the end, Paws returned to the village, and Watcher went into self-imposed exile among the panthers. Just as they had both initially desired, they switched places. Their appearance spread a legend about a boy with magical powers and incredible strength, who could even appear in two places at once. Hawk Necklace left his old people and joined a new people, and Jossiah found hope that the next generation might not always seem less wise and less strong than their ancestors.

The second playtest on Sunday afternoon I played with some of the folks responsible for GASPcon. That one I'd have a harder time recapping from a fiction angle. We had a lot of interruptions, and because it involved some of the folks responsible for GASPcon, exhaustion overtook the game and we ended early. But I still got a lot out of this game especially because of Todd. Todd has taken a real interest in the setting, and he's given me a huge number of really great ideas. Possibly more important than anything, with a project like this, you can easily lose your bearings, and you end up with very little sense of the quality of what you've come up with. Todd gave me a much-needed touchstone to gauge where I stand with this.

In previous iterations, at this point in the playtesting, I'd start to re-evaluate the most basic parts of gameplay. Now, not so much. The poem seems to work for getting into play immediately, helping keep the story's progression on track, and setting a different mood for each round by controlling which rules everyone has access to at that moment. I need to work on the progression of those rules, and as I'll write in some upcoming articles here, I've come up with some different rules to try out. But right now, I expect to bring a game to Dreamation that will look a lot like the game I ran this weekend, and right now, that alone feels like a triumph.

Sunday, November 8, 2009

Playtest Report #2

I got to playtest the Fifth World for the first time around a table on Saturday. My brother, Giuli and I played. I felt really good about the story that came out. I played a football star who wanted to live forever; Mike played the Ferryman, the heir of the character I played in the previous playtest; and Giuli played a character inspired by Nausicaä, who wanted to restore the toxic forest growing up out of the ruins of the Waterfront in Homestead. Actually, that location requires some elaboration, actually. A steel mill once sat down there. The Battle of Homestead happened near there, where Pinkerton soldiers attacked striking steel workers. Today, a large shopping complex sits on the site. The appropriation of so much of the world's biomass to build places like that, and the sprawling suburbs around them, have concentrated much of the world's biological wealth in those areas. In the Fifth World, once all that material finally gets to rot, some of the most vibrant forests grow up out of the cellars, washing machines and cars of suburbia. In this case, it sets its roots into soil filled with heavy metals from the old steelworks. I suggested a story of domination: domination of the steel workers, domination of the earth by the steel mill itself, domination through consumerism, and in the Fifth World, a place angry at humans because it has seen so much of humanity's worst qualities. Mike went for the complete opposite story: freedom bought with great sacrifice, like the labor movement bought with in the Battle of Homestead, or the life of the forest bought despite the heavy metals in the soil. Giuli went with that, and her character tied into that story because she wanted to heal the land.

Mike made the Point more of a sacred garden, as opposed to the terrifying otherworld from our last game. In the fountain, an abnormally large oak tree grows, with its roots reaching down into the secret fourth river that flows underground. When my character, the football star, wanted to live forever, the Ferryman told him to swallow an acorn from the tree whole.

Through the various rounds, my football star became more belligerent, since he thought he'd become immortal. He got married to Giuli's character, and the Ferryman told him he could cleanse the forest so important to his new bride by eating the poisoned fruit there. Since he would live forever, he had nothing to fear.

He died, right there.

The elders of my character's village accused Giuli's character of assassinating their star player; she submitted herself to their judgment to keep the villages from going to war. They executed her, and buried her next to my character, in the toxic forest she loved so much.

Next came the rounds with the memories, which worked out perfectly. The action had reached its climax, so now we went back, before, to see why it had all happened. The real climax of the story came later, even though, chronologically, it had happened before. My character remembered his grandfather dying, and telling him a story that I took from Paul Radin's Primitive Man as Philosopher, about a Ho-Chunk boy who wanted to live forever. He died, and grew into a tree—because only trees live forever. That acorn I had eaten before, what the Ferryman promised would give me eternal life? It sprouted. Its roots went deep, deeper than all the other plants, and sucked up more of those heavy metals than any of them could. So, I lived forever—and cleansed the forest.

Giuli asked why her character had to die, too. My character had wanted her admiration; despite all the women who fawned over me, I wanted her to notice me. In her epilogue, we found out why: I had sacrificed my human life to cleanse her forest, so she became a tree, too, so that my sacrifice wouldn't mean spending eternity alone.

The poem's structure paced it out perfectly, even when the other players worried that we'd reached the climax too soon. It created a beautiful, moving, poetic, mythic story really anchored in the land. I felt very good about that.

Like the playtest before, players raised some concerns about not having enough material to start with. I wanted to make character creation a part of play, rather than something that happens before play. I still suspect that I just need to press for stronger desires, but I'll definitely have to keep in mind that it may need some way of generating more pregnant starting situation.

In both games, the mechanics didn't kick in very often. That may also need some more work; or, it might work just fine right now. Who says that the mechanics need to kick in all the time? Maybe "leave them there unless you need them" makes for a perfectly viable strategy.

Another interesting thing to note: in both games, we had three players, and it took just over two hours, making for just over 40 minutes per player (I've measured time per player because I think, with the rounds, that how long a game takes will work as a function of number of players). If that continues to hold, then a game with six players would take four hours—one standard convention slot, precisely. Of course, I'll need to test other size games to see how that ratio holds up. I'll also need a much larger data set to say anything with confidence.

I haven't playtested nearly as much as I would like so far, but I think I can take this to GASPcon without too much worry. I've billed it as a playtest, so nobody should expect a finished game. All the same, the problems don't seem to break it entirely, either, and playtesters have even had fun with it.