Jeff Strain, co-founder of ArenaNet, gave a very interesting speech on the challenges of creating a successful MMO. Here’s an important point:

Before you start building the ultimate MMO, you should accept that “MMO” is a technology, not a game design. It still feels like many MMOs are trying to build on the fundamental designs established by UO and EQ in the late ’90s. In the heyday of Doom and Quake we all eventually realized that “3D” was a technology, distinct from the “FPS,” which was a game design. It’s time we accepted that for MMOs as well. We are finding ways to overcome many of the limitations of the technology that dictated the early MMO design, such as Internet latency and limited global scalability. These improvements can enable a new class of online games that break out of the traditional MMO mold and explore new territory. It can be a daunting proposition to willfully walk away from what seems to be a “sure thing” in game design, but lack of differentiation is probably the number one reason that MMOs fail, so we all need to leave the comfort zone and start innovating, or risk creating yet another “me too” MMO.

Also, similar to Civ4‘s development, they started an external alpha test years before release:

It’s crucial to get feedback from outside the development team at a very early stage. We started alpha testing over three years before Guild Wars was released. To say that the game was crude at that point is a bit of an understatement – I think we’re still tracking down screenshots from that period and trying to get them burned. It was a very controversial decision at the time, and generated a lot of heated debate within the development team, because it flew in the face of the traditional wisdom that you should never show anyone outside the company what you are working on until it is perfect. I wish I could tell you that every tester we brought into the alpha test was honest, abided by the NDA, and gave the development team carefully-considered and high-quality feedback after each of the tri-weekly play sessions, but that would not be the truth. There were several times after we launched the program that we revisited the notion and discussed whether the good outweighed the bad. But we kept at it, and by the time Guild Wars shipped in April, 2005 it was clear that the game had benefited from the alpha test program, and today we consider it an essential component of the development process.

So, I just gave an interview on tutorials, during which I had hoped to give a concrete example of a game which handled its tutorial poorly. Unfortunately, my memory failed me as most game tutorials eventually seem to blur together. Naturally, just today I saw a perfect example of how not to write one. The game is called Bloxorz, and it is a quite good puzzle game that feels a bit like a turn-based version of Marble Madness, if that makes any sense.

At any rate, when the game begins, the player is moved through 9 screens that give instructions on how to play. The problem is that this information is simply too much for the player to digest before he or she has even a tangible sense of how the game works. Simply put, gameplay cannot be described with just words. Did you understand my Marble Madness analogy in the paragraph above? Probably not. However, as soon as you actually play the first level, the basic gameplay becomes quite clear.

Thus, advanced features, like switches and teleports, are meaningless to the player until he or she actually understands the core game. The tutorial could be twice as effective if each of the instructions screens was simply placed before the level in which the new feature first appears. The designer is essentially forcing the player to read the entire manual cover to cover and then hoping that everything gets remembered. Information should be handed out to the player only when needed.

Give the game a try, it’s fun! Just not the best tutorial experience…

Much to my surprise, my articles on game design mistakes made it onto last week’s Games for Windows Podcast. I’m a regular listener, so it was cool to hear them talking about this blog. They discussed the first two points and the last, which was the one about stories. Just to be clear, I am not anti-story. I simply believe that designers should acknowledge that including a fixed story in a game comes at a cost to other potential features. Often, this trade-off makes sense – for example, RPG and adventure games would be hard to imagine without stories. However, sometimes games which could have open-ended goals (such as strategy games) limit their replayability by shoehorning in an unnecessary story.

Oh, and they mentioned that my blog is hard to read because the font is too small. Good point. I really need to actually figure out how to use Movable Type soon…

…this wedding cake is your goal:

Wow.

I did an interview recently at Boing Boing Gadgets on tutorials. Here’s an excerpt:

So what’s the best real world example of tutorial you’ve ever come across?

I’ve seen lots of good tutorials, but I’m finding it hard to think of great ones. Making a great tutorial may be the hardest part of the developments process; it’s certainly the part I find the hardest. I would like to mention one interesting thing that Prince of Persia: Sands of Time did which served as a tutorial even though it didn’t feel like one. Between levels, you would see a black-and-white dream sequence which showed some of the moves you needed to make to pass the upcoming area. The visuals were not specific enough that it spoiled the puzzles, but they did introduce you to the advanced moves you would need so that you were better prepared for a new challenge. I had never done a wall run before, but when I saw one during the dream sequence, I immediately became aware that there was a new skill I should master in order to pass the next level. The game still took the time to teach me the literal button presses needed to do a wall run, but the dream sequence did a great job of making me want to learn this new move because I saw the context for it. Finding a way to show off cool features to encourage learning is a great idea—Google seems to be doing this as well with their product video demos for Street View and whatnot.

Continuing on from my previous post, here are four more common mistakes made by game developers.

5. Hidden code/data
Protecting your code and data is a very natural instinct – after all, you may have spent years working on the project, developing unique features, pushing the boundaries of the genre. Giving away the innards of your game is a hard step for many developers – especially executives – to take. Nonetheless, we released the game/AI source code for Civ 4 over a year ago, and – so far – the results have been fantastic. Three fan-made mods were included in the Beyond the Sword expansion – Derek Paxton’s Fall from Heaven: Age of Ice, Gabriele Trovato’s Rhye’s and Fall of Civilization, and Dale Kent’s WWII: The Road to War – and so far, these mods have been heralded as one of the product’s strongest features. To be clear, these mods would have been nowhere near as deep or compelling (or even possible) if we had not released our source code. I should specify that for many PC developers, I’m preaching to the choir, so I’d like to be very specific about which genre I am calling out – strategy games. For whatever reason (perhaps the lack of a pioneering developer like id?), strategy developers have been much more closed off to modding than their shooter and RPG brethren. Sure, there are exceptions, like Blizzard’s fantastic scenario editor for WarCraft 3, but by and large, strategy modders do not have many places to turn for platforms on which to work, which was one reason we felt compelled to focus on modding for Civ 4. Giving stuff away can feel good. It also feels smart.

6. Anti-piracy paranoia
The damage that piracy does to our industry is impossible to calculate but also impossible to ignore. Few company heads can be as brave as Brad Wardell and just leave out copy protection altogether. Thus, having some sort of mechanism to stop casual piracy is a given but what is not a given is the hoops companies will make their customers jump through just to be able to start the game. The most important question to ask when considering these protections is “will this added security actually increase our sales?” A good place to be lenient, for example, is with local multi-player games – in other words, can players without the disk join a multi-player game hosted by a legitimate copy. Starcraft let you “spawn” extra copies of the game that could only join LAN multi-player games. (Interestingly, this is the same model that Ticket to Ride employs on the Net. It is always free to join a game but only paying customers can host.) Allowing unlimited LAN play was our unofficial policy for Civ 4 as well. The game does a disk check when you start the EXE but not when you actually launch the game; thus, a group of 4 friends could just pass one disk around for local multiplayer. We do not believe players are willing to buy extra discs just for the ability to play multiplayer at a LAN party, which are rare events. However, we would love for new players to be introduced to Civ in these environments, encouraged by their friends who are already fans. At some point, they are going to want to try single-player – in which case, it is time for a trip down to the local Best Buy.

7. Black box mechanics
Sometime during the late-90’s, around when Black & White was being developed, the concept of an interface-less game came into vogue. The idea was that interfaces were holding games back from larger, more mainstream audiences. Ever since then, I have noticed a discernible trend to hide game mechanics from the player. Age of Kings shipped in 1999 with an incredible reference card listing every cost, value, and modifier in the game. With most modern RTS’s, however, you’re lucky if the manual actually contains numbers. I want to emphasize that the answer here is not to bathe the players in complicated mathematics in the name of transparency. Instead, designers should think of their interfaces as having two levels: a teaching level and a reference level. The teaching level focuses on first-time players who need to know the basics, like how to build a tank and go kill the bad guys. The reference level should answer any question the player can think of about how a game mechanic works. It is perfectly fine, by the way, to put this info inside of a separate in-game resource, like the Civilopedia. Rise of Legends implemented an interesting version of this two-interfaces idea. Most of the popup help in the game had an “advanced” mode that you could unlock by holding down a key, giving you significantly more details about the game’s underlying mechanics.

8. Putting story in the wrong places
I was tempted to come up with 7 things not to do and just leave off the story one as I’m sure it’s my most controversial point. A bunch of people will disagree with me over the place of story in games, so let me just say up front that I know that I am wrong. I still want to make my point, though. I don’t like story in games. I don’t like the boring cut-scenes. I don’t like the stereotyped characters. I don’t like the plots that I have no control over (and, sorry, the Bioware you-are-either-God-or-Satan twists count too). I especially don’t like it when games stop me from fast-forwarding through the crappy dialogue (I’m looking at you, Japan). But what I really hate is when a story gets stuck somewhere it really doesn’t belong. Like in a strategy game. After all, strategy games are the original games. Humans first discovered gameplay with backgammon and chess and go; it’s a noble tradition. The “story” in a strategy game is the game itself. Layering a story onto an RTS campaign is like putting a copy of Hamlet in my pie. I mean, sure, Hamlet is a great play, but my pie would also sure taste better without it! Put another way, how much better of a game would Rise of Legends have been (and it was already a great game) if they had given up on creating a story-based campaign and instead iterated on the cool Conquer-the-World mode from Rise of Nations? Ironically, the campaign mode was my favorite way to play RoL. I loved that you could only acquire technologies and advanced units on the strategic map between missions, which helped to simplify the core RTS game. However, I enjoyed the campaign in spite of the story, not because of it. The key point here is that, for the sake of chasing a story, Big Huge Games missed a big opportunity to match a great core RTS game with a simple, overarching strategy layer that could be infinitely replayable. They are not alone; almost every other RTS developer seems to be falling into the same trap, and I don’t know why.

Of course, if I ever made an RPG, I would probably name the bad guy Foozle, so what do I know?

Well, for better or worse, these are the eight things I hate seeing in games, especially strategy games. What about you?

Fable
The Darkness Demo
Heavenly Sword Demo
Psychonauts
Selling Out

Wonder how long he can keep it up…