Skip to content

t1k:designer:level:core

FieldValue
Modulelevel
Version1.8.2
Efforthigh
Tools

Keywords: design, environment, level design, map design

/t1k:designer:level:core

  • Designing battle arenas, dungeon rooms, or open-world zones
  • Placing obstacles, cover, or spawn points for AI units
  • Planning encounter pacing, difficulty waves, or boss arenas
  • Designing player movement flow (linear corridor, hub-and-spoke, open world)
  • Adding environmental hazards, traps, or interactive elements
  • Sizing arenas for unit counts (how big should this arena be?)
  • Player must understand the space within 3 seconds of entering
  • Landmark (weenie) visible from spawn — directs movement without text
  • Distinct zones by floor/wall texture, lighting color, or height variation
  • Every path leads somewhere meaningful (reward, shortcut, information)
  • Dead ends only if they contain loot or environmental storytelling
  • Chokepoints are designed — never accidental narrowing
  • Off-path content gives optional rewards (not mandatory progress)
  • Curiosity is rewarded: 80% exploration → bonus loot, 100% → achievement
  • Secrets require skill or observation, never luck
ShapeBest ForWeaknessKey Rule
CircularBoss fights, duel arenasPredictable rotationAdd center obstacle to break circling
CorridorAmbush, chokepoint tensionLimited tacticsWiden mid-fight: destructible walls, branching
Multi-roomDungeon crawl, stealthPacing breaks between roomsConnect rooms with visible reward glimpse
Open fieldCavalry/ranged battlesMelee struggles for coverScatter 4–6 cover clusters asymmetrically
  • Ranged behind melee: ranged units start 8–12m behind front line; melee absorbs aggro
  • Flankers on sides: 1–2 fast units spawn 45° off-axis from player entry — forces rotation
  • Never spawn behind player: staging zone extends 3s travel from entry point (enemy-free)
  • Elite placement: elite/mini-boss at arena center-back — player must push through adds
  • Density rule: max 1 ranged per 2 melee at standard difficulty; invert for hard encounters
  • Risk-reward distance: high-value loot placed at maximum travel from safe spawn
  • Tier system: common → safe path; rare → off-path detour; legendary → boss/hazard-gated
  • Visual breadcrumb: player can see reward before committing — respects decision-making
  • Chest trap rule: any chest in open sight without obstacles is suspicious — teaches awareness
  • Wave entry points: 2–4 entry directions; rotate per wave to prevent corner camping
  • Reinforcement lanes: separate lane from main combat area; arrives from flanks on timer
  • Staging buffer: 2–3s before spawned enemies reach player — prevents spawn-kill
  • Visual telegraph: spawn FX (portal glow, dust cloud) 1s before unit appears
Encounter #Relative DifficultyMechanic Introduced
1Tutorial (50%)Basic attack pattern
2Easy (70%)Ranged + melee mix
3Medium (90%)Environmental hazard
4Hard (110%)Elite + adds combo
5Rest/rewardNo combat or trivial
6Boss (150%)All mechanics combined

Stat scaling per tier: HP ×1.15/tier, damage ×1.10/tier, speed ×1.05/tier.

Per-Mechanic Level Structure (Teaching → Main Body → Finale)

Section titled “Per-Mechanic Level Structure (Teaching → Main Body → Finale)”

Within a single level that introduces a new mechanic (new enemy type, hazard, ability, traversal rule), structure the space as three acts:

ActSpatial PatternPlayer Experience
TeachingSafe arena entry, mechanic appears in isolation, clear sightlines, low/no enemy pressureDiscovers the rule by interacting; particle/environmental hints replace text where possible
Main BodyMechanic mixed with previously-mastered systems, light pressure (1-2 enemies, soft timer)Applies the rule under manageable distraction
FinaleHarder variant of the mechanic, time/resource pressure, optional show-off route for collectablesStress-tests mastery; an alternate path lets stuck players progress while experts express skill

This is the level-scoped expression of the difficulty saw (per-mechanic cycles, not a monotonic curve). Across an arc of N levels, each new mechanic gets one full Teaching→Main→Finale cycle before the next mechanic is introduced. → See puzzle-game-design/references/difficulty-saw-framework.md.

Empirical Playtest Methods (Beyond Spreadsheet Tuning)

Section titled “Empirical Playtest Methods (Beyond Spreadsheet Tuning)”

Before locking encounter difficulty, gather real-player data:

MethodWhat to TrackThreshold / Signal
Death-location heatmap(level, position, attempt#) of every failureCluster on one tile/spawn = local spike; cluster at entry = readability problem
Encounter completion drop-off% reached and % completed per encounter>40% consecutive drop = panic signal; <5% drop = encounter adds no friction
Footage / silent observationFirst failed attempts of unfamiliar playersIf 4 of 5 testers try the same wrong move first, the level’s visual language is misdirecting
Structured friend testingScripted, specific questions (“How long on encounter 4?”, “Which arena made you put the controller down?”)Outliers across 5+ testers are signal; single anecdote is not

→ See game-balance-tools/references/validation-methods.md for paired simulation methods.

Design TaskKey RuleReference
Arena sizingsize = max_units × 2-3m (melee) / 5m (ranged)references/arena-layout.md
Obstacle coverage15-25% of floor area for tactical depthreferences/arena-layout.md
Encounter density1 encounter per 30-60s travelreferences/encounter-pacing.md
Difficulty patternEasy → medium → easy → hard → rest → bossreferences/encounter-pacing.md
Hazard telegraphing0.5-1s wind-up warning before damagereferences/environmental-hazards.md
#Anti-PatternProblemFix
1Invisible wallsPlayer frustration, breaks immersionUse natural barriers (cliff, water, locked door with visible key)
2Dead ends with nothingFeels like wasted spaceAdd loot, lore item, or shortcut unlock to every dead end
3Unfair spawnsPlayers spawned in combat rangeStaging zone: 2-3s of safety before enemy can reach spawn
4Symmetric arenasPredictable, no exploration valueAsymmetric with mirrored spawn distances (fair but visually varied)
5Random hazard timingFeels unfairAll rhythm hazards use predictable, learnable cycles
6Over-coverage obstaclesUnits clip, pathfinding breaksCap obstacles at 25%; leave clear corridors for Navigation mesh
7Reward high performers with harder-only contentOnly experts ever reach the asset → wasted budgetPlace expert content as optional bonus path off the main route, not gated behind elite-only access
8Punish poor play with harder future encountersDeath spiral: failing player gets harder spawns, churnsSilent rubber-band: detect 3× consecutive failure → invisible 10-15% reduction; never announce
9Unskippable cutscenes in high-retry areasEach retry replays narrative → rage-quit signalSkip-after-first-view; auto-skip after death in same encounter
  • game-feel-juice — environmental feedback (rumble on hazard hit, particle on trap trigger)
  • game-ux-design — spatial UI (minimap, objective markers, zone transition prompts)
  • engine navigation/scene skills (auto-activated via registry) — arena geometry and pathfinding tools
  • engine navigation skills (auto-activated via registry) — pathfinding constraints for obstacle placement
  • game-encounter-design → (use game-balance-tools for encounter difficulty tuning)
  • puzzle-game-design — room-based level design for puzzle dungeons
FileCoverage
references/arena-layout.mdShapes, obstacle %, spawn zones, cover, chokepoints, sizing formula, height variation
references/spatial-flow.mdWeenies, breadcrumbs, hub-and-spoke, linear corridor, open world zones, verticality
references/encounter-pacing.mdEncounter density, difficulty wave, boss arena, reward placement, roguelike structure
references/environmental-hazards.mdHazard types, telegraphing, fair placement, interactive hazards, rhythm patterns, scaling
  • Spatial flow ≠ encounter pacing — a beautifully laid-out arena can still feel monotonous if encounters all peak at the same intensity.
  • Spawn zones must be reachable AND defensible — testing this with paper-prototype spawn lists before geometry saves art rework.
  • Gating mechanics that bottleneck player progression vs gating mechanics that punish exploration are different design choices — name which one you’re doing.