Wagenheimer's Game Development Blog

Another great tips by Jordan Mechner (Prince of Persia Creator).

Tips for game designers

Rereading the advice, I think it stands up well and is more relevant to today’s industry than the 1996 list of tips for designing story-based games I posted last month.

1. Prototype and test key game elements as early as possible.
2. Build the game in incremental steps – Don’t make big design documents.
3. As you go, continue to strengthen what’s strong, and cut what’s weak.
4. Be open to the unexpected – Make the most of emergent properties.
5. Be prepared to sell your project at every stage along the way.
6. It’s harder to sell an original idea than a sequel.
7. Bigger teams and budgets mean bigger pressure to stay on schedule.
8. Don’t invest in an overly grandiose development system.
9. Make sure the player always has a goal (and knows what it is).
10. Give the player clear and constant feedback as to whether he is getting closer to his goal or further away from it.
11. The story should support the game play, not overwhelm it.

(more…)

List of game design tips for narrative games by Jordan Mechner (Prince of Persia Creator).

Tips for game designers

Eons ago, in 1996, Next Generation magazine asked me for a list of game design tips for narrative games. Here’s what I gave them.

Reading it today, some of it feels dated (like the way I refer to the player throughout as “he”), but a lot is as relevant as ever. I especially like #8 and #9.

1. The story is what the player does, not what he watches.
2. List the actions the player actually performs in the game and take a cold hard look at it. Does it sound like fun? (Resist the temptation to embellish. If a cinematic shows the player’s character sneak into a compound, clobber a guard and put on his uniform, the player’s action is “Watch cinematic.” Letting the player click to clobber the guard isn’t much better.)
3. The only significant actions are those that affect the player’s ability to perform future actions. Everything else is bells and whistles.
4. Design a clear and simple interface. The primary task of the interface is to present the player with a choice of the available actions at each moment and to provide instant feedback when the player makes a choice.
5. The player needs a goal at all times, even if it’s a mistaken one. If there’s nothing specific he wishes to accomplish, he will soon get bored, even if the game is rich with graphics and sound. (more…)

Scott Kim takes apart the art of puzzles

At the 2008 EG conference, famed puzzle designer Scott Kim takes us inside the puzzle-maker’s frame of mind. Sampling his career’s work, he introduces a few of the most popular types, and shares the fascinations that inspired some of his best.

(more…)

Game Design Lessons: From Seconds to Hours of Gameplay

Excelent tutorial from The Game Prodigy! It worths a look!

Game Design Lessons: From Seconds to Hours of Gameplay