Hello everyone,
So… I have been browsing and studying game development these past few months and I realized that there is one aspect that I felt lost about. I feel that the courses don’t cover it too much, would be nice to have a section about it and perhaps it might even deserve a course for this matter alone: Game Development Document (GDD).
I know that there is a GDD for each game in the beginning of it’s own section, but those are too simple and we get it already done instead of learning how to do our own. I`ve done some researches and it seems that a big amount of time should be spent during the GDD and Concept, before even start coding the game.
Why we should do GDD?
*It will help to know if the game that we are doing is sellable or not;
*It will help us to have a idea of how much time we will spend on the game and if it`s doable;
*It will help us to know which mechanics we should implement first and where to start;
*It will help us to stay focused on our project;
*It will help us avoid spending too much time reworking on a feature or code;
*It will help us know if our current skills are enough or at least almost enough to finish the project;
*It will allow our game to be Cohesive.
*If we want to find partners or collaboratives to our project, it will be very important to make everyone understand what we expect of our game and even discuss some new ideas;
There are plenty of others reasons into why to do a GDD. This course could cover few aspects like:
*Learning how to do the Concept Art;
*Learn how to pick up references and how our game should approach the market;
*Using diagrams;
*Working on the game’s story;
*Organize the game into stages;
and etc…
There are a few pages that describes a few things about GDD and it’s importance:
Wikipedia
How and Why to Write a GDD
I have no experience at this matter, I just felt that this is a very important thing which I’m having a hard time trying to learn and to find more information about.
Let us know what do you think about this.
Best Regards,
Johnny Dalvi