Speculative non-fiction.

Quiet Babylon

Scoring in Gymnastics

August 23rd, 2008 by Tim Maly

So I’m reading about the new Olympics Gymnastics scoring in Slate. It’s a compelling argument for making a scoring system which has no upper limit, rather than having some weird idea of perfection in what is ultimately a creative game. There is a “B” score which starts at 10 and goes down every time you make a mistake. Then there is an “A” score.

The “A” score measures the difficulty of the routine. A relatively easy move like a one-handed cartwheel on the balance beam adds 0.1 to your A score, while bringing off the astonishing Arabian double front layout rakes in 0.7. (And no, you can’t inflate your score by doing 10 cartwheels in a row; only the 10 most difficult elements are counted, and repeated elements don’t count at all.) Performing two or more elements in close succession tacks on “connection value” of up to 0.2 points per transition. The way to max out your A score, then, is to cram the toughest possible moves into your routine and pack them as tightly together as you can manage.

Guys, they have CHAINS and COMBOS in gymnastics now!

Filed under game design having View Comments

Playing by All the Rules

July 10th, 2008 by Tim Maly

David Sirlin’s Playing to Win series of articles changed the way that I thought about games. Until I read them, I was a scrub.

Now, everyone begins as a scrub—it takes time to learn the game to get to a point where you know what you’re doing. There is the mistaken notion, though, that by merely continuing to play or “learn” the game, that one can become a top player. In reality, the “scrub” has many more mental obstacles to overcome than anything actually going on during the game. The scrub has lost the game even before it starts. He’s lost the game before he’s chosen his character. He’s lost the game even before the decision of which game is to be played has been made. His problem? He does not play to win.

The scrub would take great issue with this statement for he usually believes that he is playing to win, but he is bound up by an intricate construct of fictitious rules that prevent him from ever truly competing. These made up rules vary from game to game, of course, but their character remains constant. In Street Fighter, for example, the scrub labels a wide variety of tactics and situations “cheap.” So-called “cheapness” is truly the mantra of the scrub.

I was a Starcraft scrub. I logged onto Battle.NET and only played “friendly” games marked NO RUSHING and whatnot. Every now and then, some jerk would ruin the game by rushing even though it said NO RUSHING and someone would disconnect in disgust. After months and months of play, I never got any better. It never occurred to me that it would be useful to make more than one Barracks (doing so doubles the speed that you can pump out Marines). I was totally inefficient with my resources. I more or less thought that rushing was unbeatable and totally annoying and game-ruining.

And then someone linked me to the Terran build order. Suddenly, I could defend against an early game rush. I started looking forwards to them. It turned out that most players who joined a NO RUSHING game in order to rush, didn’t have any skills past the first attack – they were relying on the other guy quitting in anger.

I’ve never had the drive to become anything close to a professional player, but Sirlin’s series (now a book) gave me a new understanding of truly competitive play. It taught me not to dismiss any move as “cheap” no matter the game.

There is a certain arrogance that comes from being a scrub. It’s the idea that you know better than the designers whether or not their game is balanced. It’s the lazy assumption that because you can’t figure out a better way, that there is no better way. It’s blinding yourself to whole rich fields of strategy and tactics. It’s weirdly choosing not to play the entire game and then blaming others for failing to make the same mistake.

It is in appreciation of the truly competitive game player, the one who understands in detail how the mechanics work and uses ALL of them, that I present the following, taken from a Snopes article about a truly strange soccer game.

Barbados needed to win the game by two clear goals in order to progress to the next round. Now the trouble was caused by a daft rule in the competition which stated that in the event of a game going to penalty kicks, the winner of the penalty kicks would be awarded a 2-0 victory.

With 5 minutes to go, Barbados were leading 2-1, and going out of the tournament (because they needed to win by 2 clear goals). Then, when they realized they were probably not going to score against Grenada’s massed defence, they turned round, and deliberately scored on their own goal to level the scores and take the game into penalties. Grenada, themselves not being stupid, realized what was going on, and then attempted to score an own goal themselves. However, the Barbados players started defending their opponents goal to prevent this.

In the last five minutes, spectators were treated to the incredible sight of both team’s defending their opponents goal against attackers desperately trying to score an own goal and goalkeepers trying to throw the ball into their own net. The game went to penalties, which Barbados won and so were awarded a 2-0 victory and progressed to the next round.

Filed under game design having View Comments

‘deconstructulator’ is an excellent word

June 30th, 2008 by Tim Maly

Here is one of the most amazing glimpses into the behind the scenes of video game development I’ve ever seen: deconstructulator

This NES emulator shows how Super Mario Bros. sprites and graphics are stored both on the cartridge and in active memory. It’s really cool.

As a bonus, you get to play the first level of Super Mario Bros. and be reminded of how it’s one of the finest examples of a tutorial level despite (maybe because of) having no text, videos or scripted events. Watch how everything you need to learn is carefully broken down into logical bits, each one building on the last section of the level.

So good.

Filed under game design having View Comments

Calibrating Difficulty

June 27th, 2008 by Tim Maly

David Edery on how hard (or easy) you should make your games:

Too many of us are still holding onto design philosophies that were born in the days of quarter-gobbling arcade games. Too many developers get most of their design feedback from QA teams made up of hardcore gamers who have played a game way more than most normal people ever will. Making a game “just hard enough” (be that very hard or very easy, depending on the person playing) is one of the primary keys to fun — and, I think, an under-appreciated way to significantly increase sales. It deserves more attention from our industry, even as we search for ways to incorporate meaningful, educational, and remarkable consequences back into our games.

I’ve long been a fan of the approach of having multiple difficulty levels at once in the same place, using things like optional badges, multiple levels of success and bonus objectives. The simplest form can be found in most racing games, which allow you to pass a race in 1st, 2nd or 3rd place.

Medals, optional missing objectives, secrets, collectibles, level (and game) completion percentages – all of these allow you to have more than one level of difficulty on the same map at the same time, which can substantially reduce QA time and other design problems that come from a situation where you need to run the same content more than once during testing because the rules have changed in some way. If advanced players have the same experience as regular players, except that they skip less, a lot less can go wrong.

David Sirlin’s excellent analysis of Donkey Kong Country 2’s secrets was the first writing that got me thinking this way. Time and time again, working on small games with tight deadlines and short QA cycles, we took advantage of this technique.

This is not to say that it’s impossible to do dynamic difficulty well. People smarter than me are already working on better automated ways of adjusting difficulty in real time and presumably, they’ve solved the QA problem. I wonder how they’ll solve the emotional problem. Some people love being frustrated by games and some people hate them. Until game systems can detect how mad you are, the system will have to err in one direction or the other.

A fixed difficulty with a range of levels of success is the best of both worlds. Instead of dynamically adjusting difficulty is that it allows the player to decide for themselves how difficult they want the game to be, in real time, in a highly contextualized way. If the one section is too frustrating, then they can ignore the side missions and just get things done. If another is going really well, they can reach for the gold. If it’s going poorly but they are still enjoying themselves, they can reach for the gold anyway.

Plus, it makes it easier to compare the size of your achievements.

Filed under game design having View Comments

Swamped

June 18th, 2008 by Tim Maly

Falling behind on my completely arbitrary and non-enforced posting schedule. So here is a link to a classic Old Man Murray article. Who Killed Adventure Games.

Filed under criticism, game design having View Comments

« Previous Entries