Game Design Document Report

Game Design Documents (GDD’s) 

A GDD or Game Design Document, is a tool used by developers to log and note things down about a game's development, concepts and everything about it. It’s essential for game developers as it helps them to group information about the game in one area accessible to all the developers to have all the information needed for their departments without having to ask questions. It helps guide the development progress into an organized form which everyone can access and make changes to. 

A GGD helps define what a game is in multiple aspects, how key mechanics will function, character design, ETC. It assists the people attempting to make a game by giving them a large document of which they are able to put all the resources needed for all departments. It aids in communication by allowing team members instead of having long conversations about certain aspects, instead being able to just give them a page number on the GDD. It attracts investors or publishers as they are easily able to look through the GGD to find important selling points and things they believe to be good. It can be used as a reference point by comparing old versions of it with new versions of it, and how it is improving.

Key Sections in GDD would consist of an overview of the game itself, sections for certain developer types such as Animation Sections and Sound Design sections. A GDD can be organised with a Table Of Contents at the start, listing what page every section is on for ease of access to everyone, and clarity that things will be able to be found with ease. High Level of detail is required in each section of the GDD, needing things to be specific and informative so no additional information needs to be asked. The person reading needs to know what to make without having to bother people about it. A GDD can be adapted in multiple ways, depending on the genre, being able to be made in seperate ways.

A GDD can be used as a living document that is constantly used by all developers by making copies before every edit, pushing new versions of it then logging it near the beginning. The best practices to maintaining the updates to the GDD is to make sure everyone on the team writes about every idea/thing they want in the game. A GDD can be used to measure progress by comparing it to old versions of the GDD and see how they've improved, along with also checking it for possible changed things that they'd want to revert.

 The primary benefit of a GDD would be that everyone is able to help eachother out by constantly updating it, adding new and specific things of which each person on the team can use. However the potential challenges would include things such as forgetting to log updates and things not being specified well enough. These challenges can be addressed by making sure everyone does their part, constantly updating the GDD overtime, along with being able to know exactly what you want, and be able to write that down.

The people who would use a GDD would consist of game developers of all kinds, such as scripters, animations, concept makers, concept artists, sound designers, ETC, all being able to access certain areas of the GDD with specific explanations of the work they need to do, how it needs to be done and why they need to do it.  It would also be used by publishers and such to have the game explained to them and see if they'd want to publish said game. It would also be used by investors who might want to put money into the game if they think it is going to be successful or big in the long run.