kienbui1995 Level Design
When to Use
When designing individual levels or encounters — from first-time player intro to end-game challenge.
Core Jobs
1. Define the Level's Purpose
Every level has one primary goal:
- Teach: introduce a mechanic (tutorial)
- Test: challenge players with what they've learned
- Rest: lower intensity — exploration, narrative, reward
- Boss: peak challenge + culmination of zone themes
Mix these across a campaign: teach → test → rest → boss.
2. Pacing and Challenge Curve
- Establish a baseline difficulty before ramping it up
- Never increase difficulty on multiple axes simultaneously (new enemy type + new mechanic + harder platforming = frustration)
- Place rewards near challenges (reward = dopamine hit after difficulty spike)
- If players are stuck, add a shortcut or safe zone — don't just make it easier
3. Layout Principles
- Legibility: players should understand where to go without a map (environmental cues, lighting, framing)
- Exploration reward: optional paths should have meaningful rewards
- Landmarks: unique visual elements help players navigate and remember space
- Flow: optimal path should feel natural; detours should feel like discovery
4. Document the Level
Per level / room:
- Top-down map sketch (rough — specifics handled in engine)
- Enemy placement and patrol patterns
- Reward locations
- Narrative beats (if any)
- Intended time to complete and player emotional arc
Key Outputs
- Level brief (purpose, player arc, difficulty target)
- Layout map with annotations
- Enemy and reward placement doc
- Pacing chart for the zone/campaign
Anti-Patterns
- Difficulty spikes without preparation
- Linear levels with no exploration reward
- Teaching a mechanic and immediately testing it at max difficulty
- Levels with no clear navigation cues ("where am I supposed to go?")