Difference between revisions of "Game Design Document"
Abel Maciel (talk | contribs) |
Abel Maciel (talk | contribs) (→Structure) |
||
| Line 14: | Line 14: | ||
== Structure == | == Structure == | ||
| − | + | ===I. GAME OVERVIEW=== | |
| − | I. GAME OVERVIEW | ||
A. EXECUTIVE SUMMARY | A. EXECUTIVE SUMMARY | ||
B. STORYLINE (N/A) | B. STORYLINE (N/A) | ||
C. NAMES (N/A) | C. NAMES (N/A) | ||
| − | II. CORE GAMEPLAY | + | ===II. CORE GAMEPLAY=== |
A. MAIN GAME VIEW | A. MAIN GAME VIEW | ||
B. CORE PLAYER ACTIVITY | B. CORE PLAYER ACTIVITY | ||
C. GAME CONTROLS | C. GAME CONTROLS | ||
D. IN-GAME GUI | D. IN-GAME GUI | ||
| − | III. CONTEXTUAL GAMEPLAY | + | ===III. CONTEXTUAL GAMEPLAY=== |
A. GAME SHELL FUNCTIONS | A. GAME SHELL FUNCTIONS | ||
B. GAME FLOW DIAGRAM | B. GAME FLOW DIAGRAM | ||
| Line 30: | Line 29: | ||
D. MULTIPLAYER MECHANICS (N/A) | D. MULTIPLAYER MECHANICS (N/A) | ||
E. SPECIAL FEATURES (N/A) | E. SPECIAL FEATURES (N/A) | ||
| − | IV. GAME ELEMENTS | + | ===IV. GAME ELEMENTS=== |
A. CHARACTERS | A. CHARACTERS | ||
B. LEVEL / MISSION / AREA DESIGNS | B. LEVEL / MISSION / AREA DESIGNS | ||
| Line 41: | Line 40: | ||
A. MUSIC | A. MUSIC | ||
B. SOUND EFFECTS | B. SOUND EFFECTS | ||
| − | VI. CHEATS | + | ===VI. CHEATS=== |
| − | VII. APPENDIX A: GAMEFLOW DIAGRAM | + | ===VII. APPENDIX A: GAMEFLOW DIAGRAM=== |
Revision as of 20:22, 13 April 2020
Template:Video game industry A game design document (often abbreviated GDD) is a highly descriptive living software design document of the design for a video game.[1][2][3][4] A GDD is created and edited by the development team and it is primarily used in the video game industry to organize efforts within a development team. The document is created by the development team as result of collaboration between their designers, artists and programmers as a guiding vision which is used throughout the game development process. When a game is commissioned by a game publisher to the development team, the document must be created by the development team and it is often attached to the agreement between publisher and developer; the developer has to adhere to the GDD during game development process.
Contents
Content
A game design document may be made of text, images, diagrams, concept art, or any applicable media to better illustrate design decisions. Some design documents may include functional prototypes or a chosen game engine for some sections of the game.
Although considered a requirement by many companies, a GDD has no set industry standard form. For example, developers may choose to keep the document as a word processed document, or as an online collaboration tool.
Structure
I. GAME OVERVIEW
A. EXECUTIVE SUMMARY B. STORYLINE (N/A) C. NAMES (N/A)
II. CORE GAMEPLAY
A. MAIN GAME VIEW B. CORE PLAYER ACTIVITY C. GAME CONTROLS D. IN-GAME GUI
III. CONTEXTUAL GAMEPLAY
A. GAME SHELL FUNCTIONS B. GAME FLOW DIAGRAM C. GAME MECHANICS D. MULTIPLAYER MECHANICS (N/A) E. SPECIAL FEATURES (N/A)
IV. GAME ELEMENTS
A. CHARACTERS B. LEVEL / MISSION / AREA DESIGNS C. OBJECTS (N/A) D. INTRO SCENE E. MENU F. HOW TO PLAY G. END SCREEN V. SOUND A. MUSIC B. SOUND EFFECTS
VI. CHEATS
VII. APPENDIX A: GAMEFLOW DIAGRAM
- ↑ Oxland 2004, p. 240
- ↑ Brathwaite, Schreiber 2009, p. 14
- ↑ Bates 2004, p. 276.
- ↑ Bethke 2003, pp. 101–102
