Hello,

This post is part background for my other Pitfighter threads, part summary of my take on a classic problem in RPG play, and part response to Jamie's recent encounter with this problem.

Terms:

First, a few terms I'll use here (and would be happy to see used elsewhere):

1) Before, Now, After.  When any activity (formal procedure, casual group chat, writing ideas, etc.) is performed relative to a given session of play.  More specifically, for this discussion, when any decision or determination is made.

2) Outcome.  How a situation of play, as faced by the player characters, resolves.

3) Play Situation.  Something the player characters do address, regardless of whether it's choice, dice, or Force that brought them there.

4) Plot Situation.  What's going on in the player characters' world, regardless of whether they can or can't and do or don't address it.

The GM's Evolving Wants

I went into GMing with an explicit intent to do Plot Situation Before.  I was excited to have all of my cleverly-written developments, with my various schemes and factions, occur during play.  However, unlike Montsegur 1244, which does Plot Situation Before, I also wanted the players involved in that plot somehow.  Exactly how, I hadn't though about.

As we began play, I tried to engage the players with my plot by offering them a difference-making role in it.  Boom!  The Montsegur formula is out the window.  You can't script that the Cathars are besieged by the Catholics in Act 4 if you're going to be enlisting the players to prevent the siege in Act 1!

But I didn't realize that I was wrestling with an incompatibility here.  I was getting a big high off the players' involvement, which I didn't want to back off from.  I told myself that I was willing to be flexible about my plot's specifics, so I thought that the players' impact could simply be incorporated.  And there were some times when I was right!

So, at this point, I'm no longer doing Plot Situation Before; I'm doing Play Situation Before.  This is vastly more rewarding.  In Montsegur, the Catholic invasion doesn't always even get talked about by the player characters.  Sometimes the context that it lends to the relationship dramas in the castle, while valuable, is completely unspoken.  In my Pitfighter game, on the other hand, my Mandragon invasion was all anyone could talk about!  When, how, what does it mean, what can we do about it, what should we do about it?!  We had some sessions where the back and forth was truly glorious, with the players captivated by my every nugget of revealed plot, and me captivated by their every response.

Unfortunately, the dirty secret I never faced up to was that you can't do Play Situation Before without doing Outcomes Before.  I would start with a Situation I thought was open-ended, but then realize in the moment that there were certain ways it couldn't wrap up if I was going to introduce my next Situation.

It took me a while to catch on.  Before I did, I used a lot of awkward Force.  "Oh, crap, I can't let you take the pirates' boat!  Uh, it catches fire."  Probably the worst possible solution for long-term play, as it short-circuits player expectations about how to contribute.

My friend Marc ran a 3-year Rifts campaign right before this, and he had a different problem.  He refused to use Force, but wasn't prepared to support play outside his plot.  So there was a lot of meandering about in There's Nothing Fun To Do Here land.

Different approaches, but Marc and I had the same problem.  As GMs, we valued player choice and hated the idea of railroading.  But we were addicted to Play Situation Before!  We tried to have it both ways, and it didn't work (colorful examples in next post).

The GM's Awakening About Situation

At some point, Marc and I both had our awakenings, and realized, "Oh yeah, being able to get Situation 2 into play means a limited range of Outcomes for Situation 1."  This is the point when you might think we'd say, "Hey, maybe we should evaluate what we really want to do with our plots, and get the players on board with that."  But no!  We did what a lot of GMs apparently do, if the bulk of "good GM advice" out there is any indication:

We tried to plan the connection between Situations so perfectly, to cover everything the players might do so thoroughly, that no Force would be needed.  I'd anticipate that the players taking the pirate ship would be bad for my plot, and so I'd make that an obvious impossibility from the outset.  Thus no last-minute "Uh, wait, no!  Your plan that should have worked, doesn't!"

And this is where the dream began to die.  Have you ever tried to do this?  It is not fun.  If you're psyched to be making up stories and enlisting other people in experiencing them and adding to them, then the last thing you want to do is go over your exciting yarn with a magnifying glass and pre-play out everything that might happen.

But it's tough to see another way out!  If this soul-crushing method was completely ineffective, it'd be easier to write it off.  But it actually does work, if you're willing to put in the time.  My friend who spent two months prepping each session never used Force and only rarely had a brief departure into No Fun Here land.

Two months.  Count me out, man. 

The Patch

In the end, my group did what a lot of groups do: we found a balance:

1) I did some planning to avoid using Force. 

2) With lots of practice, I was eventually able to anticipate a Force moment on the horizon and ad-lib something to make sure it didn't arise. 

3) Sometime I wouldn't feel comfortable using Force, and the players would wander off the plot, and then I'd just try to help make the off-plot tangent enjoyable, with humor or whatnot.  Like the nasal-voiced armorer who kept trying to sell the party an Enchanted Stoat.

4) And every once in a while, I would use Force, and it'd be awkward, and there'd be moments of anger or resentment, but the players would forgive me because they knew the pattern (I wouldn't do this too often), and the social activity of play was fun enough (thanks in no small part to my engaging plot) for us to persevere past some hitches.

Conclusions

Look at all that.  That isn't the right way to do anything.  It's unreliable, risky, and demanding.

And yet, the overall experience of play, over many many sessions, was positive.  Maybe that's because we started young, with tons of free time to waste, and played often enough to develop some serious skills over the years.  By the time of my college Pitfighter game, I probably had over a thousand hours of GMing under my belt.  But I don't think that's the only reason.

I think the basic thing we were attempting is incredibly powerful and attractive.  (I've ranted about why enough elsewhere, but will repeat here if requested.)

I also think that, absent relevant rules or guidance, it's somewhat natural for GMs to fall into Outcomes Before, even from a starting point as innocuous as "I've come up with some cool stuff I want to happen in play!"

Ps,
-David

David wrote: Marc and I had the same problem.  As GMs, we valued player choice and hated the idea of railroading.  But we were addicted to Play Situation Before!  We tried to have it both ways, and it didn't work (colorful examples in next post).

A final note about characters, character creation, and expectations:

At the point where I as GM began doing Play Situation Now, the players' range for exploring their characters took on some serious constraints.  If this had cut off what they'd been excited about in the first place, that could have been a deal-breaker!  That sounds to me like what happened in Jamie's Glorantha game.

Fortunately, Pitfighter was my baby from the ground up.  My campaign plot was already partly formed in my mind before we even agreed to play.  So, when I introduced the setting, the players were getting the right idea.  And, when they made characters, I worked with them, to tie their interests to mine (and even a little bit to my plot, though I wasn't aware how crucial that would be).

All this meant that when my Force popped up, at least the players weren't having much anticipated or hoped-for content yanked out form under them.  If we'd been using someone else's world that the players had learned from a book, and character creation had been done individually, that probably would have been disastrous.

David wrote:
Fortunately, Pitfighter was my baby from the ground up.  My campaign plot was already partly formed in my mind before we even agreed to play.  So, when I introduced the setting, the players were getting the right idea.  And, when they made characters, I worked with them, to tie their interests to mine (and even a little bit to my plot, though I wasn't aware how crucial that would be).

All this meant that when my Force popped up, at least the players weren't having much anticipated or hoped-for content yanked out form under them.  If we'd been using someone else's world that the players had learned from a book, and character creation had been done individually, that probably would have been disastrous.

Did you ever try revealing your plots to the players prior to play?  If so, how did that work out for you?  If not, why not?

Cheers,
Roger

Jamie,

That makes perfect sense to me.  I remember taking home the Cyberpunk 2020 game in high school, making a badass assassin character with monowire and a synthetic demon face, and getting all psyched to basically play Hunter Rose Grendel... and then I wound up as part of a 'tac team trying to unravel the mega-plot of some evil corporation while shooting it out with their henchmen.  Gah.  Not thwarted Story Now per se, but definitely a thwarted vision.

Totally agreed on Montsegur, though I'm surprised by that point about BE.  Isn't it part of the GM's job to engineer intersections between the characters' Beliefs and the Vaylen's agenda (via the FONs' Beliefs)?

As for being up front about the expectations of play, that's certainly what I do now!  In a recent D&D3 game with strangers, I delayed the beginning of play by asking, "So, are we gonna be in tough fights where we really need to strategize perfectly, and the character stuff is take it or leave it, or are we gonna roleplay a lot and maybe hand-wave some fighty stuff, or some combo, or something else?"  The GM seemed surprised by the question, quickly replied "that second one", and everyone else nodded.  I think this helped the game.

That said, though, I think it's interesting how a lack of awareness of this issue can still be somewhat bridged by simple interest in each other's domains.  In Pitfighter, I really wanted the players to be excited about their characters, and the players really wanted to engage with my setting.  Our techniques to achieve that were sorely underdeveloped, but the will to try totally saved us.  "Dave seems stoked about these badguys, I guess I'll make a character who's got a personal angle on them."  "John wants to play a power-hungry character, let me tie my conspiracy to his town's government."

Roger,

Roger wrote:
Did you ever try revealing your plots to the players prior to play?

David wrote:
Jamie,
Totally agreed on Montsegur, though I'm surprised by that point about BE.  Isn't it part of the GM's job to engineer intersections between the characters' Beliefs and the Vaylen's agenda (via the FONs' Beliefs)?

Burning Empires is an interesting game.  I played one full phase a few summers ago.  The GM did indeed simply play his FONs to the hilt.  One of them didn't even know his actions were benefiting the evil Vaylen invaders! 

But there was also the FON who was clearly engaging in military schemes on the Vaylen's behalf, and there was the occasional color scene of some border guard getting hulled.  Without those, the sense of purpose and consequence and drama for the player characters' endeavors would not have been nearly as high.

I think there's a feedback loop: you get spooked about the Vaylen, you write Beliefs that you think will accomplish things to thwart Vaylen efforts (even though the rules don't distinguish between thwarting and non-thwarting successes), and then your Beliefs drive the content of play toward being concerned with the Vaylen.  I think this is vital.  If my power-hungry corporate character had been trying to take over the colony for purely selfish reasons rather than to save it from invasion, I think it would have been flat, and the other players would have cared about my scenes a lot less.

That kind of fragmentation is one thing my Pitfighter game steered clear of.  When you spend most of your time interacting with the GM plot that underlies the whole campaign, you're always going to have that larger context present, lending oomph and relevance to what happens.  It's aligning that oomph and relevance with player decisions that's been the tricky part.

Thinking back on earlier play, I think part of what inspired me to focus Pitfighter on a single plotline was previous disunity in other games.  Unconnected dungeons, solo side-quests, etc.

The fact that you can't just go ahead and directly influence higher-scale events in Burning Empires before all the Maneuver and Phase rules let you -- I see a parallel there to the fact that you can't unravel a Plot Situation Before GM's plot before they're ready for it. 

Both approaches need:

• clarity up-front about the rules by which the large scale is resolved (BE Phase mechanics, Pitfighter GM fiat)
• clarity about the constraints imposed thereby (no fictional outcomes can defeat the Vaylen before their Dispo=0, or defeat Dave's badguys before Dave's ready)
• participant willingness to help manifest those constraints in the fiction

That last point is a matter of personal perspective.  My friends who are veterans of Burning Wheel say they don't feel like they're playing to the mechanics, but it sure looks to me like they are, and I know I whiff a lot if I try to "just play my character".  To enjoy playing with them, I find that I need to look at mechanical facts as situational facts -- "Well, if the rules say I can't find this dude right now, even though I was just friggin' talking to him, then... I guess... ah, he must have darted into a side tunnel to sneak-attack the badguys!"  I suspect that my Pitfighter players overcame some of my awkward Force moments with similar mental efforts.  "The last pirate to leave the ship could have knocked some lantern oil onto a lit cannon fuse; that's why the boat's on fire!"

I actually don't find it more strange or difficult to extend the spirit of "I'm going to give this a good solid shot and see what it can deliver" to GM fiat than to a ruleset.  In either case, if it turns out to suck, I'll stop.

I've gotten awfully tangent-y here, but I think there may be some takeaways for the SBP design thing I'm working on.  If so, links shall follow.

If anyone wants to talk about the conclusions from my initial post, I'm still game.

Oh!  And here's another key to the degree of success I achieved with Pitfighter: respect character sovereignty.

Burning the boat and killing the NPC and laying waste to every path except the one that led to my story wasn't always good play, but, in my group, it was always preferable to mind-control.  The players always kept control over their characters thoughts, feelings, and attempted actions.  No amount of wanting to drive the characters toward my plot ever led me to start a sentence with, "You feel a sudden desire to..."

Having character sovereignty as an inviolable principle influenced my GMing greatly.  "It's not okay to just do whatever you want to make your plot happen" may have been the foundation of my will to improve my techniques.  Further, the idea that every character's mind was outside my jurisdiction meant that I didn't prep plot based on what they would think.  That's not to say I didn't make any assumptions about what they would think.  But most of my assumptions were stuff like, "They'll stay invested in saving the world even when it looks pretty hopeless," and, "They'll take the obvious route to Grey Island." 

I never based my plot plans on an assumption about a personally important or potentially character-defining choice or attitude.  No planning for Ben's character to sell the party out to the Mandragons (which he did) or for She-Dragon falling for Metalstorm (which she didn't).

For context, the system we used in Pitfighter was:
Formal: Basically AD&D2 combat, saves, skills, and advancement.  Except every 5 levels your weapon leveled up so I could draw some ridiculous 5-bladed sword or something, and you got an extra damage die.
Informal: Dave's running the show, but won't violate certain principles.  No mind-control, no deathtraps without warning, no violating fictional plausibility... probably others I can't come up with right now.