With the hordes of rapid prototype tools available today it’s easy to cobble together a rough draft and start playing. It’s agile, lean, scrum, six-sigma and all that, right? We start with something easy, test our way to success and be releasing withing weeks. Hell, we can release a pre-alpha right now.
Hold your horses, pardner. Why would you want to do that?
Why would you want to prototype immediately at all?
See, there’s a value we’re missing here, a way of thinking that is lost in the process of constant, rapid improvement. With all the clunk removed from the prototyping process we’re left with a game where we’re blind to the clunks. We’ll get brainclunks. Yeah, that’s an actual world, as of right now.
There’s an advantage to good ol’ waterfall style game development, at least at the very beginning of the process. If we start out with a clunky prototype, one that takes effort to handle, we must focus on the basic game mechanics, the stuff that’s supposed to make our games fun. That’s what designing on paper does. You can’t script away the boring, broken pieces, can’t smooth out bad game play with motion. No “it’s only ten clicks away, let’s click as rapidly as we can and get over the boring part”. When the boring part’s on paper, and you need to move every paper once for every click, you’ll feel the boring as an un-peeled horse chestnut up your wazoo.
That’s good.
You want to feel the boredom. You want to feel it right through your excitement over your grand new idea. You want to feel it as acutely and as rapidly as possible. Shove those chestnuts in, baby!
That’s the quickest way to break your design.
And break it you will, whether it’s the itsy-bitsy breakages in an agile process or the huge, big ones of “uh-oh, this game stinks”. Get the big ones out of the way first, then start in on the little ones or you’ll end up realizing that every patch is just trying to give CPR to a carcass. The horse was dead before you rode it in, bro. That’s why you had to carry it over. Smell the stink and either start from scratch or get a new horse. Don’t polish the corpse, you’ll only end up with more chestnuts.
No, we’re not telling why the horse died.
But back to business. Designing using clunky tools exacerbates the problems in a design. So playtest using clunky, ugly, smeared materials with coffee stains on them. Playtest using bad colors, blacked out images, unreadable type. If your testers still enjoy the game then you know that you’ve got a winner. Then you can start coding.
Because you’ve got a vision that survived paper playtesting.
Of course you’ll have another problem: who’ll want to playtest a badly executed game idea? The sad answer is: only you. Only you will care enough to actually try it out. If you’re lucky, very, very lucky, you’ll find a friend or two willing to help. Value those friends, and don’t abuse their willingness to do clunky playtests.
So what do you need to do a clunky playtest? Paper, pen, that’s it. Maybe a pair of scissors. Maybe some dice. Think “tabletop 100 years ago”. That really is all you need and you need less than you think you need.
Me, I’m a board game designer. I’ve got lots of nifty miniatures, cool meeples, cubes, life counters, dice in every shade and color imaginable. I’ve even got custom boards and playmats with everything from castles to starscapes on them. I don’t use them. Not in my clunky platests.
The nifty bits are reserved for when I take my game public, for the betatesting when all the problems I can hunt down solo are dead and rotting. When I playtest solo I try to do it with as few elements as possible, with as few mechanics as possible and as little as possible. That’s right. You don’t want to playtest your game a lot. Remember Yoda: break, or break not, and you’d better break if it’s even remotely breakable.
Here’s an example from one of my playtests:
It’s a playtest of a thematic population control wargame. Can’t you see the Mongol hordes sweeping in from the right? Me neither, and that’s the point. As I sat there trying to keep track of invisible armies with only pen and paper (no miniatures, remember?) I realized that my idea for this game wasn’t enough. It simply wasn’t fun the way the design stated it should work.
It took me all of half an hour to figure that out. If I’d had toys to make it more appealing it would have taken me two hours. If I’d have had a full panoply of graphics and minis it would have taken me dozens of playtests. Cool toys can hide a lot. So remove them and get down to basics until you are confident that you can spot the flaws and potential flaws past the pink puffs of your enthusiasm blows in your face.
But when you get to that point you’re pretty much an expert.
5 comments
Zac J Wooddy (@ZacWooddy)
I agree completely with the concept of “if its bones are boring, putting on skin aint gonna help it”, But what’s your thoughts on a game like Axis and Allies?
I read Jesse Schell’s “The Art of Game Design” and he discussed how the plastic miniatures added more immersion to the game by allowing you to see your soldiers, tanks and planes represented on the map, as opposed to the cardboard circles the older version had.
The game’s mechanics were pretty much the same compared to its older version ((or the at least the version my father claims he played)), but it was the addition of the miniatures that gave Axis and Allies that special feeling of commanding an army… as opposed to commanding bran flakes.
I’ve played Axis and Alies and loved it, but I can’t imagine liking it as much if I only had those cardboard circles instead of the model soldiers and vehicles.
Filip Wiltgren
A&A is the perfect example of a game that moved towards being a toy. It’s also a perfect example of a game that needs the fluff to be interesting.
As you said, playing A&A with tokens instead of miniatures would be a rather horrible experience. This is because it’s not a very good game at it’s core – the “game” aspects are much less developed than the “toy” aspects. Which is fine, if you’re aiming to make a toy or to keep a game selling by using an older generation to promote it to a younger one (like with Monopoly, for example, another game that isn’t very good but that still sells).
And by not good, I mean that A&A is counter-intuitive, several of the sides are rather irrelevant (the big fight happening between Germany and the USSR – what has the player playing Italy to do, really?), and there are clear non-win and must-play tactics.
Thus, if you’re designing a game, and you start with a beautiful game, you’ll be lured in by the fluff, and will overlook the errors of game design that you’re making. Also, if you invest time in fluff, you’re less likely to try things that might make the game better, but which would remove that fluff.
Martyn F
Exactly! Thanks for you insights.
Although I very often use a spreadsheet, just to shape the cards and simple board. That way the second prototype mostly takes less work than writing/drawing it all again.
Filip Wiltgren
True. My very first rookie mistake (which you can read about: http://www.wiltgren.com/2012/12/03/my-first-time-confessions-of-a-virgin-designer/) was making a nice (for that time) prototype without realizing that I needed to test my game first…