Monday, May 10, 2010

The 10 most common mistakes made by Game Designers - Part 1

When you're designing a game, you've always got to keep in mind the poor player. Your poor player is the entire reason you're making a game. Sure, you could be making a game for yourself but that's a bit like writing a book or drawing a picture for yourself. You're already going to know how it turns out and there isn't any sense of discovery when you play it.

http://farm4.static.flickr.com/3035/3028314931_53d4aa5fc2.jpg

Today, we're going to get to know your poor player. We're going to take a look at the 10 most common mistakes made by Game Designers, and how to avoid them. These aren't just 10 mistakes I've seen teaching Kahootz in schools, or 10 mistakes I alone have made while designing games. These are the top 10 mistakes that are being made by even some of the best designers.

10. Making the game too hard
You've created an elaborate puzzle game where the player has to pit their wits against a series of fiendishly difficult riddles, math problems and logic patterns, but your player has just spent the last hour trying to work out the code to get in the front door.

http://farm1.static.flickr.com/201/490907537_6724705f74.jpg

High-Profile Sinners: Myst, The Castle of Dr. Brain, The Legend of Zelda

Why it happens:
You've got some great puzzles for a game. They're going to really confuse your player but they're obvious if you think about it, right? Unfortunately you aren't always going to be around if your player can't work out why the door knob won't turn, even though you know it's obviously because they need to pick the lock.

Hot to avoid it:
Simply put, your player might need a little bit more of a hint. Is there a way you could use sound and pictures to suggest that the door is locked? Maybe a thunking sound or an animation that shows the door getting caught on something just as it starts to open? This is called player-feedback, and it lets your player know what reaction they see whenever they try to do something in the game. Player-feedback is critical, it helps the player feel more involved in the game and teaches the player some of the rules of the game (such as, sometimes you have to pick the lock to open a door).

9. Making the game too easy
You've got another great puzzle, but if you make things too difficult you're going to end up with a frustrated player. You give them hints and make everything as clear as possible. Suddenly you find no one wants to play your game because it's too easy. What went wrong?

http://farm3.static.flickr.com/2469/3665571072_0bc5baf25b.jpg?v=0

High-Profile Sinners:
Red Faction: Guerilla

Why it happens:
It happens when game designers try to make their game easier, but accidentally go too far and take away all the challenge by giving the wrong kinds of hints. Players are very happy to play a game that is challenging or difficult if they have clear objectives. Hints and player-feedback should not patronise the player by giving away every little secret or lighting the way to each little hidden treasure. Learning and exploring is what makes a game fun, don't let the hints take away the fun.

How to avoid it:
Be careful not to give too much away when your giving hints. Game Designers have to be very careful to balance what hints they give out and when. Hints and player-feedback are important, but it's the way you give those hints that are the key. As any writer will tell you: show don't tell. Instead of using huge swathes of text to signpost every little part of your game, maybe you could use sounds or images. Let's say, for example, that your player walks into a toxic gas cloud and falls ill. A game might flash a warning text on the screen telling the player where to run to for medical attention, but a good game might make everything you see turn green and the character might start limping and struggling to walk in a straight line. This sudden change leads to a sense of urgency and forces your player to engage with your game, to remember where they last saw a first aid tent for example.

8. Teasing the player
Your player has just discovered a wonderful new magic power, or a fantastic new piece of equipment that suddenly makes even the most difficult enemy a mere distraction. It's fun playing with their new 'superpowers'. But then they're taken away, without warning, never to return.

Where did I put my black-hole anti-matter blaster? I had it just a second ago...

High-Profile Sinners: Half-Life, Splinter Cell

Why it happens:
It's cool when you get a new toy, especially when that toy is a powerful mega-robot with hover jets and invisibility.

There it is, hovering behind the other invisible mega-robot.

Game Designers love giving players new toys, and players love getting new toys. When done well getting a new 'toy' revitalises the game and gives the player more enjoyment out of familiar, predictable environments as the player effectively relearns how to interact with the game. The problem is that sometimes these toys are too powerful. Nothing is a threat to the player anymore. The game is no longer any fun without the threat of defeat. The Game Designer has realised that they've made a mistake by letting the player get so powerful. So the game pulls a swifty: a contrived reason is found for the player to lose these new-found toys - whether that be theft, betrayal or unexpected catastrophic meltdown. It's not clean and it's not pretty, but it happens.

How to avoid it:
Let me clarify that the problem isn't giving players these toys in the first place, in fact offering treasures and toys like this can be a great way to reward your player and keep them engaged in your game. The problem is the way in which these toys are suddenly yanked out from under your player. It's perfectly acceptable, and in fact quite fun, if there's a good reason for suddenly losing all your hard earned treasures. Good Game Design encourages a strong story. If you're going to give your player a toy, make sure they know why they're getting it and make sure they understand the limits you've placed on using it. For example, a catapult would be great fun to roll around a medieval battlefield in, reigning down unmitigated destruction. But once the battle is won, there's no use in a lumbering catapult when your actual job (monster-hunter) requires stealth and good aim. In fact, you only have such a machine because the King lent it to you, he may well order you to return his expensive contraption once you've saved the day.

We'll continue the list over the next few weeks until we reveal the number one most common mistake a game designer can fall foul of. Hopefully we'll see you all again soon.

Stay tuned!

Anthony

1 comment:

  1. > The Legend of Zelda
    > Too hard

    This is absurd. Zelda games are not too hard. If they were, then why do so many people want to see "Master Quest" modes on more games in the series?

    > Half-Life
    > Your weapons are taken away and you can never get them back

    This is false. You do get your weapons taken away, yes. But you get these same types of weapons back (and some new ones) rather quickly.

    ReplyDelete