Documentation guide

Level documentation connected to the game design

A useful LDD explains what a level should achieve, how it is navigated, which mechanics it uses, and how it connects to the GDD. It is not a decorative map description.

Create level documentation

What an LDD is for

A Level Design Document documents a level, area, or playable space. It connects intent, layout, mechanics, pacing, difficulty, risks, and progression before expensive art or implementation work.

Useful LDD structure

  • Level objective
  • Emotional or functional intent
  • Mechanics taught or tested
  • Relevant rules and risks
  • Initial layout and blockout
  • Main and alternative routes
  • Points of interest, tension, and rest
  • Rewards, progression, and relationship with the GDD

Practical use

How to complete it without making it heavy

The LDD works better when it is not isolated. Mainloop connects spatial documentation with mechanics, systems, and broader GDD decisions.

  1. 01

    Define intent before layout

    The level needs a reason to exist: teach, challenge, reveal, combine, or validate part of the design.

  2. 02

    Connect space and mechanics

    Each route, obstacle, or encounter should rely on real game rules.

  3. 03

    Separate zones and pacing

    Document entry, tension, rest, reward, detours, and key moments without writing an endless map.

  4. 04

    Use blockouts as early language

    The blockout clarifies pathing and spatial readability before final art detail.

  5. 05

    Validate against the GDD

    If the level does not reinforce mechanics, systems, or progression, it probably needs adjustment.

Criteria for reviewing an LDD

  • The level objective is clear
  • The player understands what to test or learn
  • The layout responds to real mechanics
  • Pacing includes tension and rest
  • Production risks are visible
  • The level does not contradict the GDD

Frequently asked questions

Does an LDD replace the blockout?

No. The LDD explains intent, rules, and structure. The blockout helps validate pathing and spatial readability.

Can I create an LDD before final art?

Yes. It is often more useful before final art because it validates intent, pacing, and mechanics at lower cost.

How does the LDD connect to the GDD?

The LDD takes GDD decisions and brings them into a concrete playable space: objectives, mechanics, progression, and pacing.

Connect levels, blockouts, and the GDD

Use Mainloop to document intent, routes, and progression without separating the level from the rest of the design.

Create level documentation