Games GDD

So this week for reading week 06 I got to learn all about "Game Design Documents". This is used when game developers want to keep an accurate log of the games progress to show how exactly certain parts of the game are taking affect. It is also used when you are trying to show your game plan/idea to investors or even a development team so they can get a broken down and well categorized read of the games contents.

Its quite common for Game Design Documents to have some main headings such as Story Overview, Visual's Overview, Game play Mechanics Overview just to name a few, there can be hundreds of headings depending on how diverse and big the game is.

When I took a look at some layouts for GDD's and some game studios have shown for their games, its quite clear to see what its a very straight to the point document. It states the info needed and is well detailed, but at the same time its quite short and you don't find your self just glancing over pages of what can seem like useless information.

The video attached to this weeks reading week was a really nice break down of how GDD's work, especially since its coming from someone that is going to be using one for their rpg game.

Personally I feel like a GDD is a great system to have in place, it can keep you on track with the development of a game without you having to keep it all in your head. As said in the video, you can sometimes find your self trapped in a corner not knowing what to do next, and a GDD is a great way to get you out of this trap. You can go back through your document and find what is due next or even remind your self what the purpose of the game is in case you find your self getting side tracked with development.

I am definitely going to use a GDD for my game development as like many other devs, it will help to keep me on target to produce the final product in the end.

Game Design Document Graphic

Link: https://www.gamedeveloper.com/design/four-reasons-you-need-a-game-design-document