Review: Power-Ups 9: Attributes

Recently SJGames released GURPS Power-Ups 9: Attributes and my Patrons asked me to review it, so here's my review: Never have I seen a bigger mea culpa from a company, except perhaps White Wolf republishing their old versions of the World of Darkness.  But this should not be a mark of shame on SJGames; instead, the fact that this book exists should make you proud of SJGames. They have heard your endless complaining about attributes, listened, and offered up an entire smorgasbord of options you can use to fix them.

That might seem like an odd review, but upon reading it, that was the unshakeable feeling I had.  It felt like reading someone's commentary on a collection of threads about the problems with attributes.  "IQ is underpriced once you buy back Per and Will," "Nobody would ever buy a 15 point talent when an attribute is so much better," "There are too many skills!" "It doesn't even make sense that Basic Speed would be attached to HT!" "I liked how HP was handled back in 3e better" and so on.  In the past these sorts of things would have been addressed, typically by GURPS fans, as "Well, it makes sense because X" or "You're not allowed to buy that back because there's a hard disad limit" and other such defenses.  This offers no such defenses, though it does sometimes offer the context as to why a decision was made.  Instead, if anyone ever even thought of an objection to an attribute, this book attempts to address it, and other issues beside.  It rips open the entire foundation beneath attributes and exposes them, sometimes more than I would have ever thought necessary.

This gave me mixed feelings about the book.  On the one hand, kudos to Sean Punch. Seriously.  In my experience, the RPG world is full of egotistical authors that bristle at anyone questioning their genius, while Punch says "Oh, YOU DON'T LIKE HOW WE HANDLED ATTRIBUTES? That's cool, here's why we did it, and here's 50 ideas about how you could do it differently, and some tips on how to integrate those changes into the rest of the system." Amazing.  On the other hand, this claws at the thin tissue of lies that suggests GURPS is a "universal" system. If I start making changes this substantial to my game, is it GURPS anymore? Can you pick up your character from your GURPS game and come play in mine? On the other hand, could you ever?  I know some people tried that, with mixed results, with D&D games, but I don't think GURPS every really pretended to be universal in the sense of total compatibility between games, just total support for all genres.  In that sense, this makes it a great supplement.

I will say that unlike the other Power-Up books, this isn't something you'll reference. It reads more like a discussion, like an extended forum thread or a pyramid article, a guide on how to hack your GURPS game.  Once you've gone through it, you should have a pretty good idea of what it's about, and if you're putting together a new campaign, you might revisit it once and see if it has any ideas on how to handle an attribute in your game or if you find you've run into a trait problem.

I immediately began using it in the context of Psi-Wars, and it removed the last mental block I had to lowering the cost to ST.  It also generated quite some discussion as to whether we should change IQ and DX too, and this sort of underlines one of my core complaints about this book, though it's not the book's fault: a lot of what it suggests are so sweeping that if you implement them, you'll have to throw everything you've built so far out the window and start from scratch; worse, the book is persuasive, which left me feeling like I was running a sub-optimal game for running GURPS-as-written, which is probably the biggest... what's a word for an advantage that's also a disadvantage? In any case, by unflinchingly ripping open the guts to GURPS, it reveals a lot of problems you probably hadn't considered, and once it's been seen, it can't be unseen.  You'll be a lot more aware of the warts of GURPS after this book.  It's a book for the brave and for the game designer, not for the guy who just wants to run some campaign and doesn't care how good the rules are and he quite likes GURPS.

Meditations on Gear in GURPS

Recently I had an interesting conversation over on the Psi-Wars discord.  It started with my statement that I didn't want to see players "saving up" to buy better force swords, that I didn't want them buying "better force swords" at all.  This triggered an entire conversation on gear, RPG genre, and the reasons gear is treated the way it is in RPGs.

I've found myself pondering the topic a lot lately, especially in light of people requesting revisions to Psi-Wars' templates, to update them, and my increasing dissatisfaction with how gear is handled in Psi-Wars.  Why do we have gear in games? What purpose does it serve? And what can we replace it with?

What is "Gear?"

Before we go on, we should define some terms.  Gear is fairly obvious in GURPS: it's stuff you buy with your money!  I'm talking about "loot" in Dungeon Fantasy, or any equipment that you can pick up and discard. It's anything that enhances your character that he doesn't pay for with points, really.  It's an important distinction, for reasons we'll get back to (or may well become obvious over my meandering musings).

GURPS seems to have inherited its concepts for gear from D&D and the other games of the early era of RPGs.  This includes a starting budget for your character, a big shopping list in the book that you're expected to pore over for hours to find exactly the right gear, encumbrance to prevent you from carrying too much gear (thus, creating a decision matrix of effectiveness within a given monetary and weight budget), and scaling levels of effectiveness whereby the game assumes you'll give up your starting gear for better gear "later on."

These are the concepts I wish to discuss here.

The Frame vs the Game

Sometimes when I'm looking at my statistics, I notice that I'm getting a number of views from a particular source, such as a blog.  These are usually GURPS blogs (special shoutouts to Dungeon Fantastic, GURB and Let's GURPS for sending traffic my way) and I noticed one I hadn't seen before called the Disoriented Ranger. It seems my post on the Riddle of Systems triggered some thoughts from him.  It's not really a rebuttal, so much that the post inspired him.

The thing that inspired him is a comment I often make about "the game" of D&D being about "killing monsters and taking their stuff," vs other elements that other games do better. He wonders if D&D needs those elements and slides into a discussion on metanarratives and how RPGs are a sort of "controlled language," which is an interesting discussion.

But it did get me to thinking about how many people reject the label of D&D being "about killing monsters and taking their stuff."  He doesn't seem to, not explicitly, but I do think about it.  And while I was thinking about it, I came across an idea that I wanted to offer you to sort of show something I think is critical to understanding the bounds of RPGs, what they do, and why people often get into arguments about whether a game is "broken." It's a conversation about what the game of an RPG is, and what isn't "the game" of an RPG. It's an arbitrary distinction as you'll see, but it's useful for having a particular sort of conversation about RPGs.

"Who Gives a S**t?" A Meditation on Setting Design

Tons of people are doing settings, but that is kinda hard for me to wrap my head around. I love GURPS content, I love spells, powers, advantages, builds, encounters, adventures, but for me, a setting is kind of a deeply personal thing.
-Benjamin Gauronskas, Let's GURPS

Yes, that is the second time I've used that quote, but I think it's an important one.  It highlights a truth: Settings often aren't useful to people precisely because they are so personal.  A GM discussing his favorite, homebrew setting is often about as engrossing for the audience as a player discussing his favorite character.  In part, this is because settings need to be experienced.  What makes Star Wars fun is that you're there, watching the ships explode and the lightsabers clash.  What doesn't work is watching a couple of nerds sit around discussing the importance of the Bendu Priests in the founding of the Jedi Order.

The problem here is that we need to be able to connect with a setting, and we'll only do that if it's useful to us.  I've avoided going deeply into setting with Psi Wars because, for the most part, it won't be useful to you.  I get it: Most of you who are reading this are doing so to see how I build a campaign, or to rip off some rule idea I have, or because you're bored and want to read GURPS stuff. The majority of my audience will never run a Psi-Wars game.  That doesn't mean nobody will, but if I want to my blog posts to be as universally useful as possible, I need to make my posts useful to a broad audience: the casual reader, the inspiration-seeker, the crunch-head, and the psi-wars fan, and thus my posts have so far been generic and very meta.

The same principle must apply, itself, to setting design.  To make our setting interesting, we have to connect with our audience, and to connect with our audience, we must understand their needs, why they might be interested in a setting.  We also need to understand what a setting is. So, before I get into building any setting material, let's stop to consider the point of a setting, and who our audience is.

The Illusion of Mechanics

According to some, this is good art

According to some, this is not good art

I've seen a couple of posts that touch on a topic very near and dear to me when it comes to game design, not because I agree or disagree, but more that they enter into that arena and invite discussion on the topic.  The first is Creighton Broadhurst's Why Character Optimization Is Pointless (Unless You Enjoy It) and Christopher R. Rice's Building Player Characters To Concept.  The theme they touch on is the illusion of mechanics.  At their core, they say "Mechanics don't matter" Or, at least, these mechanics don't matter, but maybe those do.  And they also point out that this is a matter of taste.  As you'll see soon, I don't disagree with their premise.  This is not a rebuttal of their posts, but a comment on some larger implications, and what their perspectives on game design can do to inform your own perspective, even if you disagree with them.

Psionics and the Psi-Wars Framework

I've largely already addressed psionics in an Action framework in each individual post.  We can largely see where they fit into the above.  For example:

• Violence (Psychokinesis and Ergokinesis)
• Stealth (Telepathy and Psychokinesis)
• Superior information and/or planning (ESP)
• Social manipulation (Telepathy)
• Mobility (Psychokinesis)
• Technological Superiority (Ergokinesis)

Mobility suffers a bit, but that's because I want ships front and center to gameplay.

Beyond that, I'm largely not concerned about how well Psionic Powers will work because I believe that PK did his homework. PK is one of the shining examples of an author who understands frameworks, as can be attested by his work on the Monster Hunter and After the End series, thus I fully expect that not only will they work well with the Action framework based on the adjustments I've made, but they'll work well with one another.

That said, if a psionic, rather than classic, approach is going to work, it needs to provide reasonable power for a reasonable cost when compared to the skills and technology available to the average character: it needs to be a viable strategy.  For the most part, the psionics I've chosen offer the ability to do something that technology cannot, with a few exceptions (lightning blasts aren't really any better than blaster bolts).

My largest concern has been the considerable point-cost associated with Psionics.  A character can become pretty good at, say, information gathering with ~20 points worth of the right skills and the right technology.  An ESPer needs to spend considerably more than that to make his gift work, but his gift can offer much more than those 20 points.  To further off-set costs, I have introduced God-Like Extra-Effort.

Evaluating the new Power Framework

Cool ideas bro, but does it work?

Many RPGs that I enjoyed in my youth, I came to notice over time, are plagued by what I liked to call the "Cool Idea! Syndrome."  The writer needed to fill out a book full of cool powers, and they needed to inspire their audience, so they wrote neat ideas into their books.  What they didn't do was write a working system into their game.  It was enough that they had neat ideas, and they seemed to have stopped there.  The result were that some cool powers completely changed the game, or even wrecked it, while others seemed to do nothing at all.  We'd have arguments at the table, and the games would shortly end up shelved while we turned to more robust games (like GURPS!).

A good system is cohesive and builds interesting gameplay.  Players respond to incentives and they'll see that there's an inherent goal in your gameplay (Psi-Wars, imitating GURPS Action, has the goal of "Accomplish the mission"), and a variety of ways to get there (Stealth, direct combat, good social interaction), as well as a variety of possible stumbling blocks/challenges that could stop you from getting there if you can't beat them (while, ideally, keeping even failing gameplay interesting).  It does this by providing a clear ruleset that creates interesting interactions.  Raph Koster argues (if I may attempt to paraphrase an entire book) that "fun" in a game essentially boils down to experiencing unexpected emergence coming out of this clear-and-simple ruleset, and the feedback loop of learning to master that ruleset and its emergent behavior.

A good system should provide you with those things.  I could write an entire series on building gameplay (and someday I will), but you can already get a pretty good idea of what it looks like by reading Dungeon Fantastic or David Sirlin's game design articles or Raph Koster's Theory of Fun, etc.  Dungeon Fantastic touches on what I'm sort of talking about in this post on "plugging holes".

"Plugging Holes" examines some of the underlying implications of the framework created by the DF rules and how to deal with them regarding a particular goal (survival, in this case).  For example, a character needs to survive being attacked by a goblin with a spear, but he also needs to deal with death curses from a lich.  These require substantially different things, so different that players are often better off specializing in their particular niche and protecting one another.

But those niches aren't inherent to GURPS.  Kromm put them there, deliberately, with his design of Dungeon Fantasy, which Peter is exploring in his Dungeon Fantastic articles.  One reason people love "Kewl Powerz" is not just because it lets them be awesome, but because those cool powers create a framework for gameplay (Said differently, cool powers let players be awesome in a specific context.  You need both the cool powers and the cool context for it to work). When we create our own powerset, we're creating a similar framework full of dangers and strategies and interactions that the players can interact with and explore.  Ideally, we create one that promotes gameplay that fits our genre and design goals.

The question I pose to you is this: Does this design succeed at doing that?  Does it promote a world full of mystical claptrap that borders on fantasy, while also allowing high-octane gunfights and spy-vs-spy action?  For added tension, realize that Star Wars itself often fails at this particular dichotomy (gunslingers and spies are practically a joke in the prequels, almost completely overshadowed by mysticism and the fantasy elements).

Do we have a working framework, or do we have a pile of cool ideas?

The Riddle of Systems

I played in a Lord of the Rings Roleplaying Game once, and it was awful.  To this day I know not the name of a single NPC.  Every fight scene was an endless, and often malicious, deluge of relatively useless monsters, and the final "climactic" scene was so tedious that one of the players literally shouted "Get on with it!" at one point and everyone else at the table, but the GM, agreed with him.  When I asked him about it later, he agreed it was a terrible game. "The system was just shit." He explained.

"Yeah, that was the problem" I thought to myself, but smiled and nodded.

Another story, if you'll permit me: I've seen Fate Core discussions make the rounds, from complaints from GURPS fans that Fate Core doesn't do enough, to complaints from  minimalists that it does too much, that you need nothing but Aspects and Fate Points, that the game is driven by the Fate Economy.  I'm currently in a Fate Core game, and what struck me about that discussion is how little the GM uses fate points and aspects.  In fact, I'm the only one who does things like create scene aspects, spend my fate points, etc, and when people try to do the same, they look at me, rather than the GM for a discussion about how to actually deal with the mechanics.  When it comes to that specific GM, he runs the game the way he runs every game: He puts the book on the table, so we know what game it is we're playing, and then he tells his story and we respond and sometimes, once or twice a session, we'll roll some dice to add some uncertainty, and then go back to telling the story.

Sometimes, the game will go well.  "It's a good system," he'll say.  Sometimes, the game will go poorly.  "It's a bad system," he'll say.

I often see arguments over system.  Rifts, for example, "has a great setting but a terrible system."  The Old World of Darkness is some people's favorite system of all time, and they bristle if I point out that it's very broken.  D&D 4e is "too much like an MMO" and so on.  The general thrust that I hear in these discussions is if so and so could finally find the perfect system, then his games would finally work.  Everyone is on the look for the next supplement that will finally make their game work.  And if you show them something different, something new, they'll recoil.  "That doesn't work for me," they'll say.

Conan the Barbarian has an interesting concept called the Riddle of Steel. Let me pose to you the Riddle of Systems, and then answer it for you: Flesh is stronger than system.  What problem with your games isn't the system.  The problem with your game is you.

On the Cost of Advantages

Christopher Rice over on Ravens and Pennies is in full rant-mode regarding the cost of advantages, and he's right.  Go over there and read it.  Done? Great!  The only problem I have with his post is that, in my opinion, he doesn't go far enough.  I'll explain in a minute, but let me first shout "Hear hear!" for a bit.

Ken and Robin have a patreon

My dear and faithful readers, I haven't had the chance to get around to some of my favorite topics, like demonology or history or GURPS Cabal, but all of them have their roots in my misspent youth scrambling for whatever scraps of the Suppressed Transmission that I could get.  Kenneth Hite helped inspire many of my campaigns and I often quote him.

 At some point, I'll get around to my own Apprentice Consulting Occultist series. Lo and behold, on a great and joyous day, Kenneth Hite started a podcast with Robin Laws. Robin literally wrote the book on game-mastering and his excellence in tightly focused game design joins my pantheon of inspirations with Sirlin and Raph Koster's "A Theory of Fun" for how I work on and design my own games or campaigns.

 So, if you like my stuff, I recommend listening to them on Ken and Robin Talk About Stuff. And if you like their stuff, if I may finally get to the real point of this post, they've launched a patreon campaign. I've already bid my dollars in support of these giants of the RPG industry, and I encourage you to do the same. Thanks for your time, dear and faithful reader. I return you back to your regularly scheduled force sword duels.

Breaking Down a Campaign Framework

I'm always creating page after page of RPG material, but I seldom follow through far enough to create something truly publishable.  I'm always getting requests for my notes, and I always have to demure because they're really little more than "What is necessary to run my specific game." In a few weeks, I hope to change that record and kick out the first bit of an actual GURPS campaign framework.

That pre-amble out of the way, allow me to make a few definitions.  What the hell is a GURPS campaign framework?  It's what I've decided to call books like GURPS Dungeon Fantasy, GURPS Action and GURPS Monster Hunters.  They provide everything you need to run a campaign except the specifics on plot, character and setting (but further provides guidelines on all three of those). Said differently, a campaign framework provides a distillation of the GURPS rules necessary for rapidly building characters, sessions and interesting gameplay for a particular genre.

This blog post will break-down what I think a campaign framework needs, but to do that, you must permit me one more definition, and to make that definition, I want to show you another definition: Philip K. Dick's definition of science fiction:

I will define science fiction, first, by saying what science fiction is not. It cannot be defined as 'a story set in the future,' [nor does it require] untra-advanced technology. It must have a fictitious world, a society that does not in fact exist, but is predicated on our known society... that comes out of our world, the one we know:
This world must be different from the given one in at least one way, and this one way must be sufficient to give rise to events that could not occur in our society…
There must be a coherent idea involved in this dislocation…so that as a result a new society is generated in the author's mind, transferred to paper, and from paper it occurs as a convulsive shock in the reader's mind, the shock of dysrecognition.


[In] good science fiction, the conceptual dislocation---the new idea, in other words---must be truly new and it must be intellectually stimulating to the reader…[so] it sets off a chain-reaction of ramification, ideas in the mind of the reader; it so-to-speak unlocks the reader's mind so that that mind, like the author's, begins to create…. The very best science fiction ultimately winds up being a collaboration between author and reader, in which both create---and enjoy doing it, [experiencing] the joy of discovery of newness.

So, to be clear, Philip K. Dick doesn't think Star Wars is science fiction!  Does that mean that Mr. Dick is a... jerk?  No, I don't think so.  It doesn't mean his definition is wrong either.  It's not prescriptive so much as descriptive of what he's trying to do.  He's not being a snob, he's outlining a model that explains what he's shooting for.  "All models are wrong, some models are useful," as the saying goes.

With that in mind, I want to offer a definition of a role-playing game, not because I feel anything that falls outside of it is "not really roleplaying," but because it defines what I'm trying to create: A role-playing game is a confluence between the tension created by interesting mechanical gameplay and interesting narrative choices.  To unpack that: When people say they enjoy "fluff," they mean they enjoy the inspiration and complex choices created by an interesting narrative.  When people say they enjoy "crunch" they're describing their enjoyment of the complex choices created by interesting gameplay mechanics.  These two sides often argue, but I think they miss the point that RPGs are designed as the wonderful peanut-butter-and-chocolate mixture of rich narrative mixed with complex gameplay.

GURPS itself provides neither.  There is no GURPS setting and there is precious little GURPS gameplay (Nothing stops me, rules-as-written, from taking telepathy and ruining all the mysteries in a police procedural).  Rather, it provides us with the tools, the "design language" to create our own settings and gameplay (Nothing stops you, rules-as-written, from creating interesting consequences to the use of telepathy, and littering the world with dangerous psychics, anti-psychics, technological mind-shields, or drug-induced nightmarish "mind-traps." BOOM!  Interesting gameplay for a police procedural involving telepathy).  Many GURPS veterans have created rich campaigns all on their own.  But a campaign framework does a lot of that work for you.  You don't need one, but you're effectively creating your own, so why not build it out enough that anyone can use it?

A GURPS campaign framework defines the "fluff" of its campaign mostly in broad strokes.  The specific setting doesn't matter as much.  Monster Hunters works as well in Los Angeles as Cairo as the hills of Kentucky. But a campaign framework does depend on some setting conceits: Monster Hunters exists in a world where magic and monsters are real, monsters and magic works in a particular (and specific) way, and things like genetically engineered super-soldiers are real (though rare or secret).  Likewise, the specifics of characters are left to players and GM, but the framework outlines the details lightly.  Dungeon Fantasy has wizards, and wizards tend to have problems like being excommunicated or feared, while Knights tend not to have any actual, defined status, and so on.  Similarly, it doesn't really define the specifics of a plot, but you can infer what sort of plot you might have.  What a campaign framework mostly does is set up the premise.  Once the premise is established, then we can build gameplay.

And building gameplay is the primary focus of a campaign framework.  When I see people discussing these frameworks and building their own, they always start with templates.  This is a mistake.  Before you can build templates, you must understand niches.  Before you can understand niches, you must understand the pulse of gameplay.  The first framework book to write is always the second released: Dungeon Fantasy 2: Dungeons; Action 2: Exploits; Monster Hunters 2: the Mission.

"A game is a series of interesting choices"
-Sid Meier

To understand gameplay, you must pick a focus for that gameplay.  Said differently, when the dice come out, what are the players doing?  What sort of choices do the players make?  Good gameplay creates a series of interesting, interrelated choices that creates an emergent narrative that, ideally, emulates the sort of genre we're exploring.  A game meant to emulate a heroic shonen anime should have a variety of interesting tactical decisions that, when chosen in an optimal way, naturally result in explosive, emotion-laden power, tangled relationships and exceedingly dramatic and dynamic battles full of people flying around and blasting each other.  A game meant to emulate Game of Thrones should have interesting choices that result in betrayal and heroes bleeding out in gutters while cynical villains slip back into the shadows to win a morally-grey victory in an uncaring, medieval world.

The first step, then, is to focus on a mechanics mission statement.  What do the player characters do by default?  Kill monsters and take their stuff?  Conspire to hide magic from the world while advancing their own political and mystical power?  Seek out new life and new civilizations while boldly going where no man has gone before, followed by sleeping with new women and punching out new alien warlords?  Once you have that, the next step is to pull out additional detail in our gaming fractal.  Killing monsters and taking their stuff, obviously, involves at least two parts, the killing and the taking, and might infer a few more, like knowing which monsters to kill, or where to find the stuff.  After we pull out these elements, we can keep or discard as we please.  Taking a monster's stuff likely involves selling it, but most players don't associate mercantile skill or deep haggling mini-games as a serious element of Dungeon Fantasy, so we remove that.

Once we understand what our game is about, we can start building the actual nuts and bolts of gameplay.

Obstacles consist of four things: Dilemma, Choices, Consequences, and Rooting Interest.
-Robin Laws (Paraphrased)

Once we know where are gameplay is, we need to decide what it looks like.  Gameplay will generally consist of facing what Robin Laws, above, calls obstacles.  The most important elements are, to me, the last three, and starting with the last first: Rooting Interest means you must explain why the heroes care.  Dungeon Fantasy does this easily by pointing out, helpfully, that the monsters have stuff and you want stuff.  Moreover, the monsters are trying to kill you and most people are interested in not dying.  Games like GURPS Action have a harder time establishing rooting interest, and tend to require fluffier reasons for doing what they do.  Nonetheless, there should always be a benefit for success, or what some people in the biz call "Risk vs Reward."

“Failure is boring – the credible threat of failure is very exciting.”
-Amanda Lang

Next, we need our series of interesting choices.  This ties in with consequences.  There must be multiple ways to achieve one's goal, and they must all be equally interesting (this is what game designers mean by "game balance"), but that doesn't mean they must all be the same.  Different tactics should involve different risks and different, long-term consequences.  Those consequences can be short-term or long-term or both, and the consequences needed necessarily be negative.  Much of chess's gameplay choices turns on positioning: to capture your piece, I must move my piece to the captured piece's spot.  This fundamentally changes the board, and might expose my piece to counter attack, or open up the field for further attack against you.  D&D 4e and Gumshoe use resources, which means you can expend a great deal of power to defeat a threat now, at the cost of being unable to defeat another threat later on.  Call of Cthulhu allows magic at the cost of sanity, which means the use of game-winning powers will likely result in a permanent reduction of your hero's power.

Ideally, our choices involve several of the above, allowing the heroes to way the risks against the rewards and the potential fallout of a course of action, and those consequences shape future choices (This is the "sequence" that Sid Meier refers to).  This creates our emergent play.  As my D&D fighter rushes forward and lays down an area attack on several foes, this has the consequence that I'm no longer near the other PCs, but all of those enemies have been effectively "pinned" near mine, which keeps them from attacking my allies, but means they're highly likely at attack me, which might be dangerous to myself.  I've made a choice, and gained both rewards and consequences that will affect the next turn (My position, my expenditure of a resource).  The enemy will react to my new position and my new vulnerabilities differently, which means I may be swamped by enemies, or might have them scatter.  Then, I have a new set of choices that didn't exist before, limited by the fact that I've already expended some of my power (a condition that didn't exist before).

Once we've defined those choices, we can determine which traits interact with them and what general paths our choices tend to guide us along.  A combat character who tends to focus on strategies of survival and focusing enemy attention on him is following a "tank" strategy.  That's his core toolkit, the set of choices he intends to maximize.  A combat character who intends to focus on removing his opponents before they can remove him is following a "striker" or "sniper" strategy. From these strategies, we can start to derive our niches, and from those niches, we can derive our templates.  And from our templates, we can write a template book.

This works because we have determined what makes each core game mechanic interesting, and how these templates interface with them, and what traits matter and why.  Monster Hunters, for example, has two major gameplay arenas: Finding the monster and killing it.  Each template has alternate strategies for finding the monster, and each template has means by which to kill it, and these overlap.  The Crusader has just enough skill to find the monster, and then has overwhelming lethality with which to destroy the monster in a full, frontal assault.  The sage, on the other hand, prefers to linger in the research phase, trying to determine what the monster's weakness might be and use that against him.  Both can team up to allow specialization and magnification of one another's strengths, but this too creates new vulnerabilities, and doesn't address additional issues and potential consequences (Remaining hidden from both the world and the monsters you hunt is a vital part of monster hunting, and requires a different strategy).

Once we've built our core gameplay, all that remains is to make sure it's attached to the rooting interest of the players themselves.  Base motivations can work, but tying everything into a deeper narrative is what makes RPGs far more compelling than mere Monopoly, Parcheesi or Stratego.  But that's an article for another time.

The Three Things an RPG System Provides

RPG.net another RPG communities abound with commentary on the "real purpose" of RPG systems, which are "good" and which are "bad," and what one needs to craft a well-designed RPG system.  Many of these arguments, it seems to me, stems from not just from conflicting views, but conflicting definitions and conflicting needs.  After all, what Mary Sue gets out of an RPG might be different than what Bob gets out of a game, which might explain why she thinks D&D 4e is great, and he thinks she's mad.

After years of listening to the commentary and studying different systems, I've found three elements that an RPG system can (but doesn't have to and doesn't always) provide, and I think the arguments between the unknowing proponents of these three things explain many of the contradictions found in RPG tastes.  Before I begin, I want to make a few things clear.  First of all, these elements are provided primarily by the system.  RPG settings and fluff play a distinct role too, but for the purposes of this discussion they're of secondary importance, namely providing a support role to the system. Any well-established publisher can tell you about the importance of excellent artwork, marketing, layout, editing and writing in the selling of his product, but we're just discussing game-design here.  Second, unlike some other theories, this isn't about "flavor," and these three elements are not mutually contradictory.  Some games place a greater emphasis on one or another, and not every game has all three, but games can certainly contain all three if they wish, and not every gamer needs all three.  This is not a case of "Which sort of gamer are you?" but "Do you like this element? Yes or no?"

1. Systems provide a social contract.


Social Contracts have become a bit of a buzzword among RPG designers, but I think that's appropriate, as they're a key element of game design.  A social contract is an agreement, unspoken or otherwise, on the appropriate behavior between the players (including the GM) and the game.  These might include elements like:

• "The GM's word is law"
• "Let the dice fall where they may"
• "No PC will die meaninglessly"
• "The story matters more than anything else"
• "Everyone brings a snack."

These can extend quite broadly, and where an RPG's social contract ends and a group's social contract begins is often hard to define, but (for example) few RPG systems will dictate that every player should bring a snack, but they might dictate that PCs will not die meanginlessly.

In this context, I mean that an RPG system needs to help the players define their setting, characters and rules of play in clear and well-defined terms so that everyone is on the same page.  When RPGs say things like "Rules are a conversation between players and their game master," or "the rules are there to prevent arguments about who shot whom when and who would win a fight," they're referring to social contracts.  In a well-designed system, if I define my character as "the greatest swordsman in the world," then he should be the greatest swordsman in the world.  This fact should be clear to me, to the rest of the players, to my game master, and in the narrative.  If this sort of design isn't possible (for example, it violates the premise of the game, which might involve relatively simple people, or a setting where swordsmanship isn't particularly important), a well-designed system will make this clear to me, directing me in a more useful direction.  In a poorly-designed system, I may discover that, in fact, my "world's greatest swordsman" isn't all that great, or the GM and other players might not realize what I'm doing and be utterly surprised when my character devastates a group of enemies that the GM thought might be a challenge.

I've stated that all of these elements are optional, but this one isn't.  A game without a well-defined social contract always falters and creates a toxic environment for players trying to create a shared imagination-space.  While few players actually discuss "bad" RPGs as failing in regards to a social contract, such games inevitably create controversy and strife.  Such games can be enjoyed, but only when a strong game master or group replaces their social contract for the one provided in the game.  Arguably, every group should be willing and ready to provide their own social contract on demand, and thus a flawed social contract often goes unnoticed, but a game should still try to provide a clear vision of its goals and premise, and it should stick to said vision.  It must remain consistent throughout its execution, to prevent arguments amongst players.  While a game master can replace such a social contract, doing so puts extra stress upon the GM and suggests that the book itself might not be worth the money paid for it, while a well-defined social contract has no downsides.  Often, when you hear people complain about roll-playing vs role-playing, or complaining about "twinks" or the like, they've often had a bad experience due to a poorly-crafted social contract system.

Nobilis exemplifies a system with a top-notch social contract system.  The core of the system revolves around writing out the rules of how you see your character working down on a piece of paper, and manipulating those social contracts to achieve your ends.  The entire game, from character creation to the evolution of the story, revolves around discussing the implication of the rules set forth explicitly by players and game-masters.

Vampire: the Masquerade is a fine example of a system with a broken social contract system in that it has rules and attributes that violate their stated premise.  The Conscience mechanic, in particular, creates a contradiction between what it says it does and what it actually does: In principle, a character with a higher Conscience refrains from committing wicked deeds because he has a good heart, according to the description of the trait.  In practice, Conscience acts as a savings throw against losing one's Humanity when committing vile deeds, and thus characters low in Conscience are punished more harshly for committing wicked deeds (and thus less likely to do so), while high Cosncience characters are punished less harshly for the same, creating the exact opposite effect: Conscience is defined as a trait possessed by those unwilling to commit wicked deeds, but is best taken by those willing to commit wicked deeds.  This sort of mismatch between description and mechanic captures perfectly the problem with broken social-contract systems.

2. Systems provide inspiration

Game-masters and players have but a limited scope of creativity and imagination.  RPGs provide a unique experience by combining the creativity of the players, the GM, the vision of the developer and the emergent properties of the system to create a story and a sequence of events that none of the above would create on their own.

RPGs can provide inspiration in numerous ways.  Dice and cards provide random outcomes.  Systems encourage and punish certain behaviors, thus shaping play.  The interaction of simple systems and small choices create unexpected, complex results.  Beyond that, a well-written and a beautifully illustrated RPG can inspire stories and character concepts that might not have arisen from the group without outside assistance (thus blurring the line between fluff and system in this case, though the system needs to reflect said fluff, but see point 1 above).  More directly, some RPGs even offer charts filled with events, brutally descriptive attack results, or random characters, or even write your stories and characters for you.

Unlike social contracts above, this element isn't strictly necessary, though most RPG systems include at least a random element to encourage unexpected results that surprise everyone involved.  A system that provides a great deal of inspiration saves the game master a great deal of creative effort and can surprise everyone involved, for good or for ill.  This means such systems can have the drawback of unpredictability, taking some control out of the hands of the GM or the players, or creating unexpected results.  Most games get around this by making such randomness optional and giving players and the game master the ability to impose their vision over random events, if they see fit.  On the plus side, a very inspiring system can make up for weaknesses elsewhere.  Many of the most broken games I've seen have a steady following based on the sheer beauty of their artwork and the way in which the character concepts or the setting speaks to the players.  An inspiring system can be a powerful tool, in the right hands.

When players discuss systems with poorly-implemented or absent inspiration, they often use terms like "boring" or "front-loaded."

Maid exemplifies inspiring systems.  It has random character creation, random events, random story seeds, and charts and charts and charts of random tables for just about everything. As a result, one can sit down with absolutely nothing and have a game up and running in 10-30 minutes.  In another direction, Exalted offers a distinct and evocative setting and character concepts, with elements like Limit Breaks, Willpower and Stunts encouraging unusual behavior, unexpected events and descriptive gameplay that might not have existed without the rules within the book.  Everway represents a relatively simple, diceless game that nonetheless manages to create unusual situations and inspires with its Fate Deck.

Opinions will differ hotly on uninspiring systems, but I find Wushu and nWoD's combat system particularly uninspiring.  In the former, your skills and character descriptions matter little beyond the bulk of your word-count, and you simply roll until you're done rolling, meaning that neither the dice nor the rules do any of the heavy lifting when it comes to telling a tale.  The new WoD has a similar problem in combat, with most choices and tactical options representing a waste of time, and most combat boiling down to the superior combatant winning, the randomness of the dice changing nothing except "by how much did he win?"

3. Systems provide gameplay

This element provokes the greatest contention between different views on RPGs, in my experience, particularly since the word "game" is nebulous and poorly defined.  Many people use it to mean a pleasant and unpredictable pastime, which RPGs certainly are, but in this context I'm referring to specific scenarios with win/lose conditions and a sequence of interesting, varied choices that shape your ability to win or lose, where the quality of the game is often determined by the scope of the options you can explore.  Simple games, like tic-tac-toe have a narrow scope, quickly mastered, while complex games, like chess, have a much wider, and more "interesting" scope.  In this context, gameplay is a celebration of system for its own sake.  Gameplay explores the options and abstract ideas laid out by the system.  When players discuss "min-maxing," "game balance," "crunchy," and "builds," they're usually referring to the gameplay element of the system, most often combat (which is usually the core "gameplay" element of most RPGs).

To be explicit: This element is not necessary for a good RPG.  One can have an inspiring game with a very clear-social contract where one player takes on the role of an elite swordmaster, and the other takes on the role of his halfling man-servant, and it's quite possible for both players to enjoy themselves.  You include this element explicitly for the enjoyment of people who like messing with gamplay.  It's a genre like any other, and as such is subject to tastes: Some people like romance and some people do not; by the same token, some people like crunchy, detailed gameplay, and some people would rather just tell their story.

The most abused and misunderstood aspect of this element is the term "game balance."  Game balance exists to ensure that the many options offered to achieve win conditions have equal applicability, provided one uses them correctly.  If a game has only one or two winning strategies, then the game quickly loses its appeal.  Game balance ensures that multiple perspectives and approaches allows for a dynamic and unexpected experience, thus maintaining the interest of the players.  Said differently, "game balance" is about balancing alternative gameplay strategies against one another.  It's not about anything else.  

For example, game balance does not apply to "inspiration."  The elements in a random chart do not need to be balanced against one another.  There's nothing TO balance, since their sole purpose is to provide interesting ideas to the GM and player.  Balance might be required in the sense that everyone gets to draw from the same deck, roll on the same charts or roll with the same dice, but this returns us to our gameplay concern of ensuring that gaining access to the "right" deck, chart or cards doesn't short-circuit the gameplay that the players are exploring.  

This applies to social contracts too: Some would-be designers argue that "game balance" is about equal air-time, but a moment's reflection shows this isn't true: Nothing in a system regulates how much of the plot revolves around a character, or how often a player is allowed to speak.  Some argue that it means that all PCs should be equally awesome, but if the "awesomeness" of various character classes is clearly defined, then players might willingly choose "lesser" character classes because they wish too.  All a well-designed social contract needs to do is carefully outline what the player is getting himself into.  Moreover, "awesomeness" generally applies to the "core conflict" of a system, the win/lose conditions as outlined in the gameplay, and thus this returns us once more to our "Systems provide gameplay" concept.

Likewise, when players discuss how "broken" or "imbalanced" a game is, they often mean this element, referring to poorly-designed gameplay, though "broken" can sometimes refer to a lack of proper social contract.

A game with well-designed gameplay has a clearly defined set of win/lose conditions, not necessarily in the classic sense of "if you lose, you're out of the game," but in the sense that players will have a goal that they're trying to achieve with the design of their characters.  Moreover, such a game will have multiple, alternative strategies to achieve this win-condition, and will provide "interesting" choices.  This final is, necessarily, subjective, as good game-design is an art, not a science, and is thus subject to taste, as any art is.  Some people prefer simplistic gameplay, while others prefer complex.  Some prefer resource management while others prefer playing the odds.  This article is too brief to go into the full depth of game design theory, but a good primer might be a Theory of Fun by Raph Koster.

D&D 4th Edition exemplifies the sort of game that centers itself around gameplay.  It establishes as its core win/lose condition "killing monsters and taking their stuff," and centers all the player's choices, from their class to their race to their feats to their choices in the midst of battle, around this central conceit.  Arguably, it does this to the exclusion of all else (particularly inspiration, as it provides precious little support for events or ideas outside of dungeon crawling), but such games don't have to work that way.  Legends of the Wulin has a similar laser-like focus on combat (in this case, on kung fu duels), but provides considerable support and inspiration for evocative games via its Secret Arts and Lores systems.

Scion might exemplify a game with terrible gameplay, depending on how you interpret its design goals.  If one views it as a game about super-heroes of modern-myth fighting Titanspawn, then its gameplay elements quickly fall down, with certain strategies far outshining others, with gameplay elements existing (seemingly) solely as traps for the inexperienced, and with advancement dictated by one's willingness to spend experience on a single trait (Legend).

Bringing it all Together

What makes up a well-designed system necessarily varies from user to user, depending on their personal tastes, but I think most of the best-designed RPGs contain the above elements in some degree.

• A well-designed system must have a clearly defined premise and it must remain consistent throughout its explanation of its rules.  Traits and mechanics should do what they say they do, and the game must clearly communicate with its readers, so that all the players of the game have a similar understanding of what to expect from teh game.
• A well-designed system often provides inspiration to the game-master and player, usually by creating emergent gameplay through a mixture of tactics including randomization (dice, cards), a system of rewards and punishments to shape player behavior, and an evocative and inspiring setting.
• A well-designed system may provide unique gameplay centered on a series of interesting choices that a player makes in an effort to achieve a win condition and/or avoid a lose condition.  These choices should be sufficiently varied and balanced to maintain the players interest throughout (at least) the extent of the campaign.

These three elements are distinct, and while they can help one another (well-explained and consistent rules are a boon for explaining complex gameplay as well as establishing a social contract), they require different things and each pursue different goals.  Other than well-written social contracts, none are strictly necessary, but neither are the elements mutually exclusive, allowing a skilled game-designer to include all three, should he wish.

Lady Blackbird Extended

So, with Cherry Blossom Rain out of the way, what is my next big project?  Well, some time ago, I discovered Lady Blackbird and handed it to Bee (Go ahead and look at it.  I'll wait.  Done?  Great!).  In my experience, Bee doesn't want to plan a session.  She hates that!  She just wants action and adventure and awesomeness now.  She comes to a game with vague ideas of what she'd like to see happen, and then she simply lets the pieces fall where they may, improvising with her players to guide them to her scenes, but if something else awesome comes along, she plays with that too.  She doesn't like to play systemless, though.  She enjoys throwing the dice and seeing how pretty they are, relying on unusual results to feed her story and, in a habit she picked up from 7th Sea, she loves to hand out drama dice or action points.

Lady Blackbird is perfect for this.  All of its rules are literally printed on every character sheet, and Bee, as GM, needs to know none of them.  All she needs to know are these three rules:

• The difficulty of the roll is between 1 and 5 "successes."
• If players fail, she has the option of hitting them with one of the 7 problems listed on their sheet (Hurt, tired, lost, etc)
• She can hand out drama dice in the form of a pool of dice players can use to boost their rolls (actually, that's not a rule, but Bee does it anyway, and it works well with the game).

That's all she needs to know.  The players take care of everything else on their own.  Even better, the game is, in fact, a standard adventure that she can play through, complete with suggested difficulties for various problems the players might encounter.

However, if you want to do anything but run the game with those 5 pre-generated PCs, or do an adventure other than that listed in the book, then you're basically on your own.  Thus, while Bee loves the system because it suits her so well, she has no interest in tearing apart the mechanics to make her own characters or to create her own adventures (she's refined the art of the lazy GM, and lazy GMs do not redesign systems from the ground up).  So, I'm going to do it for her.  I promised this as her birthday present, which coming from a published writer, is worth quite a lot ^_^

You know, presuming I actually finish.

Now, I'm not the first one to try to expand Lady Blackbird.  The writer himself took a stab at it, and other people have done their own work, but I think most of them are going about it in the wrong way.  Lady Blackbird has a few key features that appeal a great deal to its audience.  

First, it's very simple.  You don't have to shuffle through a giant skill list to figure out how to make your character.  This is the first place I think the Lady Blackbird Companion goes wrong: It lists every Trait its writer could come up with alphabetically.  How are you going to build a character like that?  Will you sort through the entire book, looking for something to build your character?  

Second, Lady Blackbird doesn't really describe its setting.  John Harper very cleverly gave us some common tropes, and then implied the rest of the setting.  He tells us in a few paragraphs that the world is shards of land orbiting a pale star, and instead of space, we have sky, plied by steam sky-ships.  Beyond that, we only know there are imperial nobles because Lady Blackbird is one.  We only know there are slaves because Naomi is an ex-slave, and we only know about goblins because of Snargle, and we only know about Flamebloods and Sky-Squid because they are mentioned in the potential challenges.  The Lady Blackbird Companion tries to fill in the blanks for you, but the whole point of Lady Blackbird are those blanks.  Do we really need to know, say, the culture of the goblins?  We can guess well enough on our own, thanks.

Finally, the real beauty of Lady Blackbird is the fact that it already includes all the challenges you need to run your adventure, and these challenges double as scene-seeds.  Because it includes the challenge rating for a fight against a flameblooded sorceror, you find yourself pondering how you might get the players to a point where they would battle a flameblooded sorceror, for example.  None of the works I've looked at (which, granted, hasn't been exhaustive) do this.  Instead, they expect the GM to come up with all of that on their own because most people who are writing Lady Blackbird material, other than the original author, come at this from a work-intensive, traditional GM perspective.

So, we're going to take a two pronged approach to our task.  First, we're going to research the traits, tags, keys and secrets, cobble together our own, and create a list.  Unlike in the Companion, though, we're going to sort them by categories: Professions, Qualities, Backgrounds, Magic and Races.  That way the player can look through, for example, the profession list to find what his character's job might be, the backgrounds to explore what his history is, and round him out with a few Qualities.

Then, we're going to make challenges for everything I can think of: Different regions mentioned in passing in the book, The various houses, the different kinds of sky-ships, the different races I come up with (including Goblins), the various conditions the book lists on the character sheet.  These challenges will be sorted together in themes.  For example, I'll find a large, beautiful picture that might represent Nightport, then create a list of challenges that one might find in Nightport, with possibly a few keys, secrets and traits that might be unique to Nightport.  In this manner, I'll offer the reader not only the potential skeleton of a story, but I'll also tell him a great deal about Nightport implicitly, rather than explicitly.  That is, by reading the challenges associated with Nightport, he'll get an idea of what Nightport might be like.

In this way, players should be able to construct their own characters quickly, and Bee should be able to simply flip the book open to some interesting part of the world or some interesting concept, start grabbing challenges, and just run the story.  If I play my cards right, it should be the great book of pick-up games.

GURPS: Create! Don't Convert!

A fond pastime of many GURPS-heads is the famed conversion: Take your favorite game, or better, your favorite book or movie.  I've mentioned before that I'm no fan of this process, and I think it's a waste of time.  Since I've picked up Dark Space, I thought I'd expand on why I feel that way:

• Impossibility of Accuracy: As Byler pointed out once, you can't possibly get the feel of 40k correct because even the source material conflicts.  In the fiction, Space Marines are gods of war, each requiring anti-tank weaponry to defeat.  In the tabletop game, anyone with an assault rifle can take them down, it's just harder than taking down a normal soldier.  While this is a glaring example, the same holds true for many sagas, whether it's Star Wars, Aliens vs Predator (remember when a single Alien was a big threat?  And then, in Aliens, it takes swarms to take down 5 soldiers?), the Matrix, the Wheel of Time, or whatever else it is you're interested in.  Thus, no matter what you do, you'll always have someone who disagrees.  So why stick to the inconsistent source material anyway, when you can make your own?  Nobody will look at the knights of Dark Space and say "That's not the way they're supposed to be!"
• Simplicity of Rules: 40k uses an entirely different ruleset than GURPS does, with different assumptions.  The same can be said of other games, like D&D or Rifts.  Trying to convert them over quickly becomes a headache for entirely different reasons.  Rather than worrying if a bolter is exactly right, it's much easier (better!) to simply grab Gyrocs with HEMP rounds and call it good.  In a conversion, someone will complain.  In a creation, nobody cares, and you're free to use the material that's already there, making things easier and faster.  Rather than fighting GURPS, you use its strengths to your benefit
• Beg, Borrow, Steal: When you convert, you must slavishly stick to the source material, taking the bad with the good.  When you create, you're free to do your own thing.  40k is a terrible RPG setting, because it's designed as a tabletop wargame.  Space Marines simply don't go adventuring!  But, in Dark Space, I can say that Knights do.  I can also completely change the aliens you face, bringing elements from other genres and stories I quite like, making Dark Space less "Fantasy in Space," and more "Transhumanism with Medieval Overtones."
• Enjoy the Adulation of Friends: If I published GURPS 40k, Games Workshop would sue my pants off, and rightly so.  If I publish GURPS "It's totally not 40k," it's much harder for them to claim that I'm stealing from them, because I'm not.  I've allowed myself to be inspired, but I've done my own thing.  And, as a result, I can not only publish, but people will enjoy the unique twists I've placed on my material.  It's true, I lose some name recognition, but you immediately gain that again when you slap "Inspired by" on it.

Emergent Narrative and the Problem with MMOs

So, whenever players start to argue over which RPG is better, invariably someone claims whichever game is more "Fun" is the better game, and then someone demands to know what "Fun" means, and invariably, people claim that fun is too nebulous to define.

I think that's bollocks.  Raph Koster, in his "A Theory of Fun" defines fun as "a learning experience."  Sid Meier describes games (which are presumably fun) as a "Series of Interesting Choices."  I like both, but I'll go further and put both together: Fun is the interactive study of emergence.

Humans like complexity.  We like it in our music, our art, our poetry and our humor.  When something is too simple, we quickly grow bored of it (a stick figure), when it's too complex, many of us can't comprehend it, and it becomes gibberish (Picasso, who often did things like attempting to convey 4 dimensions on a 2 dimensional surface).  The ideal varies from person to person, but we want to see as much complexity as we can comprehend unfold before this. This is the core of what Raph Koster was trying to say in his book, and "a series of interesting (interactions)" is precisely what creates emergence.

All good games have good "mechanical" emergence.  Consider Weapons of the Gods.  In every turn, you have many variables to contend with.  Your martial arts interacts with your opponents martial arts.  Your chi values vary, forcing you to change which style you favor.  Your river rises and falls, forcing you to make new choices.  The patterns constantly change, forcing you to adapt.  You don't know for certain what will happen next turn, but being able to predict it is the key to winning, so you struggle to understand.  That is, you have fun.  The same is true of D&D, GURPS, Yomi, Chess, Go, and so on.  It's not true of World of Darkness, as you can generally predict what will happen during any extended roll (for example, combat), so it stops being interesting and becomes the mechanical equivalent of a stick figure.

So why would people play WoD?  Or, worse, Risus, Wushu or others?  Partially, some of these players are very simple.  They take delight in simplistic games, like Tic-tac-toe and Hangman.  Large books filled with rules and complex interactions scare them, the way Picasso scares most of us.  But others, the majority I'd say, would argue that "mechanics get in the way of a good story!" which is certainly a sentiment I disagree with, but actually the point of this post.  RPGs provide another form of emergence: Narrative emergence.  In addition to having fascinating mechanics, most RPGs have fascinating, complex stories.  Through a series of simple choices, the players find themselves lost in a world of intrigue.  The princess in love with the hero cannot marry him because she is betrothed to a wicked man that the hero cannot (should not) kill because he is the key to defeating the dire Necromancer who is, in turn, a life-long friend of the hero, and interested in supplying the hero with power and aforementioned princess!  What's a hero to do?  We struggle through the interesting patterns of the narrative which, because it stems from the players themselves, seldom becomes too complex or too simple for a group's enjoyment.

From this, we have "roll-play vs role-play," the enjoyment of tactical emergence vs the enjoyment of narrative emergence.  D&D encourages a great deal of the former and little of the latter, while WoD is the reverse.  I personally don't see why both can't coincide, and thus I enjoy WotG.  Many indie games follow suit.

MMOs and CRPGs generally excel at tactical emergence. They offer us complex systems and encourage us to unravel them.  City of Heroes and Dragon Age have hundreds of possible builds.  Most MMOs rely on an interesting mix of characters, and limits the number you have going in, requiring group and tactical (in a more classic sense of small-unit combat) management.  They tend to fall down on narrative emergence, though.  Final Fantasy and World of Warcraft has the same story every time you play through it.  Mass Effect and Dragon Age have some flexibility, but I'd be hard pressed to call  it true emergence.  The closest we see to true narrative emergence in a computer game tends to come from simulation games, like the Sims, which often have unsatisfactory narratives as they fail to follow "dramatic" conventions (which matter just like artistic conventions matter.  People enjoy particular tropes.  Simply randomly dropping lines and shapes on a canvas does not generally create beautiful art, and randomly generating events does not create interesting stories.  Stories follow rules, just like art does).  A few RPGs try to get around this by being more simulationist: most of the Ultima games and Eschalon try to do this, but in the end, their stories are the same each play-through as well, and the simulation just leads to funky tactical emergence.

Thus, this is my goal: to find a way to create narrative emergence in a computer game.  It must be different every play through.  It must have a series of interactions that result in ongoing fascinating complexities for the player, and they must have a general shape that is appealing to the player (the Heroic Journey, for example, and romance should feel like romance).  I can see now that I've been trying to create this for a long time in my previous games, and, in an epiphany, I finally have a name for what it is I'm trying to do.

Yomi

I've followed Sir Lin for quite some time now. He's probably the best game-design theorist I've ever read, and if you care anything about game design, I think you owe it to yourself to check him out.

One of the coolest things he's discussed has been "Yomi," which means "reading your opponent's mind." Any skilled gamer knows that understanding your opponent's thought process is a sure way to victory, and the struggle to understand him is one of the great pleasures that makes gaming fun. Is your chess opponent bloodthirsty or defensive? Is the guy across the table from you at the poker game bluffing or not? Coming out of the blocks, will your DoA opponent go straight for an attack, will he block, or will he grapple?

The classic "Yomi" game is probably Rocks-Scissors-Paper, but while many game designers grasp this intuitively, they fail to understand deeper meanings behind this idea. Rocks-Scissors-Paper is essentially random, since it doesn't really matter what you choose. There's no "strategy" behind the choice, and the choice isn't "interesting." You could achieve equally good results simply rolling off against one another. But, as Sir Lin points out, if you make a certain move more valuable than another, you suddenly create an interesting game.

Try it: Play Rock-Scissors-Paper to 8 points. "Rock" is worth 2 points, the other moves are worth 1 point. Suddenly, Rock has a "center of gravity" that draws players to it. If you can use Rock, you should. However, given that Rock is the most useful move in the game, Paper becomes an obvious choice, because your opponent is so likely to choose Rock. However, if Paper becomes an obvious choice (due to the fact that everyone is trying to beat the guy who simple-mindedly picks Rock), then scissors becomes the killer app. Of course, if you use Scissors, you leave yourself vulnerable to an opponent choosing Rock.

What kind of person is your opponent? Is he straight-forward and prone to brute-force solutions and thus likely to choose Rock? Is he thoughtful and aware of the game enough to realize that Paper is likely the better choice? Or is he a gambler and likes to "run with scissors?" You need to understand your opponent, and suddenly a simple, random game becomes a complex game of psychology with just a single rules change.

Sir Lin has turned his love of Street Fighter and this idea of "reading your opponent's mind" into a card game called Yomi. Check it out! You can play it on Lackey using the guide here (Hey, who knew that a system designed for illegally playing Magic online would have such a fun, legitimate use). Roomie and I have been playing (He likes Satsuki, and I'm partial to Geiger currently). Give it a shot, let me know what you think.