design

v0.1 Sections to copy

World design (overall backstory, setting, and theme of the game)

System design (rules and underlying mathematical patterns)

Content design (characters, items, puzzles, and missions)

Game writing (writing of dialogue, text, and story within the game world)

Level design (crafting of levels in a game, like maps and placement of objects and challenges)

UI (how the player interacts with the game, and how the player receives information and feedback from the game)

v0.0 Principles

A “living” document that is continuously undergoing revision, it contains the entire design vision for the game. It may be in a document file or in a wiki. Some teams use Agile development, which requires no design document at all.

Story + MDA (mechanics-dynamics-aesthetics): We create aesthetic models for various types of gameplay. Aesthetics don’t refer to the looks of the game but rather the emotional response we hope to evoke in the players through the game dynamics. If mechanics are the rules and dynamics are the play of the game, then aesthetics are typically the fun experienced by playing. Let's design FUN!

From AgileManifesto.org, we follow these principles:

• Our highest priority is to satisfy the user through early and continuous delivery of valuable software.
• Welcome changing requirements, even late in development. Agile processes harness change for the app's competitive advantage.
• Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
• Business people and developers must work together daily throughout the project.
• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
• The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
• Working software is the primary measure of progress.
• Agile processes promote sustainable development.
• The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
• Continuous attention to technical excellence and good design enhances agility.
• Simplicity--the art of maximizing the amount of work not done--is essential.
• The best architectures, requirements, and designs emerge from self-organizing teams.
• At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.