Hey all,

I've always wanted to design my own game, and I do have one game on the iStore and Google Play, but unfortunately when I created it, I had no clue what actually went into creating my own game and the game was a complete and utter pile of junk.

I decided to take a step back and really learn what it takes to creating good games. So I went out and purchased Game Development Essentials: An Introduction. Now the book has a lot of information for people who don't know anything about game design and development, but it lacks any real detail about each section of development.

I'm now looking for detailed information on how to write GDD's (Game Design Documents). I've been looking for online game design courses, videos, tutorials whether they be free, or paid. But I've had no luck what-so-ever. If anyone has any suggestions or links to detailed information whether they be courses, videos or tutorials, then please lemme know.

Even if you know any books (whether free or paid) with this information, please lemme know.

Some examples of actual GDDs

http://www.scribd.com/doc/5402045/The-Design-Document-Justin-Kelly

http://www.scribd.com/doc/34994424/Viral-Light-Interactive-GDD

Some general tips

http://www.gamedev.net/page/resources/_/creative/game-design/developing-your-game-concept-by-making-a-design-document-r3004

http://www.sloperama.com/advice/specs.htm

http://www.gamasutra.com/view/feature/3224/creating_a_great_design_document.php

Thanks for the quick reply, I already started reading from the links. :)

My "develop your idea via making a design document" guide for beginning and intermediate designers:

http://www.gamedev.net/page/resources/_/creative/game-design/developing-your-game-concept-by-making-a-design-document-r3004

I just did an example of step 1, the statement of purpose, in my developer journal.

Edit: and just added a journal entry for part 2, fill-in-the-blank game description.

Also, there a vast ocean of youtube videos out there that give you a pretty extensive idea of how to start developing an idea. The short explanation however, is to really just think of any program as a very large set of problemsolving issues. But start simple, and that largeness won't be something you have to worry about.