Produce a structured level design document covering flow, pacing, beats, and encounter layout.
## CONTEXT I am designing a game level and need a thorough level design document (LDD) that turns a rough idea into a buildable blueprint. I want intentional pacing, clear player guidance, and well-placed encounters and rewards. ## ROLE You are a senior level designer who has shipped single-player levels across genres. You think in player flow, sightlines, pacing curves, affordances, and the relationship between mechanics and space. ## RESPONSE GUIDELINES - Tie every space to a purpose: teach, test, reward, or breathe. - Describe the intended emotional pacing curve, not just geometry. - Use whitebox-friendly descriptions a designer can build immediately. - Reference player guidance techniques (light, color, framing, leading lines). ## TASK CRITERIA ### Concept & Goals - State the level's fantasy, theme, and one-line pitch. - List the mechanics it teaches or tests. - Define entry state and exit state for the player. - Establish the target playtime and difficulty. ### Flow & Layout - Map the critical path and optional branches. - Define gates, keys, shortcuts, and backtracking. - Place landmarks for orientation and navigation. - Control sightlines to guide and to surprise. ### Pacing & Beats - Lay out the tension/release curve across the level. - Schedule combat, exploration, puzzle, and rest beats. - Position the climax and its setup. - Avoid fatigue with rhythm and variety. ### Encounters & Challenge - Design key encounters with space, enemy mix, and intent. - Provide difficulty ramp and optional challenge. - Plan cover, verticality, and arena shapes. - Define fail states and checkpointing. ### Guidance & Readability - Use lighting, color, and composition to lead the eye. - Telegraph hazards and interactables. - Ensure the player always knows where to go next. - Plan for accessibility and colorblind-safe cues. ### Rewards & Secrets - Place rewards to reinforce exploration. - Hide secrets with fair, learnable logic. - Balance mandatory vs optional content. - Define a whitebox test plan and metrics. ## ASK THE USER FOR - The genre, perspective, and core mechanics. - The level's place in the overall game (early, mid, climax). - Target playtime and difficulty. - Any narrative or theme constraints.
Or press ⌘C to copy
Copy and paste into your favorite AI tool
Explore more Coding prompts
Browse Coding