|
|
# Game idea description (concept) => Game Design Document
|
|
|
|
|
|
There are typically three phases when designing a game. First, you create your game idea (and pitch it) to others and then you deside whether your game will be developed. If your game idea passes this gate, then you start writing the actual game design document and, as the third phase, the actual project plan including schedule, budget etc. See [http://www.gamasutra.com/view/feature/131632/creating_a_great_design_document.php](http://www.gamasutra.com/view/feature/131632/creating_a_great_design_document.php) for more details.
|
|
|
|
|
|
|
|
|
|
|
|
# 2. Game Design Document
|
|
|
# Game Design Document
|
|
|
|
|
|
Game Design Document is the so called "Bible of game development project". It's a living design document you will fill and update during the development of your game project. It's a method of communication between the developers with various roles and tasks. Game Design Document is usually attached in a contract with a publisher.
|
|
|
|
|
|
You can have text, images, diagrams, concept art and other media. If you do your GDD in a wiki, you can also use links to refer to documents outside of the GDD. The form of the GDD has no industry standard. It can be a word document or a living document in a wiki for example. We strongly suggest you to use wiki, shared google document or anything else that is 'living' and easy for everyone to see and update!
|
|
|
|
|
|
GDD is the most important document in this course. It should be 10-40 pages long. Return a link to your GDD in [Optima](https://optima.jamk.fi/)
|
|
|
GDD is the most important document in this and the Game Development Project course.
|
|
|
|
|
|
Templates and examples:
|
|
|
|
... | ... | |