When creating a video game, several documents are typically used to plan, develop, and manage the project.
These documents serve as guidelines and communication tools to align the development team and stakeholders throughout the game's creation.
It's important to note that the specific documents and their contents may vary depending on the development team, project scope, budget, and game genre.
Here are some commonly used documents in video game development:
- Game Design Document (GDD): This document outlines the overall vision, mechanics, gameplay, story, characters, levels, and other important aspects of the game. It serves as a blueprint for the development team.
- Concept Document: This document focuses on the high-level concept and core ideas of the game. It may include visual references, inspiration, target audience, and unique selling points.
- Technical Design Document (TDD): This document details the technical aspects of the game, including the game engine, programming languages, tools, network architecture, data management, and other technical requirements.
- Art Bible: It contains visual references, art style guidelines, character designs, environment concepts, and other visual assets that define the artistic direction of the game.
- Level Design Document (LDD): This document specifies the layout, objectives, challenges, and narrative elements for each level or area in the game. It provides a detailed plan for level creation.
- Audio Design Document: It outlines the sound effects, music, voice acting, and overall audio direction for the game. It may include references, technical requirements, and guidelines for integrating audio assets.
- Monetization Strategy Document: For games with monetization elements, this document defines the revenue model, pricing, in-app purchases, advertisements, and other monetization strategies.
- Marketing Plan: This document outlines the marketing and promotional strategies for the game, including target audience, branding, social media campaigns, public relations, and distribution channels.
- Project Schedule: It is a timeline or Gantt chart that outlines the tasks, milestones, deadlines, and dependencies for the development team. It helps in project management and tracking progress.
- User Interface (UI) Design Document: This document defines the layout, navigation, controls, menus, HUD elements, and overall user experience of the game's interface.
- Localization Documents: If the game is intended for multiple languages or regions, these documents contain translated text, cultural considerations, and guidelines for adapting the game for different markets.
- Quality Assurance (QA) Test Plan: It outlines the testing strategies, test cases, bug tracking, and quality control procedures to ensure the game functions correctly and meets the desired quality standards.
