Sign in to follow this  

Thinking up 'sections' for your documentation?

This topic is 3626 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I recently started a documentation to keep track of what I need to program into my game. However, I have a hard time coming up with sections. I found that "game design templates" posted around the web are way too generic, and not personalized for my semi-unique game genre. So I ask you, oh great game designers.... what helps you come up with the Table of Contents for your documents? Thank you.

Share this post


Link to post
Share on other sites
Ask yourself what you see in most of the games in your genre and then ask yourself what you want.

I personally make all of the content in no particular order and then organize and add what I need into it.

Share this post


Link to post
Share on other sites
The TOCs of my GDDs vary depending on the content of my game.
Trying to come up with a universal list of "sections" for a GDD is just trying to put a patch on the problem you already identified - that generic GDD templates cannot work for every conceivable game.

Share this post


Link to post
Share on other sites
Im definately not a professional on this, but my opinion would be to break the design document up into the various portions of your game.

Take an FF sytle RPG

You have the world map, battle system, leveling system, etc. Each of those can be further broken down. Using each section of the game, you can then use those as your Design Doc sections.

My 2 cents

Share this post


Link to post
Share on other sites
Quote:
Original post by Cgr
I recently started a documentation to keep track of what I need to program into my game. However, I have a hard time coming up with sections. I found that "game design templates" posted around the web are way too generic, and not personalized for my semi-unique game genre.


Identify why a generic one doesn't fit, and think about where you would put that extra information.

But really, focus on communication. Things should fall into natural groupings. Your game can be divided up several ways - different aspects of the tech required, different types of in-game entities, setting/story/characterisation, input and output methods, game modes, etc. If you're confident that you know enough about your game to know that a standard doc won't work, just write your stuff down and organise it as you go along. Headings follow content rather than the other way around.

Share this post


Link to post
Share on other sites

This topic is 3626 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this