Skip to main content

Games GDD

GDD gif


What is GDD for?


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. Gonzales (2016) 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 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 make one?

There are a variety of tools that could be used t create a GDD. These include word processing tools, visual tools like PowerPoint, or new web-based tools such as DubDoc. Each of these tools has its advantages and is a personal choice. Many of the examples shared via the internet are in Microsoft Word format. Romero Games (creators of Doom) favor 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 should be in it?

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 of Bioware Austin, gave a GDC talk about how to create design documentation, some of the most relevant elements include:

  1. 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.
  2. Keep it short - Keep it to the point and clear, the short they are, the easier it is to read, write, and maintain.
  3. Prioritize the design - Divide your game in order of importance e.e. have a functional game. Concentrate on core mechanics and visuals, and then expand.
  4. Illustrate - Draw sketches of your planes that make it easier t 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.
  5. 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 game user's, their ideas may help develop future storylines or ideas.
  6. Invest in a good format - Take the time t structure your work so that it is easy to navigate.
  7. Use clear terminology - Don't over complicate the document. Make sure language is concise and accessible.
  8. 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.
  9. Capture your reasoning - Why did you make the choices you made? What led you to that thought process?


References:
Labels:

Comments

Post a Comment

Popular posts from this blog

Introduction to a future Animator 😁

If you've been reading my blog post since the day I started, you have read my first introduction. However, I haven't really talked about myself. So in this post, I will along with questions from the tasks we have given. 😁 My photo from last year First of all my name is Flosie Jane Sazon, I am currently a 2nd-year student studying Creative Digital Media at the  Technological University of Dublin located in Blanchardstown Campus. I'm 20 years old (even though I don't look my age 😂) and I have been living in Ireland since I was 13. This course wasn't actually my first choice even though I love art. My first choice was something about business and language which was way different from what I'm doing now, but I'm really happy that I'm doing what I love. Even though there were a lot of times convincing my parents but everything went well in the end.😂😂 What was the best class you took last semester? why? Even though I enjoyed Web Development and Design Proc...
14 comments
Read more

Unity Tutorial 04

This week's tutorial lesson was very straightforward and easy to follow. I also did not have any problem with the Unity tutorial videos and the software this time which I am really glad about. I learned how to apply codes that can destroy the objects when the collision is detected. I also know how to add the "Game Over" message in coding if the farmer missed feeding one of the animals. The tutorial lesson also taught us how to spawn the animals at timed intervals so that the animals will appear randomly on the game. Here are the things that I learned for this week's Unity tutorial: Lesson 2.4 New functionality: Animals are spawned on timed interval and walk down on the screen and the animal gets past the player without getting fed, there's a "Game Over" trigger massage at the left bottom of the screen. When the projectile and animal collide, objects are removed right away. New Concepts/Skills: Create custom methods/functions InvokeRepeating() to repeat c...
Post a Comment
Read more

Time Strategies

Ancient clock As usual, I have been trying to start my last blog for this week, but because I procrastinate so much I never ended up doing it.  I feel like I always keep saying (I'll do it tomorrow morning), knowing very well that I am actually not a morning person!😂 . Anyways.... I am doing it again, moving away from the main topic. *facepalm* Today I will be talking about the time management which is ironic for me as I have been procrastinating before doing this blog. We were given multiple articles to choose from and read at least 2 of them to help us manage our time and keep our head on track with college work. Even though it is only the 2nd week of semester, we already have plenty of things to do, whether it is a tasks or labs. I've already found myself overthinking and feeling pressured to be able to submit the work on time. I also find it hard to stick to my planned timetable for this specific module that I created last week because there are tasks that kept coming. The...
Post a Comment
Read more