Upcoming webinar

Game Design Documents

Creating a Game Design Document

A Game Design Document – folks in the industry often call it a GDD for short — describes the overall vision for a game

In the professional game industry, GDD’s guide all of the people who work together to make a game – the artists, the programmers, the level designers, the sound designers, etc. – so that they all can understand and work towards the game designer’s unique vision for the game.

Whether you plan to make a playable game or not, it's a good idea to start with thinking about your game's design and documenting it in a GDD.

Written Game Design Document Tracks

For Code Games, we've created seperate tracks for written game designs and playable games. If you don't have access to technology or tools to make a game, creating and submitting a written design might be a good option for you.

But if you're thinking about submitting a written design because you've never made a game or coded before: don't be intimidated! Many of the game-making tools listed on the site are specifically designed to introduce game-making and programming to inexperienced game makers. If you’ve never made a digital game or programmed before, now is a great time to try!

Anatomy of a Game Design Document

Not everyone in the game industry agrees on what should be included in a game design document or what order different topics should be covered in. But we think that the best game design documents address the target audience, the platform, the genre, the core gameplay, the visual style and characters and storyline. Each of these components is described in more detail below.

Overall Vision for the Game

This section should provide a short summary or description of the game. Imagine you are ‘pitching’ the game to a friend while riding on an elevator. How would you describe the game in one minute or less? Why would they want to play it? What makes it sound fun and engaging?

Target Audience

Great game designers always design their games with a specific audience in mind, and this section should describe that audience. For example, are you designing your game for young kids, older kids, or adults? Boys, girls, or both? Is the game designed for hard-core players who like deep, highly challenging games or casual players who like to play a little bit each day?

Platform

Is the game designed to be played on a game console? A mobile device? The web? A good game design targets a specific platform and uses the capabilities of that platform to its advantage. Doing a 3D first person action game in a web browser is hard (but not impossible!), and you can’t count on your players having access to a joystick if they’re going to be playing on a smartphone.

Genre

This section should describe the genre of the game. Popular genres include action, adventure, sports, strategy, puzzle, racing, platformer, and role-playing. Is the game a mix of genres (e.g. action-adventure or a clever combination that’s never been tried before)? Or maybe you have created an entirely new genre!

Core Gameplay

This section should describe in detail what playing the game is like. Most game design documents will do this by talking about some or all of the following things:

  • Core Mechanics: What is the player doing in the game? This is often best described through active verbs like running, jumping, racing, counting, puzzle solving, or exploring. Is the game single player or multiplayer? Cooperative or competitive?
  • Goals and Challenges: What is the player trying to accomplish in the game (i.e. what is the ‘win state’)? What does he or she have to do to achieve that goal? What barriers or obstacles exist that make achieving that goal difficult? How can the player fail at achieving the goal(s) (i.e. ‘loss states’)? What kind of feedback does the player get on progress towards the goal? How is the player rewarded when a goal is achieved?
  • Components: What kinds of things are there in the game? For example, enemies, objects in the environment, power-ups, points, etc. What do they look like? What do they do? How can the player interact with them?
  • Controls: How does the player control what happens in the game? What does pushing a certain button on the controller do? Can the player move a block by touching the screen and dragging it?
  • User Experience: When the player starts to play the game, what steps do they follow? What screens will they see? How are levels in the game structured? How does the player move from one part of the game to the next?
Visual Style

This section should describe the look and feel of the game. Where does the game take place: In the real world? A fantasy world? Space? Underground? In the past? In the future? Is the game a 2D world? A 3D World? What does the art look and feel like: Is it gritty and realistic, beautiful and fantastical or something else? Many GDD’s include drawings or graphics to illustrate the visual concept, and it's probably a good idea to include some in yours.

Characters and Story

Not every game includes a fictional world, characters or story. But if your game does, this section should provide a short summary of them. Where is the game set? What has happened in this fictional world before the game started? Who is the main characters? What is the game's plot?

Sample Game Design Documents

Here are a few design documents created by game industry pros for reference:

2020 Code Games Challenge Are you between the ages of 10-18 and interested in making video games? Enter the 2020 Code Games Challenge and access resources, like information on creating a written game design document. /images/CodeGamesOGDefaultImage_3.jpg