Game Phases: Development
The third stage of a game (Game Phases). The designed game is built.
Pre-Alpha
Functionally complete: the full game playable from start to finish, perhaps badly paced, buggy and visually imperfect, with every part there. Gate: is every part there?
- Every part a level needs is present and reads as what it is: its objects, sounds, voices, music or its silence, and the interface it needs.
- A rough part is fine. A missing part is not.
- The right vibe counts.
- Polish waits: the look and the finish of a working part belong to Alpha, and so does its debt, until the game's whole shape stands. An agent pushes back on polish.
- What a part does is good from its first version (Always Polished).
- Content the director has not decided takes the agent's recommendation under Veto (Game Work Workflow), and Alpha polishes it.
- A ticket names the parts it adds in refinement, by kind, so a story shows what it brings: ten sound effects, say.
- Before a level lands, an inventory checks every part its tickets and its feature doc name: each is present and reads as what it is.
- The Launch Strategy is picked before Alpha.
Alpha
Completeness: everything implemented properly everywhere and looking good, its passes done. A pass is an epic of checks and fine-tuning across every level, never new mechanics, so it belongs to Alpha. Gate: is every part right?
Beta
External, controlled playtesters. Gate: do strangers get it and keep playing?