Game Design

[Anable]

I had a general question about game design rather than a specific piece of code. I think that qualifies for this forum. In any case my question is about the process of game development. What order do you go in to make a game? Let's say I have an engine and a design statement (ie. what goes in the game, rules, story, etc). Now what?

Since I have no design experience I can only assume it goes something like this:

1. Put on paper what this game is going to be like.
2. Find engine to support features you want.
3. Art team gets to work on models, textures, etc.
4. Somebody programs a map editor for the engine.
5. Mappers get to work.
6. Programmers impliment engine support for maps created.
7. Magic
8. Game is finished!

Seriously, I have no idea. Is there a good book on all this?

 

[Ansur]

I'm no game-developer but I would think there's an iterative process in creating a game.

I think they spend lots and lots of time on discussing stuff, eg. a map. Someone at last creates it, and then there's more discussion which parts should be eg. strategically better.
This would also apply on other areas of the development.

What you are saying is ofcourse things that happen during the progress of the game, though probably a bit more complicated. The art team can't really start working on textures if they're not sure where and when these things will be used, what they should contain, how optimised they should be.
The same goes for a mapper, you don't want to create an Area51 high-tech base if eventually you come to realise you're building a WW2 shooter.

Just my 2 cents ofcourse.


Maybe look through these categories:
http://www.gamedev.net/columns/books/
Not sure if there's something there, but its worth a check.

 

[selfdestruct]

Game Creation and Careers, by Marc Saltzman.

http://www.peachpit.com/title/0735713677

All you need to know.