Game Design Document Template
Game Design Document Template
Game Name:
Genre:
Game Elements:
Game elements are the basic activities the player will be doing for fun
Player:
The number of players that can play the game at once
TECHNICAL SPECS
Technical Form:
Basically there are 2D graphics (flat) and 3D graphics (form)
View:
Camera view from which the player will experience the game
Platform:
iOS, Android, Mac, PC
Language:
C#, C++, Ruby, Java
Device:
PC, Mobile, Console
GAME PLAY
Use the game play section to create a descriptive paragraph about how the game is played. You want the use tor imagine they are
actually playing the game. Try not to use generic (i.e., broad, non-descriptive) terms when writing about the game play. For example,
few readers want to hear statements such as, “enemy_1 will have more hit points than
enemy_2.” Instead, it’s better to make statements like, “The Lazarus Fighter has more armour than the Apollo Fighter.”
Onion Diagram
DESIGN DOCUMENT
This document describes how GameObjects behave, how they’re controlled and their properties. This is often referred to as the
“mechanics” of the game. This documentation is primarily concerned with
the game itself. This part of the document is meant to be modular, meaning you could have several different
Game Design Documents attached to the Concept Document.
Design Guidelines
This is an important statement about any creative restrictions that need to be considered and includes brief statements about the general
(i.e., overall) goal of the design.
Player Definitions
A suggested list may include:
• Health
• Weapons
• Actions
Player Properties
Each property should mention a feedback as a result of the property changing.