Staying on track when making a new game is a job in itself, so game developers create a Game Design Document (or a GDD) to record their vision for the project.
Compiling one is an artform, yet it’s an essential practice for anyone who considers themselves a professional game dev.
So what goes in it? What if your vision changes as the work gets going? And how do you get started in putting one together?
Why you need a GDD
If you or someone on your team is unsure about whether a gameplay mechanic, a new character or a music track is right for the game, they refer to the GDD. But this is a living document that grows as the game does, so it shouldn’t be considered a list of commandments carved into stone tablets.
It’s fluid, but more importantly, it’s always up-to-date.
In this feature we’re taking a look at what you need to create a game design document from scratch, the best ways to maintain it, and what you should put in it. We'll cover some of the most useful tools for a GDD scribe, ways in which a team can collaborate on the creation of a single GDD, and the resources that are available should you hit a wall.
As always, we want to hear your thoughts and advice on working with a GDD, so remember to send us links to relevant info and to put your hints and tips in the comments section at the bottom of the page.
Click here to view the list »