Example documents for making games
Game Design Document (GDD) - marketing doc
New Zealand Centre of Digital Excellence (Code) have published a description of what constitutes a game design document to be used when seeking funding for a game.
Your browser does not support viewing this document. Click here to download the document.
Game Design Document (GDD) - working doc - visual novel
The actual working document is a design guide for the team.
Usually incorporates top level art direction, but not same as Art Bible.
Usually incorporates top level programming direction but not same as Technical Design Document (TDD).
Usually incorporates timelines, but not same as Production Plan Document (PPD).
Needs to have headings so users can click to go straight to the right place.
This GDD is for a visual novel so it misses whole sections about interactivity including detailed game mechanics.
This GDD incorporates marketing research which is usually shown in marketing documents.
Usually incorporates top level art direction, but not same as Art Bible.
Usually incorporates top level programming direction but not same as Technical Design Document (TDD).
Usually incorporates timelines, but not same as Production Plan Document (PPD).
Needs to have headings so users can click to go straight to the right place.
This GDD is for a visual novel so it misses whole sections about interactivity including detailed game mechanics.
This GDD incorporates marketing research which is usually shown in marketing documents.
Your browser does not support viewing this document. Click here to download the document.
Production Plan Document (PPD)
These are plans for student games - basically, make asset lists and milestones.
Note the risk assessment and contingency plan.
Note the version control.
Note the risk assessment and contingency plan.
Note the version control.
Technical Design Document
This is an old version (we are up to version 29 now) but it shows the kinds of things that need to be decided.
We made it in Excel, with tabs for each topic, which made better flowcharts, but made it harder to rearrange.
We didn't keep proper version control because we hadn't realised how many changes would be made.
We made it in Excel, with tabs for each topic, which made better flowcharts, but made it harder to rearrange.
We didn't keep proper version control because we hadn't realised how many changes would be made.