Games GDD

 Reading Task Week 06-

Pepe reading
Link- https://tenor.com/view/pepega-reading-book-studying-pepe-the-frog-gif-17817293 

This week in our reading task we learned about the creation an overall existence of GDD's (Game Development Documents) which is something I didn't know existed before today. Game Development Documents are effectively Bibles in which people who are making a game pool all their research and studies into making a game during game development so that they can come back and see what their thoughts behind process's where in the future. This isn't just for idea's or a lax version of a game journal however, everything needs to be detailed down to the ground, the simple jump most games share as a unanimous move can be nearly 2 pages in this document. The GDD details the games contents as follows:

• Game Design Overview
• Detailed Design Doc 
• Story Overview 
• Technical Design Doc 
• Pipeline Overview 
• System Limitations
• Art Bible
• Concept Art Overview
• Game Budget 
• Project Schedule 
• Story Bible 
• Script 
• Game Tutorial and Manual
• Walkthroughs

All of these headings and sections can potentially be pages upon pages upon pages long, resulting in my want to call GDD's Game Bibles. The pages are not long for the sake of being long however, one of the main points to make for GDD's is they try to take as little space as possible and explain mechanics and the like as clearly and cohesively as possible with the lowest word count possible. Some other tips for GDD's is to know your audience, prioritize the design, illustrate, don't tell others how to do their jobs, know your job, use user stories, separate code from context, invest in a good format, use clear terminology, kill redundancy, capture your reasoning and finally avoid weak language.

There is a lot that goes into creating a GDD and while I haven't looked at the project task this week yet I'm already quite fearful of what I am going to be asked to write now (>0<).