Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


How do you format your game design document?


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
17 replies to this topic

#1 Tutorial Doctor   Members   -  Reputation: 1692

Like
5Likes
Like

Posted 16 June 2014 - 08:43 AM

I found a really nice example of a game design document:
http://marceltau.com/files/Arcana_Project_GDD.pdf

Is this somewhat the format used in professional studios in the industry?
Anyone have their own format that works better for them?

I am getting ready to work on my first game for a contest, and I want to get everything more organized, so I could use any input.

Thanks.

They call me the Tutorial Doctor.


Sponsor:

#2 Orymus3   Crossbones+   -  Reputation: 10675

Like
5Likes
Like

Posted 17 June 2014 - 09:26 AM

For a beginner, it is good to follow a template, because it makes sure you build something coherent that encompasses the information it needs to.

However, do not hesitate to break this template apart. Games are not built into generic templates, rather, the so-called template varies based on the project (because every project is different).

 

I would approach this document with a grain of salt. Read it, try to find all of the info that is given. You should have the same kind of information present in your original GDD.

Do not hesitate to add-in wireframes and flowcharts.

This document seems to do a poor job of putting all wireframes together and discussing the specifics later. If possible, break it down by interface.

 

Also, it seems the styleguide is included in the GDD. This is one way to take a stab at it, but it makes for long documentation. If possible, I would advise to break the styleguide apart (art styles, etc.) and keep everything art-agnostic as much as possible.

 

I'm not sure why there is actual code in the design doc, that may also be unecessary. The TDD (Technical Design Document) should be produced by developers once the GDD has been dissected by the production team, not before, and certainly not by a designer.

 

Same holds true for estimates (time to make a character, etc.). The GDD should only contain gameplay elements, interfaces, etc. Not try to be an "everything bible". This leads to confusion.



#3 GoCatGo   GDNet+   -  Reputation: 1637

Like
4Likes
Like

Posted 17 June 2014 - 03:03 PM

As a lone developer I like to play fast-and-loose with GDDs.  Since they are usually for my eyes only, I tend to include sketches, graph-paper layouts, and flow chart/design pattern illustrations a la Machinations (http://www.jorisdormans.nl/machinations/) for the specific game mechanisms.  I've been know to staple index cards to pages and include photos of paper prototypes, generally all jammed into a folder.

 

The real key here is that the user ("reader") of the GDD is me, so it only needs what I want in it.  If you are making a GDD to be used by a team, for potential publishers, or for artists/programmers/whoever, you'll need to tailor it for those readers.  Know your audience!

 

Before I sound too careless, I really believe good planning leads to good design.  The GDD is vital, but the format is not.


Indie games are what indie movies were in the early 90s -- half-baked, poorly executed wastes of time that will quickly fall out of fashion.  Now go make Minecraft with wizards and watch the dozen or so remakes of Reservior Dogs.


#4 Tutorial Doctor   Members   -  Reputation: 1692

Like
0Likes
Like

Posted 17 June 2014 - 09:00 PM

I was looking at the GDDs as being a sort of record or formal documentation of the process of making a game for future reference.

But I guess they can be used as a simple guideline as well. Thanks for the tips.

They call me the Tutorial Doctor.


#5 GoCatGo   GDNet+   -  Reputation: 1637

Like
4Likes
Like

Posted 18 June 2014 - 07:10 PM

Ah, OK... I think I misunderstood.  I also keep a design notebook that accompanies my GDD.  In it I record what I work on by the day, problems I run into, solutions I may (or may not) find, and a written record of my thought process.  Maybe that is what you are thinking about?  Something that you can easily organize into a post-mortem when you have a finished product?

 

I go to B&N and buy up all the lined journals they have in the bargain bin.  Each game/design gets its own journal.  Also the act of writing on paper with a pen -- not at a computer -- lets me concentrate more on the task at hand.

 

Hope that helps!


Indie games are what indie movies were in the early 90s -- half-baked, poorly executed wastes of time that will quickly fall out of fashion.  Now go make Minecraft with wizards and watch the dozen or so remakes of Reservior Dogs.


#6 Orymus3   Crossbones+   -  Reputation: 10675

Like
1Likes
Like

Posted 19 June 2014 - 06:02 AM


Ah, OK... I think I misunderstood.  I also keep a design notebook that accompanies my GDD. 

 

I did that once :)

Turns out there was no post-mortem at the end of the project, so I was glad I had my own notes. Definitely recommend it, if you can make time for it.



#7 GoCatGo   GDNet+   -  Reputation: 1637

Like
0Likes
Like

Posted 19 June 2014 - 09:05 AM


Turns out there was no post-mortem at the end of the project, so I was glad I had my own notes. Definitely recommend it, if you can make time for it.

 

 

I really try to make time for non-coding/technical work in my design.  10 hours of unfocused work in Unity barely equals what I can map out with my design journal in 30 minutes.  If I get working with the tools before I have a plan I end up just playing with tools and accomplishing little.  I have made some fantastic looking environmental scenes, though.  I'm the Bob Ross of Unity.


Indie games are what indie movies were in the early 90s -- half-baked, poorly executed wastes of time that will quickly fall out of fashion.  Now go make Minecraft with wizards and watch the dozen or so remakes of Reservior Dogs.


#8 Tutorial Doctor   Members   -  Reputation: 1692

Like
3Likes
Like

Posted 04 July 2014 - 12:46 PM

Stumbled across a video on design document making when looking for a markdown tutorial.

http://m.youtube.com/watch?v=_ODFl4GUy8I

They call me the Tutorial Doctor.


#9 Orymus3   Crossbones+   -  Reputation: 10675

Like
1Likes
Like

Posted 04 July 2014 - 07:02 PM


I really try to make time for non-coding/technical work in my design.  10 hours of unfocused work in Unity barely equals what I can map out with my design journal in 30 minutes. 

 

I generally do that on my android phone when I'm not in a spot where I can work on my projects. Can't afford to waste that precious spare time on my computer... wait... what AM I doing RIGHT NOW? :P



#10 GoCatGo   GDNet+   -  Reputation: 1637

Like
1Likes
Like

Posted 05 July 2014 - 07:52 AM


Can't afford to waste that precious spare time on my computer... wait... what AM I doing RIGHT NOW? tongue.png

 

Me, too! wacko.png

 

I've been getting more serious with using Articy: Draft 2.  I've got to say that now that I've pinned down the way it works, I've been able to use it for everything from broad design to mapping out dialog trees.  I don't think it is for everyone, but it sure hits some sweet spots.


Indie games are what indie movies were in the early 90s -- half-baked, poorly executed wastes of time that will quickly fall out of fashion.  Now go make Minecraft with wizards and watch the dozen or so remakes of Reservior Dogs.


#11 Tutorial Doctor   Members   -  Reputation: 1692

Like
1Likes
Like

Posted 05 July 2014 - 11:30 AM

I am working on a template for constructing my Game Design Document with Editorial.

 

I have a few Workflows already, that will help make it easier (search "Doctor").

 

For anyone that has an iPad, I think this is a good way to create any sort of document. I can even convert it to LaTex if I wanted. 


They call me the Tutorial Doctor.


#12 Acharis   Crossbones+   -  Reputation: 4002

Like
2Likes
Like

Posted 06 July 2014 - 12:10 PM

I found a really nice example of a game design document:
http://marceltau.com/files/Arcana_Project_GDD.pdf

It's a nice document, as a programmer I would love to work having something like this.

 

But I have some issues:

1) Such level of detail in GDD guarantees there won't be anything unique or original in such game, it will be bland and overused. I mean, if you go fo original it MUST be messy and you can't plan everything, it has to be discovered not written down upfront.

2) They ignored prototype, they didn't have any plans to redesign the game based on the feedback they get from testers/players after releasing the prototype (which frequently results in a mediocre game).

3) This GDD completely lacks the promotional texts. That's the first thing I write down, how I will advertise the game, and then I tend to REDESIGN the game to fit this fun description. It's extremelly crucial and it will benefit the game.

4) That game is pretty simple, and honestly, you don't need any GDD to write something like this in the first place :) They could have just written down "let's make a game like XXX except [put a feature here]", yet again, it has some uses. If you go for unoriginal mass produced casual games that GDD is perfect to send to your programmers, they will love you for it :)


Europe1300.eu - Historical Realistic Medieval Sim (RELEASED!)

PocketSpaceEmpire - turn based 4X with no micromanagement FB


#13 Tutorial Doctor   Members   -  Reputation: 1692

Like
0Likes
Like

Posted 06 July 2014 - 01:15 PM

I'd use it more as a starter template, and derive my own template from it (which is what I am going to do).

The video I linked to actually encourages not being too detailed in your GDD.

I totally get what you mean with your first point. Having strict guidelines takes away the free-form nature of creative design. When I draw, I don't make guidelines and markers for the location of every part of the drawing, neither can I use those same guidlines for a completely different drawing.

I'd feel restricted.

They call me the Tutorial Doctor.


#14 Tutorial Doctor   Members   -  Reputation: 1692

Like
0Likes
Like

Posted 06 July 2014 - 01:35 PM

I have a couple of questions also for anyone that could provide some input:

With Editorial (as it stands) I am able to:

* Type a document using Markdown
* Insert images into the document using Markdown links
* Use HTML and CSS to lay out and style the Markdown document
* Convert the Markdown document to PDF, LaTex, DOCX, HTML
* Insert Links to Youtube Videos via Markdown Links
* Use Python and a new UI module to actually create an in-app app
* Use a provisioning profile that uses a URL scheme to launch that in-app app from an icon on the homescreen (just made it today)
* Make a sort of private GDD wiki using Markdown links
* make regular expressions to quickly find/edit text in the GDD.
* Automate all of the above

So in summary:
I could amlost make a private GDD automator (template at least)

The thing is:
There is a lot that goes into a game as the sample GDD I posted displays.
And it is a lot to manage.

Question:
1) What would be your ideal needs for such a program?
2) How would you have it operate
3) What export formats would you need?

Text-wise and image-wise I could do the attached pretty quickly:

Attached Thumbnails

  • image.jpg

They call me the Tutorial Doctor.


#15 Acharis   Crossbones+   -  Reputation: 4002

Like
0Likes
Like

Posted 06 July 2014 - 02:34 PM



So in summary:
I could amlost make a private GDD automator (template at least)
It's your first game. Forget about all this, it does not matter, it's irrelevant, it only distracts you, it will make you fail. Make a clone of some game you like (and maybe improve it, but only after you got the core gameplay working). Believe me, with your first game it will be hard enough without all this originality thing. You are not at the level to worry about "GDD automator" (whatever it means :)), worry about simplier, much simplier things. Save all this for your second game.

Europe1300.eu - Historical Realistic Medieval Sim (RELEASED!)

PocketSpaceEmpire - turn based 4X with no micromanagement FB


#16 Tutorial Doctor   Members   -  Reputation: 1692

Like
0Likes
Like

Posted 06 July 2014 - 03:06 PM

Hehe. I know it isn't that neccesary, but I need to get more organized, because I dont have any structure to my workflow. So, I haven't gotten much done anyhow.

I have however, just finished up the beginning of a simple

Game Design Document Automator:
http://www.editorial-workflows.com/workflow/5549020571238400/_Ay8twW29QM

Right now it helps me to quickly create headers and content for my document, as well as insert images into it.

This is all I need right now, but I could use more input on how I could develop it further for future (perhaps more advanced) games.

They call me the Tutorial Doctor.


#17 ShadowFlar3   Members   -  Reputation: 1258

Like
1Likes
Like

Posted 07 July 2014 - 04:49 AM

A GDD for a someone who is working alone is really just a place to work on the project and organize your tasks for when you can't dedicate to the tasks themselves. I don't see one format of GDD suiting everyone.

 

Think of all the assets you're going to need and where to get them. What challenges or dilemmas could you face when you're creating your AI, pathfinding or inventory for example. I believe every game developer asks themselves these questions sooner or later. Hard things can prove quite easy when you lift it on the table and start writing things down. Or vice versa. A GDD is nevertheless a place where you can start answering your questions and regard yourself better prepared than prior to writing it :)

 

In team projects it has more important job of communicating between members, things have much more strict schedule and priority order so that every member can progress fluently and purposefully within their field without having to wait other assets that haven't been finished or designed yet. In commercial projects it also links to the bureaucracy and budget: how the spent and spare resources are in balance compared to the budget and schedule.

 

Also a pointer about the detail level: it doesn't matter but don't plan too much ahead. There's no use designing every number and feature in detail before you've done rudimentary playtesting to see if the concept will fly at all. Expand on "width" axis meaning it's better to design 7 enemies on crude level (and scrap 3 of them later if they don't work out at all) than trying to polish 2 enemies in detail before you have anything playable.

 

TL; DR: It's for you, make it as it suits you, but understand what it's for :)



#18 Tutorial Doctor   Members   -  Reputation: 1692

Like
0Likes
Like

Posted 11 July 2014 - 10:57 AM

It took a bit of frustration, but I created another extension to Editorial that automatically converts my GDD into a checklist (Taskpaper style). (Mark To Task)

That's all I need for now. I'll refer to this post for ideas when I need to. Thanks.

Attached Thumbnails

  • image.jpg

They call me the Tutorial Doctor.





Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS