Seeking Suki – The Cangames Running

The Friday evening and Saturday at Cangames 2011 in Ottawa passed rather successfully. As soon as I post this I will dash off to “run” a game of The Extraordinary Adventures of Baron Munchausen followed by John Wick’s Wilderness of Mirrors. I just thought I would give a quick report on the first running of the Spark RPG yesterday.

It worked. The game held together and encouraged exactly the kinds of conflicts that I wanted to support. We had our cold and callous corporate scientist have a epiphany and change one of the pillars of her personality into “All people deserve respect”. The practical village headsman was inspired by the Shinto android and they were able to overcome great challenges.

There were problems, certainly. I had to alter how the dice were evaluated since botches were a mite too extreme in the old approach. Much of the rules presentation could be improved and I might need to rework some of the Resolutions (mechanical outcomes of rolls). Still, it was fun, fast and lively with excellent players who really seemed to get into it.

Speaking of which, if any of you fine players have found this post, welcome! I neglected to record your names so if you would like to be credited in the book and/or receive some other goodies, please email me!

Now back into the fray.

Links:

http://cangames.ca/

Seeking Suki – Developing the Scenario

I will be running a convention game of the Spark RPG at two local regional conventions.  The first of these is Cangames on the May long weekend in Ottawa,  where I will run my session on the Saturday morning (9-1).  The second convention will be the Grand Roludothon in Montreal on the 11th and 12th of June.

I would absolutely love people to attend these sessions, if they are available.  I will provide any participant with electronic access to my game as it is developed and add them to the credits if they are interested.  The adventure takes place in a “Kurosawa does Firefly” type of setting where the players try to discover what happened to a village and seek the headswoman Suki for reasons of love and honour.

 

Working on the design has led to a few delays in producing part 2 of that mechanics article, so please bear with me.  I will post that as soon as I can.

The Foundations of Fun (Part 1 of 2)

The Foundations of Fun

Basic Decisions when Designing RPG Mechanics

.

Gears

Note: This is only the first half of the article.  I will aim to release Part 2 of 2 dealing with Resolution Systems, as well as the full article in PDF format  within the next week or so.
I hope you enjoy  reading and please feel free to leave comments
.
.

There is a great wealth of knowledge of Game Design that can be found online if you have the patience. There are forum threads describing abstract theory, blog posts on novel techniques and the occasional dialogue on Twitter on the underlying philosophies. It can be a challenge to learn though, since they tend to be I thought that it might be useful to have a high-level overview of how mechanics function and that such a document could be a boon for new designers.

Disclaimer: I am neither a wealthy nor a successful designer.  I don’t even manage to play one on TV. I have more then a few years of experience in the craft and spend far too much time reading up on game design theory and technique, but that’s it.

 

 

What this is about

Each game is fundamentally built out of a series of choices, each informed in turn by your central design premise. Rather then examining each particular application, I am focusing on providing a high level overview of the general types of decisions you will have to make. The major decisions fall into two categories; what kinds of Traits are on the character sheet and how that interacts with the Resolution System. Once you use this to build the skeleton of your game system, you will be able to go into depth and determine the specific traits and formulae. Those details will allow you to encourage specific behaviours and focus the style of play to meet your needs. That is where most of the real challenges lie, once you build a foundation

Traits

The typical format of an RPG has multiple participants who play different roles in the game. These characters are differentiated by the various Traits they possess. I am using the most generic form of the word to represent attributes, skills, aspects, abilities, merits, flaws, cash and an y other element written on the character sheet. This is intentionally broad and represents the Cues/dice in Vincent D. Baker’s “Clouds and Arrows” article in the Further Reading Material.

 

1 How many different Traits?

The number of traits is a good measure of system complexity. The more Traits, the more variables that a player will need to account for during play. Often some Traits are lumped together in categories to represent differences. For instance, Melee, Archery and Riding might all be Traits in a system where they are all categorized as different “Skills”.

 

1.1 Games with Few Traits

There are a number of advantages of a system with relatively few distinct traits. Fewer traits mean that the game system is proportionally easier to learn, to recall and to teach to others. These games are usually friendly with new players and allow for quick character generation. These lightweight games tend to be friendly to improvisation and will naturally reinforce character actions as driving the story forward.

Examples: Dresden Files RPG, Savage Worlds, Dogs in the Vineyard and even 4th Edition AD&D.

 

1.2 Games with Many Traits

These types of games tend to be more complex and more precisely describe the player characters. Many traits mean that the game models more complex interactions between the character and different elements of the settings. These heavyweight games tend to do excellent jobs in modelling certain situations in game and can promote a sense of realism. The heavyweight games tend to be friendly to planning and will naturally reinforce character concept/capabilities as driving the story forward.

Examples: GURPS, Hero System or Rifts.

 

 

2 What is the Scope of the Trait?

Each Trait has a range of situations where it applies. Athletics may be defined in the book as allowing running, throwing and climbing but not swimming (Proscriptive traits). Alternatively, the player may decide to write in “Track and Field” on their sheet and interpret the trait during play (Descriptive traits). The question is whether the applicability is defined by the game designer in advance or by the player in game.

 

2.1 Proscriptive Traits

These types of traits are common in RPG’s. The designer tells the participants exactly what each given trait does mechanically. Trait A will only apply in these situations, and will behave in a predictable fashion. This dates back to the early versions of Dungeons and Dragons where thieves might have a score in “pick locks”. It’s very clear that exactly what those traits do mechanically and there will be no confusion on where that particular trait applies. As a natural result, it limits the number of possible actions that a given PC might perform. This often allows for the designer to focus the style of play to match certain themes, moods and settings.

Examples: Almost every RPG in existence has proscriptive traits. Most systems have Skills as clear proscriptive traits.

 

2.2 Descriptive Traits

Descriptive traits are rare, but have been appearing more and more of late. The participant writes in some statement, question or word for one of their traits. When the player, GM or group determine that the trait is relevant, there is some mechanical effect. This means that almost every trait is unique in applicability and each player has drastically different capabilities. As the traits are determined by the player, they are custom tailored and flag exactly which issues and actions the player wishes to focus on. Descriptive traits also have the merit of being flexible and usable for any setting, as it is the player who determines them.

Examples: Unknown Armies (Skills), Dresden Files RPG (Aspects), Burning Wheel (Beliefs).

 

 

3 What values can the Trait have?

Once you know _what_ each trait applies to, it comes down to deciding what possible mechanical effect those traits have. While I know you haven’t determined your precise mechanical system yet, you will need to know what variables will feed into it.

 

3.1 Binary Traits (Lever)

Binary Traits, also known as Levers, are traits that have two values. They can have a value of Yes, meaning that the Trait exists and will apply the mechanical affect within it’s scope. Otherwise, the character doesn’t have the and it will not have any mechanical effects. Levers are simple to remember, easy to learn and fast to apply during play.

Many game systems treat languages as Binary Traits, with characters either fluent or ignorant of the language in question. Another common use of levers is for special traits called “Conditions”. When a character is stuck in the head, they may have a condition of “Stunned” which would have certain mechanical effects.

Examples: Dungeons and Dragons (Languages, Feats, spells), Storyteller System (Some merits, flaws)

 

3.2 Fixed Traits (Score)

Some Traits are fixed in values and are referred to as Scores. Other then occasional improvements, each Score will remain static. These are qualities have predictable and consistent mechanical effects whenever the Trait applies. It’s the most common type of Trait in existing roleplaying games. These are just written as integers on the character sheet most of the time.

Examples: Dungeons and Dragons (Attributes), Storyteller System (Skills)

 

3.3 Variable Traits (Dial)

Variable Traits, referred to as Dials, change frequently during play. Each Dial will have a minimum (usually zero) and a maximum value. The value of the Dial provides some mechanical effect and/or interacts with the resolution system. Conversely, certain kinds of events in the fiction can change the value of your Dial. These are the most customizable, complex and compelling types of Traits. Usually Dial Traits are tied to the players long term concerns and goals.

Examples: Don’t Rest your Head (Madness Dice, Discipline Dice, Exhaustion Dice) or Vampire: the Masquarade (Humanity).

 

3.4 Resource Traits (Currency)

Resource or Currency Traits are similar to Dials, but they have no maximum. They have values from zero (no resource) to potentially infinite. Resources can either be diminished in play or increased, but the actual amount of currency usually has no mechanical effect in the game. Often Resource traits function as “cheat mechanics” which allow for players to affect their chances of victory in specific conflicts.

Examples: Dungeons and Dragons (Gold, XP), Dresden Files RPG (Fate Points), Buffy RPG (Drama Dice).

 

To Be Continued

Ponderings

I have manged to cobble together a two-page long summary of my game thus far. While it’s only understandable to me, it is solid enough for me to run a demo game I think and took dramatically less time then a fully detailed revision of the text. I have some pressure to prepare the scenario for a local convention (CanGames) and I want that session to be as enjoyable as possible.

By the way, I am pondering a quick little mini-review series of some of the indie RPG’s which I have picked up from the various DriveThruRPG disaster relief bundles but I am uncertain if there would be much of an audience. Anyone have opinions one way or the other on this? Highlighting the novel technologies and interesting implementations within the design community seems helpful but I am honestly uncertain if anyone would read the things. Can you let me know?