| name | pacing |
| description | Shape the rhythm of challenge, traversal, discovery, narrative, rest, resource pressure, and intensity across a level using timed play and player-state evidence. |
Level Pacing
Use when a level needs intentional rhythm rather than uniformly dense activity.
Procedure
- Define the intended emotional or gameplay arc and the level's role relative to what comes before and after it.
- Map segments by activity type, intensity, duration, cognitive load, resource pressure, novelty, and narrative information.
- Estimate and then measure actual traversal or encounter durations through play rather than relying only on map size.
- Alternate pressure and recovery deliberately, allowing players time to orient, learn, anticipate, or appreciate important spaces.
- Introduce mechanics and complexity at a rate compatible with player learning; avoid stacking new demands before earlier ones can be practiced.
- Use rewards, vistas, narrative beats, checkpoints, shortcuts, or low-threat traversal to shape decompression without creating dead time.
- Observe where players rush, stall, get lost, repeat content, or become fatigued and distinguish intended tension from accidental friction.
- Iterate segment order, spacing, encounter density, resource distribution, and transition duration based on playtest evidence.
Decision rules
- Pacing is the sequence of player experience, not a fixed formula of action and rest beats.
- Quiet time needs purpose just as action does.
- Measured playtime is more useful than designer estimates once a blockout exists.
- Difficulty, novelty, navigation, and narrative all contribute to cognitive load.
Quality gate
Pacing is ready when the level has a deliberate and playtested intensity arc, learning and recovery windows support the target player, repeated friction is distinguished from intended challenge, and measured play demonstrates a rhythm consistent with the level's role.
