Games GDD




What is the purpose of GDD?

A Game Design Document (GDD) is a blueprint for the design and development of a game.

The GDD is a way of being creative and documenting the approach to the development of the game. Gonzale (1999) states that “ the important thing is to have something that describes your game project (or any other project for that matter) before jumping into production.( Gamasutra ) It should help to plan out your game. Though it is recommended that the GDD should be short it needs to be detailed enough so as game developers and artists can coordinate the development of the game independently whilst still keeping to the design. 

The GDD is a blueprint for how the game is going to be designed and built, similar to a mind map. In conclusion, the game design document is vital to making a game and it is important to have in order to describe your game project.

How do we create one?

There are a variety of tools that could be used to create a GDD. These include word processing tools, visual tools like Powerpoint, or new web-based tools such as DunDoc. Each of these tools has their advantages and are a personal choice. Many of the examples shared via the internet are in Microsoft Word format. Romero Games(creators of Doom) favour a more visual tool such as PowerPoint. Whichever tool is used they should support the development of the game in an open and transparent manner.


What to include?

The GDD should be simple enough to read through details about your game design and concept. Schubert (2007), who was at the time lead designer for Bioware Austin, gave a GDC talk in about how to create design documentation, some of the most relevant elements include:

  • Know your target.- Have a clear vision and understanding of what you want to make. Make sure your game is suitable and fits your target audience.
  • Keep it short.  Keep it to the point and clear, the shorter they are, the easier it is to read, write, and maintain.
  • Prioritise the design.  - Divide your game in order of importance e.g have a functional game. Concentrate on core mechanics and visuals, and then expand 
  • Illustrate. - Draw sketches of your plans that make it easier to structure and implement. Present what your game would look like as it’s important to have a clear idea of the visuals before you begin creating.
  • Use user stories.- Describing the game through the player’s vision (Similar to what we did in the game vision statement).
  • Take into account the games users, their ideas may help develop future storylines or ideas.
  • Invest in a good format. Take the time to structure your work so that it is easy to navigate.
  • Use clear terminology. Don’t over-complicate the document. Make sure language is concise and accessible.
  • Kill redundancy.  -Recycle your code - use variables, not hard code). Always reference the new section on your page to have a clean document. Avoid copy and pasting sections.
  • Capture your reasoning - why did you make the choices you made? What led to that thought process?


References

Nachen, Lennart. 2014 Communication and Game Design Documents accessed 02/11/2020 http://acagamic.com/game-design-course/communication-and-game-design-documents/


Ferns, Shaun (2020) Readings Week 06 accessed 02/11/2020 https://cdmonline.ie/multidev1/reading-week-06/ 

 Gonzalez Leandro. 2016 How to Write a Game Design Document accessed 02/11/2020 

https://www.gamasutra.com/blogs/LeandroGonzalez/20160726/277928/How_to_Write_a_Game_Design_Document.php

Comments

Post a Comment

Popular posts from this blog

Game Idea Research

Image
Taken via Google Images (Click for link)  The game I am choosing to create for the remainder of this project is going to be a FPS style shooter. Now, right off the bat that seems complex and, in all honesty I am a little sceptical about the workload that may be involved but after doing quite a lot of research I definitely think it is manageable. I don't plan on creating anything too spectacular my main goal is to have the basic mechanics of the game to work properly along with some basic graphics. If in time I'm capable of creating more detailed graphics and find the time and resources to do so, I most definitely will but the priority is for my game to run as intended. I will begin with the sheer minimum. an open plane, untextured perhaps with some 3D objects to add some atmosphere and to create placeholders for future development. ideally I would like the game to run as a quick response, precision shooter which while having fun and exciting aspects to the game, can be used to
Read more

Introduction Of A Future Superstar

Image
  Hi! I'm Matthew, An up and coming superstar. Mark my words! I've just turned 22 and am currently in my second year of college studying Creative Digital Media at TU Dublin Blanchardstown. School was never really for me. When I was young I was a "bad kid" constantly getting in trouble and never listening or participating. Primary school I enjoyed while I was young but once secondary came along I absolutely hated it. I would dread going into school in the morning, constantly trying to pursued my mom not to send me in. I missed countless days during school as I just felt I was never learning anything as I could not find interest in anything. I would sit there drawing or try to listen to music from my phone. I'd do this by putting an earphone through my sleeve, holding it in my hand and leaning my head on my hand. Anything to occupy me until I could go home. I fell behind so much to the point where there was no catching up. I just simply did not want to be there and
Read more

Unity Tutorial 02

Image
  Upon completion of this beginner tutorial I felt very achieved. Although most of the work was done and was following a step by step guide. It's very rewarding to start a project and have it operating properly by the time you finish. I thought I would run into a lot of problems along the way but the software was really quite straight forward.    Coding came easy enough, I did however get an error when attempting to go into G ameview as I forgot to add the ";" at the end of my code. Looking back over my lines of code I was able to locate the problem, mainly because of how many times I've made this same mistake in Brackets while developing websites so the problem was quite noticeable to me. It's great to see similarities like that between modules that I'm doing currently. Web development I'm sure will fit in nicely to future coding that I will need to do I'm sure.    I do feel I will forget a lot of the code in the future, I think that will be my main
Read more