SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

The Design Document

fausta avatar
fausta
11 diapositives · 321 Views · Jul 29, 2014

The Design Document. 04.04.2013. The Design Document . Introduction Game Mechanics Artificial Intelligence Characters, Items, and Objects/Mechanisms Story Overview Game progression System Menus. Introduction. Single page Game’s most compelling points Sum up the game’s story

The Design Document - slide 1
01 / 11The Design Document
1 / 17

Télécharger la présentation

The Design Document
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. The Design Document 04.04.2013

  2. The Design Document • Introduction • Game Mechanics • Artificial Intelligence • Characters, Items, and Objects/Mechanisms • Story Overview • Game progression • System Menus

  3. Introduction • Single page • Game’s most compelling points • Sum up the game’s story • Discuss different aspects of your gameplay • Conclusion

  4. Game Mechanics • Describes what players are allowed to do in the game and how the game is played • Introduce the simpler moves then more complex ones. • Describe how puzzles function • Modes should be described. • Technology • How the players see the world. • GUI

  5. Artificial Intelligence • How the world will react to the players’ actions • How actions will be initiated. • Are they smart? • AI for a strategy game • What sorts of strategies will the enemy use to overwhelm the players’ units? • How will the units work together? • If applicable, when will the computer player decide to build more units, and how many will it make?

  6. Characters, Items, and Objects/Mechanisms • Buildings in SimCity, blocks in Tetris • Characters: active and non player controlled • Items: notes, keys, or health elixirs… • Objects/Mechanisms: doors, switches, puzzle elements… • A game may contain all or some of them. • There may be more elements like skills and spells. • Group different subclasses together

  7. Story Overview • A brief Story Overview, if story exists. • Big picture • Try to make it compelling.

  8. Game progression • Describe in detail what challenges players will face • What story transpires on them • Visual aesthetics of the levels • How should the player feel • How difficult a level will be • The conditions under which certain enemies appear change

  9. System Menus • How players will save and load their game • Type of interface (mouse, keyboard or both)

  10. Bad design documents • Meaningless descriptions like “gameplay will be fun” and “responsiveness will be sharp.” “Players will be given an option of many cool weapons. For example, the Gargantuan Kaboom does twice the damage of the players’ other weapons and has a special effect. The Barboon Harpoon will allow users to kill enemies at a distance with a nice camera effect. Other weapons will be just as fun and cool . . . ” • Poor table of contents and the lack of an index • Talking about back story too much • No information about the gameplay • Too much detail • Including source codes • Technically unrealistic • Has not been updated

  11. Conclusion • A design document should be: • Simple • Easy to read (not too long) • Comprehensible • Updated