Communication and Game Design Documents
GDDs are an important part of game design to allow developers to share their vision with a team, it is important to work off of a template although it can be an issue as one template will not suit all or even many games.
GDDs can be used as a memory aid to remind developers of early concept ideas to work into a game.
They are also handy for communicating ideas throughout the design faze.
GDDs are broken down into different parts throughout the development process where developers from different teams will add in their own content.
There is a long list of features which dictate if a design document will be good, such as knowing the games audience, keeping it short but informative, breakdown the features of the game into different sections, illustrations, leave open questions, use views of the players, separate code and content, find a suitable template, use clear language, don't have useless or repeated sections in the document, avoid weak language and give reasons as to why game logic works in such a way.
Have gameplay pillars, meaning have certain aspects of the game that are important and essentially make up the majority of the game.
Break down the game into all of its essential parts to explain in the design document.
How to Write a Game Design Document
From the reading of a GDD it should be clear what type of game is being produced aswell as its genre.
Sections of a GDD
Characters
Story , theme, story progression
Gameplay and Goals
User skills, game mechanics, power ups and items and progression and challenge
Losing conditions
Art style
Music and sound design
Technical Description
Marketing and funding, demographics, platforms and monetization
Localisation
Any remaining ideas
Using a Game Design Document | BenderWaffles Teaches - RPG Maker Tutorial HOW TO #2
List of Screens visible to the player
Gameflow - what order the player travels through the game world
Comments
Post a Comment