Role workflow
Mainloop for Level Designers: connect levels to the GDD
Mainloop helps level designers document intent, areas, levels, blockouts, puzzles, and pacing without separating playable spaces from the broader design.
Design levels with MainloopDay to day
What improves day to day
Level design loses clarity when layout lives separately from mechanics, pacing, and progression. Mainloop helps each level keep visible intent and a direct relationship with the GDD.
- What the player should learn or feel
- Mechanics present in the space
- Areas, routes, rest, tension, and reward
- Blockouts before final art
Daily board
Daily workflow inside Mainloop
- 01
Start from intent
Before layout, define the level's function inside the experience.
- 02
Connect mechanics and space
Each route, encounter, or puzzle should rely on game rules.
- 03
Bring the level into structure
Use Areas, Levels, and Blockouts to organize zones, pacing, route, and spatial readability.
- 04
Review progression
The level needs to fit difficulty, resources, systems, and GDD goals.
Frequently asked questions
Does Mainloop replace blockout tools?
No. It documents intent, structure, and decisions. Spatial tools still handle the technical role.
How does it help with puzzles?
It helps organize rules, sequences, dependencies, and player readability inside the same GDD.
Why avoid separating levels from the GDD?
It avoids levels that look good but do not teach mechanics, scale difficulty, or support systems.
Design levels with visible intent
Use Mainloop to connect layout, pacing, puzzles, and progression with GDD decisions.
Design levels with Mainloop