Skip to content

Game Design Laws ​

Laws are short rules that hold unless there is a very good reason to break one. The generic set lives in the standards, in eight parts by theme, and this standard is its index. A game's own laws and overrides stand in the game's docs.

Why ​

Design builds on what is settled, and an agent decides the small things on its own.

The Set ​

Experience ​

The full text is in Game Design Laws: Experience.

  • Never Wait - the player never waits unless continuing is technically impossible. Unavoidable waiting entertains
  • Always Something To Do - a pull short term, a dot on the horizon long term
  • Exploration Is Rewarded - looking around always finds something
  • Full Control - nothing is decided or happens without the player
  • Respect - no dumb tutorials
  • Speedrun Ready - a returning speedrunner has as good an experience as a first-time player
  • Once Per Save - a story cutscene and a progression minigame play once per save
  • AFK Safe - away without negative effect. Nothing is lost, and only what the player set running keeps running
  • Easy Pause - pausing is always easy
  • Soft Sound - a soft mix, varied repeats, a layer per scene
  • Fun First - player experience is priority one. A good game clips well
  • Loop First - the core loop is fun in a greybox, before anything is built on it

Progress ​

The full text is in Game Design Laws: Progress.

Quality ​

The full text is in Game Design Laws: Quality.

UI ​

The full text is in Game Design Laws: UI.

Story ​

The full text is in Game Design Laws: Story.

  • Show, Don't Tell - the player experiences it. Words short and never too spot on
  • Worth Reading - for dialog: a missed line stays missed
  • Dialog Gives Context - dialog accompanies the screen as narrative and gives context, never instructions
  • Make Yourself - for a player character: the player can represent themselves

Guidance ​

The full text is in Game Design Laws: Guidance.

World ​

The full text is in Game Design Laws: World.

  • Fair Surprise - the world has rules the player finds by playing. A surprise answers the player, warns once and is readable after
  • The World Reacts - an action leaves a trace that can be seen
  • Friction In The World - friction is something the player does there, never a menu or a wait

Own Style ​

The full text is in Game Design Laws: Own Style.

How To Apply ​

  • The player is a human who walks the dog, answers the door, goes to sleep and continues the next day. Laws about that human, such as Easy Pause, Never Wait and AFK Safe, translate into any genre. Only their concrete shape changes.
  • A game's laws doc has three parts: the generic laws it adopts, the ones it leaves out with a reason, and its own laws and overrides in full.
  • An adopted or left-out law is named by its name in this set, never copied.
  • A law for one kind of game says so in its name or in a Relevant for: line, and is adopted or left out by it.
  • An exception is a paragraph under the law in the game's overrides, naming the feature and the reason, added only when the director affirms it.
  • Check a new feature against the laws before its spec. A conflict is surfaced, never averaged.
  • Feature docs link the law they lean on instead of repeating it.
  • A new law goes in the game's docs, in the director's wording. One that holds for every game is filed with coentrify, its game specifics stripped (File A Change With Coentrify).