Monday, November 13, 2006

What is Setting? part 1

Heya,

This was inspired by a great thread on revising the Dark Sun Setting.

Today I’m going to start a multi-part series of articles on Setting. I don’t know how many parts it will have, but I fully expect by the end of it to have my views on Setting change significantly, and at the same time I expect my views to change those of others’. But to make sure this happens without a lot of arguing and sniping, I’m going to set some ground rules. I want to invite feedback and debate, but I don’t want it to get out of hand. First, as always I expect responses to be meted out with common sense and common courtesy. Debate and learning break down in a hostile environment. So no attacking, and back up your statements with actual play or actual designs. Second, I won’t go back and change anything in the original articles. Don’t expect me to. I will, however, post a revised article sometime distant and down the road or make a note in the next article. Third, I am very open to your ideas. I hope you will be open to mine and others’. Fourth, expect me to play the Devil’s advocate and challenge you to prove anything you assert. I want to agree with you, but I won’t until I feel completely convinced. Fifth, I may add more ground rules at any time.

Alright, enough of that crap. Let me really begin by saying first that I’m not a big fan of Setting Exploration, especially if I already know a lot about the Setting. However, I am VERY interested in Setting as one of the major elements of an RPG. The sad thing is though, that the methods and tools for Setting Design have (IMHO) lagged waaaaay behind those for System and Character design. So what I want to do with this series of articles is create some tools for Setting-generation for myself and anyone who finds this blog useful.

The Provisional Glossary defines setting as: “Elements described about a fictitious game world including period, locations, cultures, historical events, and characters, usually at a large scale relative to the presence of the player-characters. A Component of Exploration.” That’s helpful to some degree. It gives us a starting point for components of a Setting and its purpose in-game. One thing it doesn’t mention, that I feel is important, is that every game has a Setting. Even so called setting-agnostic games like GURPS, Universalis, or Rolemaster have Settings. Sometimes those settings are created by the players in-game (Universalis) or sometimes those settings are implicit based on genre tropes like elves, swords, and magic (Rolemaster). But to really get any use out of a definition of Setting, we must understand what makes up Setting.

At the moment, I have identified nine aspects of Setting. They are:

-History
-Geography
-Authority (as in Government/Rulers/etc.)
-Social Situation
-Mythology/Religion
-Inhabitants
-Where the PCs Fit In
-Dynamic Forces
-The Mutables

ALL of these are important to a Setting, but not all of them are always present. The first five aspects I call Lesser Aspects. Not because they are unimportant (remember I said all aspects have importance) but because if they are absent, the game can still be quite functional. If you never read the reams of history that comes with Forgotten Realms, you could still quite easily play in the setting. Not knowing the exact geography of New York City does not necessarily stop you from playing Vampire in that local. Knowing what form of government Ptolus has will probably not be essential to a dungeon crawl in that city. Skipping reading the mythology or religion section of Middle-earth (while it is really cool) doesn’t mean you won’t enjoy playing in that setting. These five are important but are not necessary for a design.

The bottom four aspects I call Greater Aspects of Setting. Not because they are more important than the others, but because they are requisites for a Setting to be functional. A Setting must have inhabitants (Characters) in order for it to be useful in an RPG. Who lives in the world? What’s the diversity like? Knowing where the PCs fit in is vital. What is their place in the world? How does the world see them? Dynamic Forces are forces that directly impact the characters. It can be anything from orcs to secret police to a terrorist organization. Where does the conflict in the Setting come from? What do the players play against? Finally, the mutables. These are things the PCs can change in the world. What can the player-characters impact? How do their actions matter in the context of the Setting?

In the next part of this series, I’ll go into greater detail for each aspect. This article is merely to get my ideas down and get some feedback. Hopefully, by the end of this I’ll have something akin to the Power 19 for Setting Design.

Peace,

-Troy

Saturday, October 21, 2006

It Lives!!!!!!!!!

Heya,

A couple of landmarks here. First, this is my 50th post with Socratic Design. I'm proud to have it announce the following: The new Divine Legacy website is up: http://www.divine-games.org/index.htm

This is one of several steps that bring my games closer to productions. I'll keep udates going here as things get closer to the release. Feedback is welcome! :)

Peace,

-Troy

Monday, October 16, 2006

What is Strength of Emphasis?

Heya,

At the moment, I’m in the midst of finishing up the final layout retouches on one RPG and starting to design a new one. One thing I’m finding as I do both is that I want to draw more of the reader’s attention to some aspects of the game and less of it to others. I believe that every word in a game’s text should be important. If it is not important, why is it in there? Fluff and Filler text can be spotted a mile away by experienced roleplayers, and it serves only to confuse new ones. If I find a piece of text that is unimportant to how the game should be played, I should just take it out.

That’s a piece of good advice I got from another game designer a while back. But I’ve also come to realize that while yes, everything in a game’s text should be important to the game, there are different levels of importance.

Take combat and magic, for instance, in DnD- any edition. Look at how much of the PHB those two things take up! It’s close to two-thirds of the book when you include weapon lists and spells. Those two things are vital to play in DnD and therefore are strongly emphasized in the text.

Look at Town Creation in DitV. It’s a big deal. The author even says so. It has a lot of description, and if you look at the game’s website you will find sample towns available. Town Creation receives a great deal of “strength of emphasis” from its creator because it is so important to play.

But should the important stuff always be so strongly emphasized? The answer is no.

One of my favorite examples of a game that purposely did not strongly emphasize its key feature is (was) The Riddle of Steel by Jake Norwood. (Jake, if you read this say hi. It’s been a while) The key feature, IMO, to TRoS is a character’s Spiritual Attribute. But instead of going on page after page about it, it’s just thrown in with all the other character creation items. On the other hand, the book has all kinds of stuff about combat. It probably has the most realistic combat system ever implemented in an RPG. And Jake used that as a major selling point. However, talk to anyone who’s ever played the game, really played it, for an extended period of time. See which of the two they though was more important to play. The importance of Spiritual Attributes is to be discovered during play, not hammered home in the initial reading.

I have run into this sort of thing with one of my own games I am designing. It has a “Walk Away” mechanic. The game is filled with violence, tough choices, and sacrifice. That’s the point of it. But I wanted to offer the ultimate tough choice to the players: giving up. Now it’s not something I want them to choose often, but I do want it to be there. So while other game features get bold print, examples, and lots of description, the Walk Away mechanic does not. Perhaps it will only get a couple lines. But it is something I want them to discover later in play, just not necessarily in the first reading.

So what are some ways to show strength of emphasis? Below are some suggestions:

-Layout Features
-Graphics
-Warnings
-Verbiage
-Capitalization
-Illustrations
-Repetition
-Promotion
-The Blurb

What can a heavy strength of emphasis accomplish for a game? It can draw attention to a mechanic. It can encourage the use of a portion of the text during play. And it will help discourage indifference towards that mechanic/rule/text. Basically, strong emphasis can alert a reader to something’s prominence in the game. What is strongly emphasized in the text will likely be strongly emphasized in play.

What can a light strength of emphasis accomplish for a game? It can hide surprises that come up in play. It can make the use of a particular rule or mechanic more rare. It can present options to players without making them a requirement. Finally, it can be used as contrast to help emphasize the portions of the text that are important.

At lot of this is self-evident, I realize, but this is a topic that was pertinent to what I am doing with my games. Both strong and weak emphasis are necessary to a game’s text. Used appropriately, they can greatly enhance the depth of understanding and play of a game. Used wrongly, and a game could end up an incoherent mess. It’s somewhat obvious, I know, but that does not make it any less important to design.

Peace,

-Troy

Wednesday, October 04, 2006

What's the Worst Part of Moving?

Heya,

For various reasons, none of which I am happy about, my wife and I have moved to a new city. It is much clearner and nicer than our old one and I know we will be much happier here. However, it's a real pain. I hit a mailbox with the UHaul. Our cat got lost outside during a rainstorm. Our landlords are never around so we can't even sign the lease yet. And we have 87 empty cardboard boxes to deal with now (no exageration). But you know what? None of that is what's bothering me. What's really bothering me is our lack of Internet access right now.

You see, in our new town Cable TV/Internet is run by the city as a utility. None of the major companies (Comcast, Insight, Time Warner) are allowed to compete. So when you move in, the city government is in charge of hooking you up. As with anything the government is in charge of, it's never done right, never done on time, and not nearly as effective as it should be. So, I'm at work on my Fall Break (I'm a teacher) using the Internet to catch up on online stuff and enter grades into the school's network. It's lame, but I got no choice. Worse, it's delaying the release of Cutthroat. It will take at least 10 more days for them to get around to hooking us up. You know, if the paperwork isn't lost or a committee doesn't have to vote on it or something else governmentalish.

Whatever. Anyway, I hope you are enjoying the changing of the seasons. Nature is SO beautiful this time of year. You should get out and enjoy the fresh air in a park or nature preserve or something. October is my favorite month.

Peace,

-Troy

Thursday, September 28, 2006

Is Min-Maxing Bad?

Heya,

For a while now, there’s been talk goin’ round that Min-Maxing isn’t a bad thing; that players are just choosing the optimal strategy and finding a niche for their characters. Those that say this do have a point. You can’t hardly blame a person for wanting their character to rock! They’re just doing what the rules allow. However, the full-on supporters of Min-Maxing might have a narrow point of view. In truth, I see three legitimate PoV’s on this: Min-Maxing isn’t bad, Min-Maxing might be bad, and Min-Maxing is bad. I’ll explain.

Let’s take “it isn’t bad” first. Min-Maxing is a strategy. Period. In fact, I’d say it’s a very obvious and natural strategy. Minimizing resources allocated to character components (skills, stats, advantages, whatever) that will seldom see use and/or character components that have drawbacks or flaws of some kind is sensible. Likewise, maximizing resources allocated to components that will see a great deal of use and/or components that provide advantages and bonuses is very logical. It’s almost a kind of “Duh!” moment, if you will. Whether it is during character creation (Chargen) or advancement, Min-Maxing is indeed a legitimate and probably beneficial strategy. Thankfully, those that decry it as a bad way to play are dwindling, however they are not gone completely. Which brings me to why Min-Maxing might be bad.

There are people and play groups that feel that Min-Maxing is bad play or that it’s not very sporting. They feel that the strategy undermines both the spirit of the game and the spirit of the group. It is in this circumstance that Min-Maxing might be bad. More important than good strategy is the Social Contract a group has set up (consciously or unconsciously). If Min-Maxing violates that contract, then if becomes bad play.

So what does one do in this situation? As I see it, there are three options. First, is to open a dialogue and work out a mutual compromise everyone can agree to. Come up with a solution that makes the entire group comfortable, so play and enjoyment can resume. Second, is to conform to the group’s Social Contract. Sometimes one has to sacrifice one’s own preferred style of play for the good of the group and the opportunity for having fun. Finally, one can simply leave the group. If a compromise cannot be found and there is no willingness to conform to each other’s style in either party, then perhaps it is a good time to bid farewell and find a group that better matches that style. Staying in a contentious situation ruins everyone’s fun. Each person will have to decide on their own.

Now for an instance where Min-Maxing is bad (IMHO). I submit that any game where Min-Maxing is the dominant strategy either during Chargen or Character Advancement, that game needs revision. Min-Maxing is one legitimate strategy in play, not the only legitimate strategy. If a design funnels characters into tight Min-Maxed boxes, then I believe the designer has come up short. He has left open a lot of room where he can design far more interesting strategies in his game. Especially if a game focuses on strategic use of character components, Min-Maxing as the dominate strategy is horrible. That’s not really strategic at all. It’s just following the only real path presented by the rules. Others may disagree, that’s fine. But I honestly don’t believe those kinds of game have the potential to produce as much fun as games with multiple and varied strategies. There’s a lot more out there than Min-Maxing.

So to sum up, Min-Maxing is a legitimate strategy. However, players should be mindful of the Social Contract of their group and designers should be mindful of incorporating other strategies in their games. Just because it is legitimate, doesn’t automatically make it good.

Peace,

-Troy

Wednesday, September 20, 2006

Design Journal: Saviours

Heya,

As mentioned back HERE, I am working on a new RPG for my quarterly release called Saviours. I’ve written of Big Three on them and added in answers that respond to two questions raised by Ron and Vincent in THESE videos.

What this Game is About:

Saviours is about superheroes with super flaws. It’s about being powerful and being tragic. Though you save the populous of Ultraopolis time after time, they will turn on you in a second. Though you defeat your nemesis time and time again, there’s always another to take his place. You are powerful, no doubt. You have saved thousands, for sure. But the constant demands of the desperate citizens and the pressures from your enemies lean hard on your back and the temptation to turn against those who support you can look so gleaming at times. Society is doomed anyway, why hold on?

What the Characters Do:

Player-characters in Saviours are divided into two types: Heroes and Sidekicks. Heroes are faced with three main situations: Fight a Nemesis, Rescue your Beloved, or Avert a Disaster. Each of these carries potential benefits or costs to resolve. While doing nothing will certainly earn you the ire of your fans and your colleagues, doing something thrusts the temptation to abuse the great power bestowed upon the PCs. The Heroes must constantly balance gaining power with keeping control of themselves. Sidekicks are helpers to their mentor. They use their powers to augment that of the Hero’s. However, they are often the first to suffer the brunt of the Hero’s frustration and are sometimes forced to sacrifice themselves to save their leader.

What the Players Do:

Players in this game are charged with creating a Crises, how much help they will ask for while facing those Crises, and how much help they will give. They will have to closely manage the resources of their character(s) in order to defeat the obstacles that lay before them and to be sure none of them betray the Organization.

The Game Master in Saviours will provide the opposition to the players. He’ll take on the roles of the Nemeses, Henchmen, and Disasters the characters will fight. He will also provide Temptations for the characters to stumble and Hazards that the characters will have to overcome. His job will be multi-faceted as each player will have his own character with perhaps a sidekick and then choose which crisis to take on. It’s a lot to keep track of, but very rewarding to see how the players deal with the high stakes situations.


Why do I want to make a Superhero Game?

Well, first, I’ve never written a Superhero game. I’ve played plenty of heroes, but never with any real satisfaction. The Superhero genre is one many of us can relate to. Many of us got comics as youngsters that stirred our imaginations. I remember my first Spiderman comic. It was the one where the Scorpion is invented. I wish I still had it. It was awesome to me to see how a person with power could be tempted to use it for his own selfish purposes and how another person could use his power for the benefit of others. It was from that initial, childhood impression that Saviours would some day be born.

Why do I want to make a new Superhero Game?

I like games with strategic choice and tactical encounters. I like games that pose a challenge to me, that I had a part in creating, and ask me to figure out a way to overcome that challenge. I also like to narrate. I’m not very good at it, but I like to do it anyway. From these desires came several ideas for a game. None of the other Superhero games, I felt, gave me the kind of play experience I wanted or that others who are inclined like me want. I want strategic fights that are heavy in narration with consequences that matter (i.e. mechanically represented explicitly) at the end. I wanted a game where I got to make both the hero and the villain he faces. I wanted a game where I had the option of making a sidekick, but didn’t have to play him too. I wanted a game where people had to care about and support my character and where I had to care about and support their characters too. So basically, in the words of the Durham 3, I want others to make me look awesome, and I want the chance to make everyone else look awesome too!

So what’s next?

Well, I need to finish my first draft. It’s mostly done, but there’s a couple issues I need to hammer out. I have some tough choices to make. I’m sharing this here on my blog because I talk about design a lot, and I felt that I had better start showing my words in practice. So with Saviours, I’ll try to show how I implement my own design ideas. Today it was the Big Three. Of course, feedback is always welcome! :)

Peace,

-Troy

Saturday, September 16, 2006

Memory Lane

Heya,

Good ole, good ole times. If you're into the Forge at all, check out this link: http://www.indie-rpgs.com/forum/index.php?topic=21464.0 Bringing back some old memories- good and bad. I'm sure by the time it's all done, there will be a lot to learn from what's posted there.

Peace,

-Troy

Wednesday, September 13, 2006

What is 'System' ?

Heya,

In previous articles I have touched on Situation and Setting. Today I’m going to tackle another key component of RPGs: System. First off, you should know that I do subscribe to the “lumpley principle.” So if you have serious issues with that, then I’m afraid that this article won’t help you very much.

But anyway, the lumpley principle states: “System (including but not limited to 'the rules') is defined as the means by which the group agrees to imagined events during play.” The first time I read that I went, “Huh?!?!?” Then, through the years, I read a lot of explanations to it and the definition finally clicked.

Basically, System is big. Real big. In fact, we should really write it in all caps like this: SYSTEM instead of just capitalizing the first letter. Writing it like that, I think, might clear up a lot of confusion, because when someone (especially if they are new to RPG theory or design) sees “System”, they might think of something like the D20 System and say, “Well the whole system is just the SRD, right?” Well, not exactly.

To really help me understand what SYSTEM (the lumpley principle) meant, I had to brake it up into two parts: Rules and Procedures. For my purposes, Rules are the games text. They are the printed words on the page, unmodified in any way by the participants. Rules are the author’s expression of the game objectively observed in black and white on the page. Everything in the book, from cover to cover, is Rules. Anything that is not in the book that affects play is Procedures.

EXAMPLE OF A RULE (A): “Roll three d6 seven times to generate the seven stats for your character. Arrange them any way you like on your character sheet.”

EXAMPLE OF A RULE (B): “Choose one of eight races included in this book for your character. This will be his/her heritage and background.

Procedures can include modified Rules (often called “House Rules”), dialogue between participants, deciding who the “leader” of the party will be, who gets to roll dice first, narration of events/actions by characters, negotiating conflicts between players and/or characters in a fashion not provided for in the Rules, and so on. Procedures are essentially the talking around the table and the actions/agreements made by the participants that are unique to the group. It’s anything the participants agree to do or establish that affects the in-game events. Sometimes Procedures are based off Rules; sometimes they are not.

EXAMPLE OF A PROCEDURE (A): “Hey guys, instead of rolling 3d6 for your character’s stats, roll 4d6 instead and drop the lowest one. Arrange them in any order you like.”

EXAMPLE OF A PROCEDURE (B): “Guys, there are no elves left alive in this world we’re going to play in. So when you choose a race, you can’t choose to be an elf.”

So if you look at it like that, you can see that SYSTEM really is big. It includes everything that goes on at the table no matter how closely or loosely it adheres to the written rules of the game. It even includes stuff that people term as “meta-game.” Anything that affects the in-game events is part of SYSTEM.

So what does that mean for a designer? A designer must be aware that the SYSTEM of his game will, no matter what, include two parts: The Rules and The Procedures. It’s been said that the only part of SYSTEM a designer really has control over is The Rules- the words he writes in his game. But this isn’t entirely true. A designer can encourage players to develop Procedures for the game. In fact, many games are enhanced by players making up the bulk of SYSTEM and only referring to the Rules when there is a dispute. A designer must signal to the players (using the text) when it’s probably okay to use a Procedure to handle something and when it is advisable to use a Rule instead. You have to decide, will your game be Rules Strict (i.e. encouraging players to play as closely to the rules as much as possible) or Rules Relaxed (i.e. encouraging players to improvise and customize the rules as much as needed)?

This is quite important. No group will ever play the game strictly by the Rules as written. Human communication and understanding is far too limited to allow for that as a possibility. However, no group will ever completely toss out the Rules either. People sit down to play a game because the game text inspires and intrigues them. Therefore it is vital that the Rules give the participants guidance, explicit and thorough guidance. A designer must ask himself these two questions constantly as he writes his game:

“When do I want them to use my Rules as written to help advance play?”

“When is it okay for them to take ownership of the game and use Procedures of their own?”

Peace,

-Troy

Tuesday, September 05, 2006

New Business Plan

Heya,

((This is also cross-posted HERE at the Forge))

What a trip my path towards game publishing has been lately. Recently I read This Post by Ron. There’s a road of no return that people walk when they get fed up with RPGs and never want to come back; I almost went down that. Just for some quick background two of my games Cutthroat and Hierarchy won Ronny awards last year. I was pumped about getting them tested and published. Well, I got that done, finished the layouts scooped up all the art I could for them on my budget and had it all ready to go. Then several things that I wanted to go my way didn’t. I was disappointed, very disapointed. When my cousin Stacey scheduled her wedding on the weekend of GenCon, I just swore the whole thing off. I thought I was done. But, after several encouraging conversations with my wife and a really awesome trip to the Western United States this summer, I came back with a new perspective. I knew I still wanted to publish my games, but releasing all four (adding Standoff and Holmes ‘n Watson to the list) at once didn’t seem right. I had an opportunity to do something unique, but I didn’t know what. Then I listened to Paul Tevis’s interview with Ken Hite on Have Games will Travel.

The idea struck me like a bolt of lightning. Ken said the gaming industry, specifically the distributors and shop owners, were increasingly looking at RPGs as periodicals rather than books. His words also jived with what I’m learning in my masters classes about children: attention spans are getting shorter and new stimulation is required *often* to keep their minds focused on something. So I thought, “Hey! Why don’t I turn my games into a periodical rather than just dumping them on the market all at once!” It was crazy. And I liked it. So here it is, my new business model:

I am going to offer customers the opportunity to purchase a subscription to my games rather than purchase each new game as it comes out. A subscription would include four books that would come out quarterly (every three months) and be complete, self-contained games. This is not a model where I create one “Core Rules” and release supplements every quarter. Each game is a unique individual and very fun to play. As of right now, I plan to offer three different kinds of subscriptions.

The first kind would be a PDF subscription. This would be the cheapest. I would just send the customer the pdf over email the day the game is “released” and they would have it waiting for them when they got home. PDFs are getting increasingly popular and if someone wants to test the water this way, it’s good for both them and me.

The second kind would be a Book subscription. This is kind of the “normal” subscription. At no additional cost for shipping and handling, they would receive a new book (paperback, perfect bound) sent to their address every three months. International orders would probably cost a little more and take a little longer to ship.

The third would be a Lifetime Book subscription. While it would cost more, it would guarantee them a copy of every book I release under the periodical model I’m talking about for as long as I can keep it up. They would never again have to pay another fee for the books, shipping, or handling even if the costs of my other subscriptions go up. Once that fee is paid, you get one of everything I make. Period.

I think I would probably also offer to sell “back issues” if people wanted those. I wouldn’t make them available, however, until the next “issue” came out. But if someone gets a subscription in the second year of this and wants Cutthroat let’s say, then he’d have a chance to get it. Of course ordering four back issues would be more expensive than ordering a subscription. Subscriptions are what I’m really interested in selling.

Now I know this sounds a little crazy. A book every three months!?!?! That’s nutz! But hey, I’ve got the first four already written and tested. That’s the first year at least. I’ve got two more games in the draft stage and will start testing them after a couple more revisions. So for the first year and a half I’m already set. Plus, if you’ve followed my Blog at all, you know that I’ve created a good number of tools to help me write these games. I now know what it takes to make a complete game and I’ve got a whole wad of ideas just waiting to be realized.

And you know, honestly, the games I write are pretty simple. They aren’t designed on the same level of depth as say Dogs in the Vineyard or the Mountain Witch. Character creation in each of them is fast and easy. 5-15 minutes for most of the games. And they are really designed to give the players a complete game experience in one sitting. Kinda like a short story rather than a novel. So imagine a customer gets his book. It’s 50-70 pages long and takes less than a half-hour to set up and only 2 to 5 hours to get a complete game. If he and his friends play twice a month, then by the time my next game comes out they’ve had 6 play experiences with it. They’ll be ready for something new. And that’s the idea. I will provide customers with frequent, new gaming experiences at regular intervals that won’t take up a lot of their time with things like set-up and prep. At least, that’s the hope.

I will be a little bit before I get this in motion, though. I’ve got to redesign my website. I need to figure out PayPal a little better so I can set up a storefront on my site. I need to revise the covers and touch up the layout on a couple games. So no sooner than the 4th quarter of 2006 would I be able to get this out the door. That sounds about right.

Anyway, here is what I want from you guys. I’m not really interested in comments on why this model won’t work, why the games will suck, or how I can’t possibly keep up the pace. I am very interested in comments that suggest way to HELP make it work. I’ve discussed this privately with a couple other people. Interestingly, they had opinions on the opposite ends of the spectrum. But I am very interested in what do you think I need to do to make this happen and happen well, and even more interested in anyone’s publishing experiences that might be helpful. How can I avoid potential pitfalls? What are the good points of selling games in this fashion?

I do appreciate you reading this far and all the feedback you will offer.

Peace,

-Troy

Tuesday, August 29, 2006

When is a Concept Ready to be a Draft?

Heya,

As I get ready to make an official announcement about how I’m going to sell my games, I’ve been wanting to stockpile a lot of different game concepts. Of all the steps in RPG Design, this is BY FAR the easiest. So let me preface this article by saying that having a game concept doesn’t really mean all that much. Practically everyone who plays RPGs has a game concept of some kind.

Okay, so what is the article really about then? Well it’s about knowing when your concept is fleshed out enough to move on to actually writing down a coherent version your game. Everyone is a little different, but for me I have a checklist. I call it my “Systems Design Checklist.” What I do is break my game concept up into seven distinct parts (or systems). Think of it like the systems checks that NASA does before they clear a space shuttle for liftoff. If I don’t have each of these systems in place, the concept stays in my notebook. If I do, it’s off to my keyboard. So what are these ‘systems’ I’m talking about? I have a checklist provided below if you’d like to copy and paste that, but for now I would like to describe each individual system in some detail.

System #1- The Play System: This system basically answers the question “What do the players do?” It covers items like scene framing, narration rights, procedures for entering ideas and actions to the shared imagined space where in-game events take place, stakes setting, and stuff like that. In essence, it’s the rules for talking. The play system spells out who gets to say what about what things, when they get to say it, and how far that power goes. This tends to be fairly free form in a lot of games, and that’s totally fine. However, some games ritualize this a great deal (e.g. Polaris).

System #2- The Character System: The character system covers two aspects of character. That is both the creation of characters and their components. This system answers the questions, “What does it take to make a character?” “What resources does the character provide its main player?” and “What resources does it provide all the other players/GM?” Character is one half of the components that go into Situation. So the character system should include arenas of conflict (since conflict is what drives the Situation). Usually arenas of conflict will be tied to a characters stats, personal history, or abilities. When designing my character systems, I make sure I have plenty of built-in arenas of conflict for the player to explore. However, it’s not just the character’s primary player that matters. All the other players, especially the GM if there is one, will be interacting with that character. So the arenas of conflict need to be made available to them as well in order to facilitate collaborative storytelling. When creating your character system, think about what parts of the character can other players (including the GM) use to springboard action? If you want to break it down, I believe the character system consists of three main parts:
1. Process of Creation
2. Main/Primary Player Resources
3. Other Player/GM Resources

System #3- The Resolution System: There are two main types of resolution: Task and Conflict. Each one of those can be broken down into styles: Drama, Fortune, and Karma. I’m not going into any sort of detail about those right now. Check the Provisional Glossary if you’d like to learn more about them. What I am going to talk about is what a resolution system accomplishes for a game. Mainly, it answers the questions, “Where is the element of chance?” “How can disputes between characters be mediated?” and “How are the outcomes of task or conflicts decided?” This can bleed over a little bit into the Play System. But that’s fine! All parts of a game should be related to each other in some form or fashion. When should a Resolution system be engaged? Answer: any time there is a dispute or conflict of interests between characters and/or players in the game that cannot be resolved by talking it out. Vincent’s, “Say yes or roll dice” seems a very appropriate answer to that question.

System #4- The Endgame System: An endgame system is very optional in an RPG design. A majority of games don’t have them, but some do. It answers the questions, “What is the final objective of the game?” “How does the character’s story end?” or “When does play stop?” Not every game needs and endgame. I happen to like designing with them because it helps me conceive of what a session or campaign (for lack of a better word) should look like, what I want the players to do, and the product I want the game to produce. For me, it is a device that helps drive the action to a climax. You may find that you don’t need one, but I encourage anyone working on an RPG to consider just how the game will end and if there is a way to mechanically support that ending that would enhance the experience.

System #5- The Reward System: Or really, the “Reinforcement System.” This system answers the questions, “How do I encourage the kind of actions and behaviors I want and discourage the kinds of actions and behaviors I believe are detrimental to play?” “What mechanical rewards do the characters receive?” and/or “What mechanical rewards do the players receive?” The best way, IMO, to break up rewards is to split them into two- Character Rewards and Player Rewards. It’s very important to understand the difference between the two. Heh, that’s probably a whole ‘nother article in and of itself. But anyway, examples of player rewards would be things like narration rights, plot tokens, or spotlight time. Examples of character rewards include experience points, relationships, and improved proficiencies. Not every RPG will have both kinds, but it is important to consider whether or not your game should. Remember the reinforcement system is the main tool you, the designer, have at your disposal to help the people playing the game to get as much out of it as possible. A weak rewards system will likely result in a weak play experience.

System #6- The Setting System: Setting is the second component of Situation. Where the action takes place has a great bearing on what sorts of conflicts (and by extension Situations) you can have. Creating your game’s setting is therefore, critical. The setting system answers “Where & when does the action take place.” “What is the geographical context and and/or social context for the game?” or “What parts of the fictional world do the players *not* have to worry about?” My games tend to be setting lite, but that’s not necessarily the way to go. Each game will be different. You’ll have to decide. In any case, the “setting system” can be represented in several ways. First, the setting can be predetermined. For instance, White Wolf has World of Darkness. Second, a setting can be hinted at in the text and then left up to the players to fill in as they go. Example: InSpectres. Finally, a game’s setting can be generated on the spot through play and discussion among the players like in Prime Time Adventures or Unversalis. It is important to know how your Setting System influences the Situation of your game. Providing a context for the conflict and action of the game is the main job of setting.

System #7- The Responsibility System: This system is the one you’d probably think about the least. It is the system that decides who does what in the game. For instance, it doles out whose job it is to decide when the Resolution System kicks in or when the Reward System kicks in. It decides which and how many characters each player will be in charge of. The Responsibility system is basically the job list of your game and procedures for deciding who is going to be in charge of what. Does your game have a GM? Does your game allow anyone to introduce conflicts? Does your game force each participant to portray a character? Basically, the responsibility system answers the questions, “What is everyone’s job?” or “What is each participant in charge of?” Sometimes various responsibilities will overlap. Sometimes they wont. Sometimes this will overlap with the Play System. Sometimes it won't. But whatever you decide, your game concept needs to make it clear who is going to be doing what during the game and what tools/mechanics/game pieces they will be able to use to accomplish their charge.

It doesn’t matter in what order you tackle these systems. I just sketch them out as the inspiration arrives. I put them in this order for this article as I found them in my notebook. So don’t feel like I’m prescribing a certain order of conceptualizing. I’m not. All I am doing is suggesting something to you that might be helpful since I have found it helpful to me.

So in conclusion, basically this is the method I use to determine whether or not a concept is worth taking to the next level: the drafting level. Drafting is probably another article for the future, but I feel that if I can have something - some idea - to drop into each of these seven slots, then I feel I have a game worth transferring from the scribbles in my notebook to a coherent document on my computer. You may have more systems or you may have fewer. But I would say that having some kind of method that determines when a concept is worth pursuing and when a concept is wasting your time is a valuable and time saving device.

::System Design Checklist::

O The Play System
O The Character System
O The Resolution System
O The Endgame System
O The Reward System
O The Setting System
O The Responsibility System

Peace,

-Troy

Monday, August 21, 2006

Which is Better: Hit Points or DPS?

Heya,

Like last week’s, this post may actually be more applicable to playing RPGs than Designing, but I feel there is something to learn on both fronts here. Anyway, I was thinking about RPGs and the RPG market the other day. Depending on who you ask, the market ranges from “Never better!” to “A nuclear wasteland littered with the corpses of dead companies.” Either way you believe, there can be no doubt that RPGs are facing some competition. But this competition comes not from CCGs or Minatures or Boardgames. It comes from MMORPGs (Massive-mulitplayer Online Roleplaying Games). Games like EverQuest, World of Warcraft, and DnD Online. I know Mike Mearls has talked about these things once or twice, but I thought I would add my observations.

To me, there is something very important MMORPGs can teach us. First, people don’t need to be sitting in the same room to enjoy an RPG. I salute Code of Unaris for recognizing this and making that a centerpiece in its design. Second, is that games with a Gamist slant (which include MMOGs), hit points are a character’s key feature. They are far more important than DPS (damage per second or how much damage characters can do per round) and the breadth of his repertoire of spells or abilities. This is true for both online games and for tabletop games.

I generally prefer Gamist style games and really look for the best strategy in situations, especially combat. When I examined all the resources available to me during combat in Gamist-leaning games, I came to a conclusion: Hit Points are the most key resource. Not to my surprise, this was backed up by Jonathan Tweet in this article.

In essence, you can really boil combat down to this statement: “You run out of hit points, you lose; your opponent runs out, you win.” Speaking in absolute terms (ignore retreat, capture, etc) that’s the bottom line for victory in combat- the winner is the guy who ends up not running out of hit points.

Victory does not go to who deals out the most damage. That may seem odd, but you have to take the victory conditions into account. You can dose out insane amounts of damage each round in a game, but if you can’t get your opponent’s hit points to zero, you will lose. If your opponent starts out with more hit points than you, can heal himself, pick up extra hit points, or reduce your net damage, then your DPS won’t matter. He has ways to counter it.

So what does that mean? Well, if you’re designing a game where combat is strategic, violent death is a likely outcome, and hit points or something equivalent is involved, be mindful of how you design other aspects of your game. A lot of things that typically go along with hit points such as healing, damage spells, character enhancements (buffs and enchantments), and equipment can inadvertently and radically affect how victory is decided.

Take for instance healing spells. In my mind, these are very powerful spells. They prolong a fight, in fact they can prove the clincher. Even if you only got 1d8 hit points per spell like back in DnD, it made a major impact on the game. If your opponent doesn’t have access to the same spells, the impact is even greater. This is why, if you ask anyone who has played a game like oh say EverQuest 1, clerics are the most vital class to have. They are not the ones who kill the bad guy, they are just the ones who make sure the good guys don’t lose.

So now what? Heh, if you are playing a game where combat and hit points are important, look for feats, skills, and rules that help you not lose hit points. Things like cover, armor, spells and so forth that grant additional defense or hit points should be high on your tactics list. Things like weapon enhancements, fireball, criticals, and so on should be farther down. From my experience, it is better to have strategies to not lose a fight than it is to have strategies to win a fight.

From a design standpoint, designers should think carefully about how you want combat to begin and end and how long you want it to last. The more hit points (or wounds or whatever) a character can amass, the longer an instance of combat will take. Especially if the characters have access to hit point saving strategies like healing, buffs, armor, etc.


Peace,

-Troy

Friday, August 18, 2006

Monday, August 14, 2006

What is a GM?

Heya,

What’s a GM??? Even for Socratic Design, isn’t that a little basic? Heh, maybe. This article might be more useful for players rather than designers. We’ll have to see. But over the years I’ve been roleplaying, I have heard the GM defined as many things. The GM is God. The GM is a moderator for the action. The GM is the one who tells the story. The GM is a game referee. The GM is the final authority. The GM is the opponent. All these things have been said and applied in games at one time or another, but from a design perspective, they aren’t all that helpful. So let’s look at what I believe a GM really is.

First and foremost, the GM is still a player. He is a participant in the game just like everyone else. I think this concept is sometimes lost on people, especially new designers. The guy behind the DM screen still wants essentially the same thing as the guy portraying the half-orc barbarian. He’s there to have fun and use the system to kick ass. So one thing designers need to keep in mind, if they plan to include a GM in their game, is that the GM really is on equal footing as all the other participants. He’s there to explore the game elements, have fun, portray characters, and socialize with his friends. He’s not a mystical entity behind a curtain with smoke and thunder surrounding him.

Second, the role of the GM boils down to responsibility, specifically the degree of responsibility a game thrusts upon him. All participants in a game have certain responsibilities dictated to them by the game. For players it is generally their job to portray one or more characters. GMs, however, are usually responsible for handling everything else. That’s a lot. But in recent years, this has started to change somewhat.

Imagine, if you will, a spectrum. On one side you have a game like Dungeons and Dragons. Players play one character that is strictly defined by class and race. The GM creates the setting, NPCs (both enemies and allies), and challenges the player-characters will face. The players have a very limited amount of responsibility, while the GM has a very expansive amount of responsibility. Moving over slightly you have a game like Ars Magica. In this game, players might portray many characters- especially allies of their main character. The GM still creates a lot of the setting, NPCs, and challenges, but player input in much more encouraged and even supported somewhat with mechanics. Next over you might have a game like Dogs in the Vineyard. Here, the GM is responsible for creating a town, its people, and a Situation. However, it is then up to the players to decide how all that relates to each other. It is the players that tend to drive the action while the GM rolls dice in opposition. At this point, the responsibility of the players and the responsibility of the GM are about equal, IMO. Finally at the opposite end of the spectrum is InSpectres. In this game, it is almost totally up to the players to decide what parts of the setting will be explored, who/what the monsters are, and how the whole thing ends up. The GMs role is pretty much just to react to what the players do. Most of the responsibility is lifted from his shoulders as the players are most definitely in charge. There’s a million games in between and beyond even those, but when you envision what a session of your game will be like (if your game has a GM) think about how much you want the GM to be responsible for.

Third, the GM is the pace setter for the game. Often, it is the GM who starts a scene and who declares a scene over. This is often called “Scene Framing.” It’s up to the GM how fast or slow a particular set events take. This is where a GM has to be very responsive to the players. He has to gage what the players want to get out of a particular scene and how much they are enjoying it. Sometimes a scene will last a few minutes in real time but encompass hours or days in the game’s imaginary time and vice-versa. Designers need to consider this role of the GM. What tools do you give a GM to create, explore, and end a scene? Is it his sole discretion? Is that authority shared with the players in any way?

So in the end, what have we got? The GM is a player first, he’s endowed with certain and specific responsibilities, and he is the pace setter for the game. Every GM in every game will be slightly different. Examine the GMs you’ve had in the past. What made them great? What made them suck? For your game, what would the ideal GM do? How much responsibility and credibility are you going to give him (or deny him)? What tools and aids are you going to create so he can do his job? Finally, what makes your game fun for him?

Peace,

-Troy

Tuesday, August 08, 2006

Socratic Design Anthology #2

Heya,

So I’m working getting back to a regular posting schedule. Things are coming along well now, and soon the hectic pressure of school starting up again will be behind me. Anyway, to tide everyone over I’m releasing the second anthology of posts on this blog. If you haven’t read the First Anthology, go back and look it over. It’ll give you good context for this one. Anyway, expect a new, original post in the next week or two.

Anthology #2

What is the ‘Alt 3’ ?
When Should a Character Die?
What is a Death Spiral?
Does Setting Still Matter?
How Can Magic Be Used in an RPG?
Where Can I get Art for My Game?
What is Troy’s 12 Step Process?
Another Process.
Yet Another Process.

Peace,

-Troy

Sunday, July 30, 2006

So Where are Troy's Games?

Heya,

This is sort of another update as to what I’m doing personally. I’d like to update you as to where I am with my upcoming RPGs. I can proudly say that Cutthroat, Hierarchy, Standoff! and The Holmes and Watson Committee are all revised, laid out, and ready to go. So what’s the hold up? Well, I’ve been doing some thinking. I’ve taken a look at how the gaming industry is set up right now. Have a look at what Ken Hite says in this pod cast. This has really resonated with me. Couple that with the fact I'm unable to attend GenCon this year, I’m going to hold off on these products for a few more months. I apologize, but you’ll just have to wait a weeeeeee bit longer. What I’ve got in mind is really cool and I can’t wait to share it with you. But first I need to get to work on my next two projects: Saviours and Ballin’. I’ll give an update on those in a few more weeks and probably work on them openly at The Forge once it’s back up and running. Thanks for your indulgence and I can’t wait to discuss design topics with all of you in the very near future.

Peace,

-Troy

Saturday, July 22, 2006

So Where Have I Been?

Heya,

Good question. Well, for the last month and a half, I've been on a long road trip out west with my wife. She has vamily in Utah and so we decided to go on a road trip to see all the sites out west and visit her folks. We got to see everything from Yellowstone National Park to the Great Salt Lake to Las Vegas to Old Town Albaquerque. It was a great trip and really recharged my batteries.

I appologize for not responding to anyone's post in a while. I really just needed to get away from Gaming in general for a bit. I'll do my best to catch up on what's been going on and post a bit more regularly. Thanks for sticking with me :)

Peace,

-Troy

Thursday, May 18, 2006

Does Setting Still Matter?

Heya,

The quick answer is Yes, of course Setting still matters. I won’t deny for a moment that when I’m working on a design, I feel the System > the Setting, but they are both necessary for good play and good design. Okay, so why does Setting matter?

Well, first off the PCs need to BE somewhere. So in the very basic sense, there must be a Setting in which they exist. But that’s a non-helpful answer. Setting matters because it is the material the participants build conflict out of. Yes, the resolution systems detail how you resolve those conflicts, but the mechanics themselves don’t spell out where the conflicts come from. The Setting provides the context for the conflicts. It helps the conflicts make sense.

For instance, my game Cutthroat is VERY light on Setting. I barely mention it at all (basically I can sum it all up with “Biker gangs in the 1970’s”). But even though I just barely touch on it, that is enough to give the players all the context they need to create hilarious stories and rivalries among the characters. Take that small bit of Setting away, and everything from the Challenge to the Status Rolls to the Top Dog stop making any kind of sense. Dogs in the Vineyard’s setting focuses heavily on religion. And it is out of the religion that the characters follow that the conflicts in each town arise. Strip out the setting, and you just have a nifty way to roll dice, IMO.

So what about Setting Agnostic/Generic RPGs? Good question. I’m going to divide these two kinds of games into two camps for the purposes of this essay. The first kind is the type of game that gives you procedures for creating your own Setting. Universalis and Prime Time Adventures are examples of this sort of game. The games do not contain an exact Setting, but provide explicit rules for making your own. In fact, it’s part of the fun! The other kind of game is where Setting is implicit. For instance, the core books of ADnD2e had no official “setting”, yet it was very clear that you would be playing in some kind of fantasy world. People often point to GURPS as a game with no Setting. But I would in turn point to the insane amount of supplemental books that’s come out of SJG that deal directly with Setting elements. To say GURPS as a whole doesn’t deal with setting is absurd. It most certainly does. And each group that plays GURPS will have to deal with it in some way also.

So what’s the best use for Setting? That’s another long essay. The main thing to keep in mind when creating the Setting for your game is to make the setting elements drive the conflicts. If your Setting isn’t involved in what the characters are fighting for, then it’s time to redesign it.

Peace,

-Troy

PS: On the topic of Settings, the grandaddy of all settings is coming out soon: Ptolus! I've seen a few previews and from what I read and seen, I give it a preliminary thumbs up! If you're into D20, you really should check this thing out.

Monday, May 15, 2006

Just So Ya Know...

Heya,

Just throwing out a little FYI here. I am officially signed up to be at the Forge booth at GenCon this year! It runs August 10-13ish I believe. If you regularly read this blog and will be there, drop by the Forge booth. I'd love to shake hands and meet ya! :)

Peace,

-Troy

Tuesday, May 09, 2006

When should a Character Die?

Heya,

When designing an RPG, the issue of character death always comes up. Some people feel it is a necessary part of design (untrue), while others feel it should be avoided because it is un-fun play (also untrue). It can be hard sometimes to know when to include and when to leave out character death. To my way of thinking, there are only four reasons to include it in your design: 1) it adds to the atmosphere, 2) it increases the stakes, 3) it fulfills the player’s goal, and 4) it escalates the overall conflict/scenario all players are participating in. Let me break them down one by one.

1. It adds to the atmosphere
It certain games, mainly those that explore the setting or situation, character death can be an integral part of play. In fact, character death is expected, and the lack of it will diminish the fun. I am reminded of many Call of Cthullu games I have participated in and read actual play reports about. There was even a really hilarious thread on RPGnet many years back where people posted the most outlandish and fun way their characters died. For this game, at least the way I’ve seen it played, character death is well accepted, and honestly it’s anticipated. The thing that really makes it work, IMO, is the speed of Chargen. I know many CoC players who can draw up a brand new character in 5 to 10 minutes. So when their character dies, they jump right back in during the next scene no biggie. To me, that’s the key for using character death in this way. If your game has a time-intensive character creation and advancement process (imagine recreating a level 15 character in DnD 3.5 from scratch) then I would counsel against using character death to add atmosphere to your game. Three things to remember for this use of death: Frequent, Fast Chargen, Expected.

2. It increases the stakes
In my game, The Holmes and Watson Committee, players have the option to put their character’s life on the line. Choosing to do so grants them an additional bonus, but also makes the situation a lot more crucial. This is an example of character death increasing the Stakes. Sometimes it’s important to put everything you have on the line to accomplish something important. In RPGs, that can mean everything from nabbing the bad guy (like in Holmes and Watson) or saving a town from corruption (like in Dogs in the Vineyard). For designers, using death to increase the stakes means limiting the conditions where a character death is possible. Usually, that means making it a player option of some kind. Choosing that option ought to grant the player beneficial but dangerous bonuses of some kind. Sorcerer, Dogs in the Vineyard, and The Holmes and Watson Committee are the best examples I can give you of games that do this. Three things to remember for this use of death: Optional, Bonus, and Lethal.

3. Fulfills a Player’s Goal
Some games have players create a destiny or goal for their character to achieve by the end of play. The death of a beloved character can be a very moving experience. I can easily envision a game that incorporates that fact into the mechanics. The payoff would be the character dies with *something*. For instance, a character could die in redeeming himself. He could die with dignity in a war. He could die saving another person. Or he could die in order to allow another character ascend to a great position. The point of using character death in this way is to allow the player to choose the outcomes, but not necessarily the means of the character’s death. I can see a functional design that allows another player to choose the way a character dies so long as the character’s player gets to choose the conditions leading to and the consequences of that death. Three things to remember: Resolves the Character’s Story, Player Controlled, Consequences.

4. It Escalates the Conflict
Escalating the conflict means that the death of one PC impacts all the other PCs and their enemies in a way that makes the conflict more meaningful. Using character death in this way requires that all players be invested in everyone’s characters in some way or fashion. A dungeon crawl where everyone is out for himself to grab as much loot as possible and then skedaddle is not an effective atmosphere for character death that will escalate the conflict. A game where characters are dependant upon each other or where characters are related to each other in some way (blood, sex, loyalty, duty, etc) is the type of game where the death of one will add meaning to the final victory. In cases like this, character death IMO should still be at the option of the players playing the characters. However, the conditions that the game puts the characters in can make and should make death an attractive option. For instance, if I sacrifice my character, everyone else gains two bonus die and has enough time to rescue the princess from the evil sorcerer. Without my character’s death, the mission might fail. Of course now the sorcerer is really pissed and will take his vengeance out on the whole kingdom. Three things to remember: Sacrifice, Relationship, Meaningful.

In any of the four examples, character death needs to be explicitly mechanically supported by your game. Just including a rule like “When your hit points equal zero, your character dies” is not good enough. What does that death mean? Why might a player want his character to die? What does the character’s player get in return for putting his character’s life on the line? What does everyone else get if he does die? Answering these questions will add a lot of depth and meaning to the death mechanics of your game. Consider them carefully as you design.

Peace,

-Troy

Thursday, May 04, 2006

Yet Another Process

Heya,

I have found a third Game Design Process I thought I’d share with you. If you haven’t checked out Ron Edward’s thread on The Forge (Click Here) about his new game “It Was a Mutual Decision” then go check it out. He has a very thorough run-down of the process he used to bring that game from concept to finished product. Also, other people chime in with their own experiences. This thread is a treasure trove of helpful hints, models, and suggestions for designers who intend to write and publish a RPG. Troy’s Rating: two thumbs up! Enjoy :)

Peace,

-Troy