Game Development Documentation EREN NABİ

 When the team grows, becomes harder to protecting the focal point of the project.  Good documentation is useful in regulating the design of the game and manufacturing process.

 The team members need a reference (a document), to how to format the system running around. And they must work base on this document.  Thus, the design document, art books, technical design document and many more reference like those will lead, for the creation of the game content.

 If you are a publisher or working in a development company, documentation is essential for a professional computer games, (commercially required).  No documentation is possible to make a game, but it will be difficult for big development teams.

Pitch Document, or Proposal  Pitch Documents, documents to sell or impose the idea of a game to executives, or publishers.  How the game will take place in the market, budget and development schedule, which technology to use, brief information about the possible people who work for the game, and include some comments about gameplay.

Pitch Document, or Proposal  This document is not used directly in the design process, it is important to the creation of other documents.

Competitive Analysis  That document is written for how to compete with similar game titles on the market.  It must contains game's unique properties.  Other similar games on the market with the same objectives are listed and analyzed.

Design Document  It has vital importance especially in large team projects, it leads team members of the project.  Well-written a design document, if you change the design team is still of vital importance (in terms of to be able to resume).

Design Document  Design document setting out full gameplay.  It contains game mechanics details (for example, the players what can do or how can do in the game).  It includes a list of objects, different characters and elements the player will interaction.

Design Document  It does not contain game code like as technical design document.

Flowchart There are two important field of use:  Monitor the player how travels out of the game menus. This is a player new to the game or player wants to play a loaded game.  Especially level-based games, when players move in the game they are used to map the fields.

Story Bible  In the design document of the game game's story can be found, but in the story bible a different part of the complex story of the main characters (especially if you have different characters and locations), or reside anywhere in the universe in the story.  background story of the game is processed in this bible.

Script  If you have a story of the game, players may want to hear characters speeches or read the subsequent quest of the game.  If there are the movie-like scenes in the game the game's script and dialogue should focus on these scenes.

Script  Games scenarios are different from film or television scripts because of their non-linearity.

Art Bible  It is not created by designers, it is created by the head of artists and his/her team. It basis of the main concepts and other resources.  Compatible with the game's story and characters.  It goes with the game game engine.

The Game Minute  It written in the form of prose and it is 1-3 page document describing what the player did during the game the and giving specific details about game.

Storyboard  It means; each scene individually hand-drawing of a movie, animation cartoon etc…  It’s providing feedback or correction before submitting offers to some member of the team without any problems.

Technical Design Document  Written by the lead programmer at the beginning of the project and the other programmers used it as a point of reference.  The designer may not understand this entire document but can be sure that the programer team is on the right track.

Schedules and Business/Marketing Documents  Design document is not related to advertising or, how the game is will be retail selling.

No Standard Documentation  Different companies use different documentation standards, in order to help or guide the design of the game.

Benefits of documentation  Good documentation makes your game better (work in a single, or work in a team as well).  Publishers want worthwhile evidence that it is a good idea to wait for actions from game development team therefore documentation is important.

 Thank you..!