Saturday, November 3, 2012

The Queen Needs No Advocate

http://youtu.be/h2N_OMp3T8I

In my career, I've been fortunate to spend a great deal of time involved in system design.  Much of that time has been spent implementing or modifying established systems (e.g. Dungeons & Dragons and Fallout's SPECIAL system).  Before I was employed in the industry, I spent a lot of time developing my own tabletop systems and modifying the systems of others, so this has always been something I've enjoyed doing.

There are many pitfalls to system design and I believe most designers trip those pitfalls by moving into implementation details too quickly.  I believe some keys to success in system design (and for design in general) are to establish clear goals, to frame what those goals will accomplish in terms of player experience, and to continually return to those goals and player experiences to ensure that nothing was lost in the details of implementation.

I believe the most well-executed systems are ones where thoughtful players can accurately discern the designers' goals simply by scrutinizing the systems in action.  Though not all players need to be able to do this, the ones who care to do so should be able to.  Designers who succeed in creating systems that can be "reverse-engineered" in such a way have captured the soul of elegance in design.

I sometimes look to traditional games for mechanical inspiration.  One of the ones I think of most often is chess.  Clocking in at over 1,000 years of play around the world, chess has had a lot of iteration time.  I'm not an expert on chess strategy and I'm not a particularly good player, but I know chess well enough to take some simple lessons away from it.  Two that I often rely on are lessons of obvious value and orthogonally equivalent value.  These two lessons can be summarized by examing three chess pieces: the queen, the knight, and the bishop.

When I look at any system, I examine both the system's design as well as the content that uses the system.  I believe this is something that system designers should always do.  A system is only as good as the content that makes use of it; content that fails to make use of a system (or vice versa) will always create a disappointing experience.

The queen is typically the most powerful piece in chess (though not the most valuable; that role is reserved for the king).  The queen's movement capabilities combine the lateral movement of the rook with the diagonal movement of the bishop.  Even if you are learning chess for the first time, the fact that the queen combines the movement of two other pieces makes her relative power clear.  A rook's ability to perform a castle, the knight's excellence at creating forks, and a the pawn's ability to capture an enemy pawn en passant are all capabilities that take a while for players to appreciate, but not the queen's movement.  The queen's value is obvious.

Gameplay consists of players making (more-or-less) informed decisions about what they need to do to overcome an obstacle.  It is not enough for the obstacle to be clearly defined and communicated to players.  They also need to have a clear understanding of what tools are at their disposal to solve the problem.  In chess, the player's primary tools are his or her pieces.  Though circumstances determine the value of pieces on any given move, no one needs to advocate the fundamental value of the queen in chess.

As an extreme analogue in video games, it's unlikely that many players need to be told what the value of the HECU RPG is the first time they find one in Half-Life.  After being pursued by a relentless Apache helicopter over numerous maps, the player winds up in a cave with the RPG on the ground and the Apache hovering outside.  Players typically snatch up the RPG and blast the Apache in moments.  Though the HECU is not the "queen" of Half-Life's weapons, it has obvious applicability in the circumstance where it appears.

When designers develop tools, we should strive for clarity of primary purpose in a player's tools.  The more obvious we make the value of the tools at a player's disposal, the more quickly the player will spend time fully engaged with the obstacles at hand instead of trying to figure out what they aren't "getting".

Chess has various informal ranking systems for the relative value of pieces.  The rankings are not used for scoring, but they are used to give players a rough idea of the strategic (not tactical) value of those pieces.  In the most commonly used system, pawns have a value of 1, rooks have a value of 5, and queens have a value of 9.  Knights and bishops are both rated at 3.  Bishops move diagonally, always staying on their starting color, and knights are the "funny moving" pieces of chess, hopping two squares horizontally or vertically and one square vertically or horizontally, passing over other pieces along the way.  Though their tactical applications in any given circumstance are completely dissimilar, the common ranking systems give them equal (or close to equal) strategic value in chess.

Whether chess' numerous contributors intended for them to be equal in value by design or players collectively determined they were equal in value, today's players generally regard them as being so in spite of their radical differences.  I.e., players treat them as having orthogonally equivalent value.  Knights and bishops are considered equivalent in an orthogonal sense because their mechanics and applications do not overlap but they commonly create the same amount of benefit for players.  Though bishops can move infinitely along their color, potentially from corner to corner, they lack the knight's ability to move over pieces.

Dungeons & Dragons commonly presents choices in such a fashion.  The most obvious examples are spells, which are grouped by level.  In most editions of A/D&D, haste and fireball are 3rd level wizard/magic-user/sorcerer spells.  Though the tactical relevance and application of these spells varies wildly, the games' designers established them as being equal.

When we design tools for the player to use -- abilities, gear, options, upgrades -- options with ostensibly orthogonally equivalent value create interesting choices for the player.  They also lend themselves to increased clarify of purpose.  The more tools overlap in function, the less obvious it is to players why a given tool exists.  The less tools overlap in function, the more those tools seem suited to a specific circumstance.

While these are high-level design concepts, creating choices with obvious, easily differentiated values can make the low-level details much easier to execute and build upon.  When a player is presented with strategic or tactical choices, he or she is always fundamentally asking the question, "Why do I want to make this choice instead of any of the others?"  As designers, we want to communicate the answers to their questions as elegantly as possible.  Ideally, the design of the player's tools and the game's content should be self-advocating, allowing players to reverse-engineer our intent and their range of choices without a word of explanation.

8 comments:

Thomas said...

Very interesting look at chess, really gets down to basics.

However, I would like to see an examination of the other side of this, which is something that RPGs have traditionally done poorly. How do you inform the player about his opponents' "power level?" In chess, it's clearly obvious what tools your opponent has, how he can use them, where they are, and what you have to worry about. In most RPGs, this is mostly hidden from the player. Often the only way to judge an opponents power is through trial and error. If you're about to fight a DnD wizard, there is basically no way to tell what spells he has, so no way to know how to prepare.

Now, it's obvious why this is. The designers are trying to create a sense of realism. How would the players know what's in a spell book beforehand?

It still creates a less than ideal situation for a game, where the players are asked to overcome a challenge with very little knowledge about what the challenge is.

Anonymous said...

@Thomas:
That's why we have savegames (and also why their loading times should be minimal.)

Another way to do this would be to have rumors from people who know the enemy about that wizard's preference for spells, or maybe by means of the thief pickpocketing/finding the mage's journal or something. This way tends to add a lot of immersion and rewards player exploration (a basic 'feel good' feedback).

Fabrulana said...
This comment has been removed by the author.
Fabrulana said...

t's true that in chess you know the tools your opponent have - but you don't know their skill and like RPG's ... with a little bit of luck you may even beat a skilled player if he/she was not focusing. Talking from experience as an amateur chess player :)

Wojciech said...

Interesting stuff, I will be watching your blog

dracuella said...

@Fabrulana
Yes but if we draw the comparison from RPGs to chess, aren't we talking about the player's strategic skills rather than power level? To me it seems the player himself has no 'power levels'; power levels in chess are the abilities of the pieces, ie. move length, speciality moves etc. This translates directly into the opponent resistances, speed, strength, thac0 etc. we find in RPGs.

Anonymous said...

Check out counter play from Extra Credits.

http://penny-arcade.com/patv/episode/counter-play

Similar ideas are expressed in chess as well.

Herr Comrade said...

Very interesting read. Makes sense, especially considering expanding the concept out to class relatives between editions, like the power of a L1 Fighter or MU in 1E vs L10 in each class.

If you've ever played Gamma World, what's your take on their 1st edition in regards to ? It's probably the most consistently popular system & edition combination with players that I've run over the years behind amalgamations of D&D editions and house rules. I'd like to think the combination of simplicity of abilities and the many applications of those abilities - a giant telepathic iguana with heat vision doesn't just fry baddies but microwaves dinner during night watch - lends itself well to what you said re: tools and their obvious function; there's just enough detail to give the players ideas about what they can try to do with those abilities.

OTOH there's little to no clear definition of power relatives other than the function of abilities or equipment and the influence of the character statistics and player creativity over those. There's no Level 6 force field, force field is a mutant ability which is power relative to that mutants Mental Strength score. The differences are confined to the categorical - Physical or Mental mutation. Even leveling up has very little impact in relation to other game systems.

Relational power when it comes to equipment is based on the characters stats to an extent but also their race - pure strain humans have access to all technology (including powered armor, killer robots, stylish hovercars and fusion powered portable unfolding pocket toilets), whereas mutants have a much more difficult time. This creates an interesting power balance between characters with mutant powers vs. characters without them.

I think a lot of the fun players have with the GW E1 system is the sense of discovery and exploration (as well as creating new characters when a faulty laser rifle explodes in their faces when they try using it as a shovel). I think the big downfall of that and subsequent GW systems were its faulty mechanism for working out technology - it was complicated and unintuitive to many players until they spent a ton of time with it, and even then it was a "lets get through this and back to playing" process. The concept was true to the game though - a set of rules to provide a feeling of discovery, even when the player already knew the dang thing shot lasers.

Sorry for filling up your wall with ramblings, got me to thinking. Thanks for the great read.