Monday, December 19, 2011

Why playing (lots of different) games is important

During Gencon 2011, I ran into an apocryphal story regarding the then the lead designer of the Classic Battletech franchise. According to the legend (which I have never been able to corroborate), the designer had posted to the Classic Battletech forums the comment that he had played his first game of Battletech in seven years, and had remembered how much fun it was. This of course caused an intense cacophony of hate and questions, as fans questioned how a lead designer could be so out of touch with the game. The person who held control over the future of their game, they supposedly cried, was incompetent to actually lead the game into the future. How could he know what course to plot, if he didn't know what the problems were in the first place?

Now, I'm not a Battletech fan (instead being a rabid fan of the Heavy Gear universe published by Dreampod 9). But being a fan of Heavy Gear I've often expressed a similar frustration rooted in different causes - namely, why exactly are people who aren't familiar with the wargame side of the house running the show? To be sure, there is some element of these frustrations that are the natural effect of wanting your favorite thing (be it a sport, religion or game) to align to your own ideas of how it should be organized. Everybody wants to be a generals, and few want to be troopers. That's normal and expected anytime there's a leadership structure in place.

Focusing on the natural leadership dynamic misses an important criticism that's being made in the above statements, though. Wargames are a hobby primarily, and a hobby with a considerable investment. Smaller wargames in particular tend to be risky expenditures of money due to the lack for used material in smaller communities. Most people want to see their games grow and evolve as time goes on, so that it has a continual lifespan. Unlike video games which tend to be picked up and put down within a span of a month or so, wargamers tend to hope for a long 'shelf-life' during which they can enjoy their chosen system or miniatures. To this end refinements and additional 'hooks' need to be continually introduced into the game, in a way that it maintains its identity but still continues to grow.

To this end, a designer has to understand the community's interpretation of a game in order to improve upon it. And the only way to understand is to play; you have to put models to the table and see how your preconditions stand up in the face of evidence to the contrary. Analysis can only get you so far; most wargames (even simple ones) tend to feature enough complexity that it's nearly impossible to keep the entire ruleset in the front of your mind, much less every permutation of rules intersections in your mind. And that's even before you start to interpret the results of those interactions, and see if they match the end design goals for the system you're working on. Most players understand that very clearly, even if at a instinctual level; how can you understand what's not working if you're not playing with it on a regular basis? If you don't play at all, you are going to be nature be blind to the relevance of flaws as exposed by your community - your decision making is entirely intellectual, logical and without any consideration to the psychological and presence implications of any given rule.

Further compounding the outrage is the observation that every group plays a slightly different game, even if the rules are the same. Interpret a rule slightly differently and it may have a very large impact on the way that the game turns out; what we would loosely call the 'metagame' of your local area. Interpreted one particular way a rule may make artillery more powerful than shooting someone with a rifle, while an equally valid alternate interpretation makes the rifle more powerful. The ambiguity of the English language makes these differences possible and potentially disastrous to a community. So not only should game designers be expected to play, but they should be expected to play lots of different groups. Like any good company head they need insights into how the game is played in small enclaves because the insights they can pickup from those games yields a better 'big picture' view of exactly what the game is in the wild - and how much that diverges from your idea of what the game should be.

Now to this point I've talked about why designers should play their own game; but that's only a part of the picture. Remember, gamers want their games to grow, preferably while keeping the games' identity intact. However, growing the game means expanding the boundaries of the game - which is contrary to the march towards perfection that introspection tends to funnel you towards. There is where other, competing games come to the fore; the time-honored tradition of stea... er, borrowing from others is perhaps the most important tool in any game designer's handbook. It's better to leverage the wargaming community as a whole rather than just the limited subset of community that is relevant to your particular game; by doing so not only do you find novel solutions to related situations in your own game, but you also start to keep a pulse on the industry as a whole.

Taking Heavy Gear as an example, it has problems with its Stealth system. It's been through several iterations of design, with varying degrees of success. In each case though the 'solution' shows obvious signs of 'in-the-box' thinking, trying to make the current system work 'better'. The are fewer signs that someone has sat down and said 'look, Infinity does it this way, and Mercs does it this way, and Warmachine does it this way. Do any of those fit the conceptual model we're gunning for?'. You really need to occasionally step back and look at the problem from a high-level rather than trying to ram a solution in using a shoe-horn.

But to do that, you've got to play. You've got to sit down and figure out what Infinity does that you really like, and what it does that you really hate. You need to play Warmachine and figure out that shooting sucks, which is fine for a medieval game, but note that the abstracted bases works just fine in their case. And you need to play Malifaux to learn about their objectives - what works, and what doesn't - and how it can apply to your game.

In short, to be a good game designer, like anything else in life, you've got to be a professional. You've got to practice the craft of designing a game, of learning about all the possible competitors, and welding all the various pieces you have floating about in your mind - and the minds of your community - into one larger whole. It's got to become something you think about, and wonder about and say 'how can this be better?'. You have to contribute to pushing games forward into the future rather than wallowing in past successes.

In short - in order to be a good game designer, you have to be a good gamer. Otherwise you're just a snake-oil salesman.


  1. Hey, Just wanted to say thanks for taking the time to post on my blog. It was much appreciated.

    Just wanted to say that was an interesting read. And I pretty much agree with you. Games designers who live in glorious isolation invariably muck things up!!!

  2. Thanks! I spend probably too much time thinking about wargaming, and needed a place to vent. Glad you found it useful.

    And I'm happy to post - any questions about the Pod, I can try to answer, here or there!

  3. Well I've followed your blog, and if you are planning on adding more articles I'll put you on my blog roster. It's hardly the world most popular blog but I am getting nearly 2000 hits a day average and peeps seem to follow links on my site. Perhaps it can give you a bit more traffic. :)

  4. Excellent post! Lots of food for thought.