Sensory Overload Level Editor Guide

The Sensory Overload level editor is one of the features that turns a viral clip into a long-term craft. Developer updates describe a full editor for designing and playing community maps, with color-cycle tools and music-synced reward logic. This guide explains how to build courses that feel fair at speed.

If you are new to the fantasy, finish Getting Started and How to Play first. Editor authors who cannot clear Vertigo cleanly usually publish unfair maps.

What the editor is for

• Recreate campaign gimmicks to learn the tool
• Design community courses for friends and Workshop-style sharing (confirm Steam Workshop status on launch day)
• Prototype obstacle ideas from Discord community prompts
• Stress-test color cycles and breathing walls without Ranked ego

Official pre-demo messaging also mentioned community-designed obstacles feeding official levels — treat that as a feedback loop, not a guarantee every Discord idea ships.

Fairness rules for authors

1. Determinism first. Sensory Overload teaches through repeatable geometry. Avoid random invisible traps.
2. Readable tells. Even hard maps need a beat or silhouette players can learn.
3. Half-speed testing. What feels fair to the creator at full speed often feels cruel to first-timers.
4. One new gimmick at a time. Stacking spin + strobe + compression on beat one is a rage-quit factory.
5. Accessibility respect. Remember players may disable speed lines or thicken outlines (Accessibility Settings). Do not rely on illegible camouflage alone for difficulty.

Suggested authoring workflow

1. Sketch the fantasy in one sentence (“Peristalsis throat with late color flip”).
2. Block a short corridor with generous gaps.
3. Add one visual layer from the Difficulty Tier List vocabulary.
4. Play five observation runs yourself in Practice Mode if available.
5. Invite a friend who is worse than you — if they cannot name why they died, fix readability.
6. Only then raise speed or stack effects.

Music sync and color tools

Composer credit on the store page goes to Giorgio Satta; music sync is part of the fantasy when you play cleanly. In the editor, use color-cycle presets as foundations, then customize. Color-swap frequency was extensively playtested for intensity versus fairness — lean on presets before inventing seizure-grade strobes.

Sharing and etiquette

• Label maps with expected skill (Vertigo-like / Apocalypse-like)
• Note comfort warnings if strobe intensity is high
• Prefer short courses for first uploads
• Link your Discord bug reports separately from map feedback

Track editor-related launch notes on Patch Notes and Roadmap. For competitive play after publishing, return to Ranked Mode.

Common author mistakes

• Designing only from spectator camera memory of viral shorts
• Using false mirrored paths without a learnable rule
• Forcing mouse-precision gaps that ignore Controls habits
• Publishing without a clean restart loop

The best community maps feel like a stern teacher. The worst feel like a coin flip. Build teachers.

Obstacle vocabulary for authors

Borrow language from campaign pages so players can transfer skill:

• Rotation literacy from Vertigo
• Color camouflage from Nausea & Peristalsis
• Stacked chaos from Apocalypse

When your map invents a new gimmick, write a one-line tell in the description. Secret rules that only work in the author’s head fail the determinism thesis in Mechanics Deep Dive.

Playtest roles

Invite three kinds of testers:

1. A skilled friend who clears Apocalypse-like stacks
2. A mid friend who lives on Vertigo
3. A comfort-sensitive friend who uses Accessibility Settings

If only the skilled friend survives, your map is a clip, not a course. If the comfort-sensitive friend cannot name a tell after five deaths, raise outline-friendly contrast or slow the first teach beat.

Music and intensity budget

Music sync should reward clean play, not punish first attempts with seizure-grade strobes. Cap palette flips per ten seconds during teach segments. Save maximal intensity for optional late corridors labeled as such. Players coming from Motion Sickness Tips will quit maps that ignore this budget — and they will be right.

Publishing checklist

• Title includes expected difficulty band
• Description lists comfort warnings
• Restart loop is clean from death to checkpoint or start
• No invisible traps that Compatibility renderer cannot show
• One intentional near-miss farm section max, never required
• You personally cleared the map after a day away so memory bias cooled

Authoring is another way to study the tunnel. The editor teaches fairness the same way Practice Mode teaches segments — by forcing you to see what learners actually experience.