Really.... this is getting out of hand.

A design document can really be anything a gamer wants it to be.

The more detailed the better, to be sure, but unless you plan to submit the idea to a publisher who will pay your way through production, you don't need to follow the exacting specifications commonly accepted as a 'true' design document.

If you know what you want to do, then the design document can be written as simply or as complicated as you wish.

It's YOUR game, do it however you want, and in a way that helps YOU.

So noone knows the full details of the game? Who cares? They'll know when it's finished, won't they?

Write your ideas down as you think of them so you don't forget them over time. That's all you really need to do.

But since noone here is offering to pay your way, you don't have to prove anything to anyone. Make it in a way that helps YOU.

Let the rest waste time argueing over who can make the best design document. You go make a game while they squabble over who has the most testosterone to vent in the forums.

With or without a design document, at least you'll have something to show when all is said and done.

You also are free to agree or disagree with any critiques, but don't waste time arguing about it. The finished product will speak for itself, good or bad.

- Jason