Level design contract (template)
Agents load this file first, every time they build or change a level. Fill in the metrics once the game exists and keep the file in step with the game. Generic on purpose: no theme, no game design. The purpose and relationships of each space come from the task, not from here.
All values are centimeters and Unreal units unless noted. Rows marked DEFAULT come from the UE5 Third Person template (Manny capsule) and are placeholders until the game's own value replaces them.
1. Metrics
| Metric | Value | Status |
|---|---|---|
| Player capsule radius | 34 | DEFAULT (Third Person, Manny) |
| Player capsule half height | 88 (full height 176) | DEFAULT |
| Eye height above floor | about 160 (camera at capsule top minus a little) | DEFAULT, set the real camera height |
| Walk speed | 500 | DEFAULT (template CharacterMovement max walk speed) |
| Run speed | none in the template; set one | TO FILL |
| Jump height | about 120 (JumpZVelocity 700, gravity 980) | DEFAULT, measure in game |
| Jump distance (flat, at full speed) | about 400 to 500 | DEFAULT, measure in game |
| Max step height | 45 | DEFAULT (CharacterMovement) |
| Walkable floor angle | 44.765 degrees | DEFAULT |
| Door width | capsule diameter 68 plus margin; use 120 | RULE, confirm |
| Door height | 230 | RULE, confirm |
| Corridor width | 200 for two-way, 120 minimum one-way | RULE, confirm |
| Stair rise (per step) | 17 | RULE, must be under max step height |
| Stair run (per step) | 28 | RULE |
| Railing height | 100 | RULE |
| Minimum clearance (overhead) | capsule height plus 30, so 206 | RULE |
| Minimum clearance (sideways) | capsule radius plus 20 each side, so 54 | RULE |
| Cover height (crouch) | 100 | RULE, set with the game's crouch height |
| Cover height (standing) | 190 | RULE |
| Third person camera distance | 300 (spring arm) | DEFAULT |
| Third person camera collision probe | 12 | DEFAULT |
| Grid snap | 50 for blockout, 10 for detail | RULE |
Rows marked RULE are common practice values for a human-scale character, not engine defaults. Replace any that the game's design contradicts, and record the change and the date at the bottom.
2. Working rules
- Describe the space by its purpose and its relationships (what connects to what, what the player must see from where). Leave the rest open; propose and then verify.
- Block out from primitives (cubes, planes, cylinders from the engine) at the real metrics above. Do not place final assets until the blockout passes the checklist.
-
After each step, capture and inspect with
prep/scripts/scene_capture.py(top-down, four corners, eye height). Do not use the user's editor viewport. -
Name actors for what they are (
Door_Hall_To_Cellar,Wall_North_01) so gaps and clearances can be queried by name. - Use whole numbers on the grid. Place doors and stairs by their metric, not by eye.
- Save the level after each passing step, one file, small commits.
3. Checklist (run it after every step; record pass or fail with the number)
Clearances
- ☐ Every door is at least the door width by door height, and a capsule overlap test at its center is clear.
- ☐ Every corridor is at least the corridor width along its whole length; check the narrowest point, not the middle.
- ☐ Overhead clearance everywhere the player walks is at least the minimum, including under stairs and beams.
- ☐ Landings at the top and bottom of stairs, and in front of doors, are at least a capsule diameter deep on both sides.
- ☐ Gaps between named actors that should touch are 0 (no slivers, no light leaks); gaps that should leave a path are at least the minimum clearance.
- ☐ Rails are present at every drop above the max step height.
Reachable routes
- ☐ The player can walk from spawn to every required point with no jump over the jump-height limit and no step over the max step height.
- ☐ No dead-end the player can enter but not leave.
- ☐ Every one-way drop leads somewhere that has a way forward.
- ☐ Each route was played, not only inspected: run it in PIE or with a movement test and note the time.
Sightlines
- ☐ From the first position in each space, the next goal or exit is visible, or something draws the eye toward it.
- ☐ Nothing important is hidden behind a wall that the capture from eye height shows as a wall of a single color.
- ☐ Left and right are correct against the plan: check the top-down against the eye-height view at the same door (reversals are the common fault).
First 60 seconds of the player path
- ☐ The spawn has a clear direction, a first goal in view or hinted, and no immediate blocker.
- ☐ Within 60 seconds at walk speed (500 cm/s, so about 30 m) the player meets the first decision or reward. Measure the path length in the top-down.
- ☐ The first 60 seconds contain no gap, stair or door that fails the clearance checks above.
- ☐ Lighting at spawn is readable at eye height (not black, not blown out).
Player-scale review (several angles)
- ☐ Eye-height view at spawn, at each doorway, and at each landing.
- ☐ Four corner views plus the top-down, compared against the plan.
- ☐ Scale feels right against the capsule (a stand-in mannequin is visible in at least one capture).
- ☐ Anything that looks wrong gets one fix and a re-capture, not several fixes at once.
4. After the level is built
Write what worked and what failed into the jam lessons (see the Level building section of prep/agent-rules/UNREAL-AGENT.md), so it can become a skill.
Change log
- Template created 2026-11-11. No game values filled in yet.
Source
The workflow (blockout through MCP, inspect and correct, furnish, own-camera captures, a reusable contract, learnings kept as skills) follows Epic's "Exploring AI-assisted level design in Unreal Engine" (Chris Cook, Nov 11, 2026).