Level 6 guide
Level 6 is where many players stop using direct routes and start solving the room as a rule stack. The safe answer is slower, wider, and planned before the objective.
Evidence Status
Quick hint, no spoilers
If your first instinct is the direct path, choose the wider route instead. Level 6 punishes confidence more than slowness.
Evidence screenshots
Read the active rule as a route command. If the sentence changes, your old safe lane may be wrong.
Do not cross open space until Cobb is offset and you already know the return path.
Treat switches, pickups, furnace steps, and exit triggers as state changes, not simple errands.
When reach, smell, duplicate, or restored senses are active, nearby hiding becomes a failure point.
Level 6 route
Objective: Reach the visible objective and leave without letting Cobb own the return lane.
Safe lane: Outer loop first, objective second, exit third.
Failure point: Taking the center shortcut after the objective.
If Cobb moves into the center, the direct path is no longer your route.
Evidence route sheet
Community route notes point to switches first: clear the room setup before carrying objective items.
Treat coal/candle interactions as furnace setup. Do not carry an item into a dead lane unless the return is open.
Use the lower side of the room as the bait lane. Let Cobb commit downward before crossing back up.
Cobb should be pulled away from the furnace/objective lane, not raced through the same line.
Switches -> objective item -> furnace interaction -> bottom bait lane -> straight escape line.
Taking the objective before the switches or turning into a lane Cobb already owns.
Drop the objective plan, widen to the bottom lane, reset Cobb's path, then return from the opposite side.
Why Level 6 is hard
Level 6 is a wall because it makes the obvious route feel almost right. The mistake is not usually missing a hidden item; it is touching the objective while Cobb can still collapse the only exit.
Full solution
Complete the required room interaction while keeping a return lane open. The exact pressure can vary by build/rule roll, so route discipline matters more than memorizing one line.
Expect the first serious overlap of movement, sensing, reach, or route pressure. If Cobb can smell or reach, do not use close hiding.
Start on the outside lane, look for the longest loop, then approach the objective from the side that leaves the exit visible. If Cobb shifts toward the direct lane, abandon the objective and widen the loop.
Wait until Cobb commits away from the exit lane, then take the objective and retreat through the widest side of the room. If the lane closes, skip the objective and reset distance.
Use the same wide loop, but cut the waiting time only after Cobb is visibly committed. The shortcut is timing, not a tighter path.
Touching the objective before planning the return, hiding too close, and reversing through a hallway that Cobb is already controlling.
Do not squeeze past Cobb, do not reverse through the same lane after Cobb reacts, and do not assume close cover is safe if smell or reach is active.
If Cobb enters your lane, stop forcing the objective. Pull Cobb around the outer side of the room, regain space, then return from a safer angle.
Death diagnosis
Likely cause: Cobb can see
Fix: Break line of sight before crossing and move cover-to-cover.
Likely cause: Cobb can smell or reach
Fix: Stop camping close. Use the outer loop and add more distance.
Likely cause: Cobb can duplicate
Fix: Your route had one exit. Pull one threat away before touching the objective.
Likely cause: Rule state changed
Fix: Pause after each interaction and rebuild the active-rule list.
Likely cause: Restored senses
Fix: Treat every final-room action as a new mini-level.
Spoiler layer
The winning idea is not a secret object; it is refusing the obvious shortcut. Touch the objective only when Cobb is committed to the long side and your exit lane remains open.
30-second summary
Page FAQ
Level 6 punishes the direct route. Plan the return lane before the objective and use the wide outer loop when Cobb controls the center.
Break sight first, stop forcing the objective, and pull Cobb around the long side before you return.
The rule state can make the room feel variable, but the reliable answer is still route discipline: objective, loop, backup lane, then exit.
People Also Search
Sources checked
Use: Official facts: developer credits, platform, input support, rating signal, screenshots, downloadable/browser builds, tags, and current public game metadata.
Authority: Primary official source
Status: Checked May 24, 2026
Use: Version check: v1.7 is a small balancing update affecting smell, long pursuit acceleration, and rock stun behavior.
Authority: Primary official version source
Status: Checked May 24, 2026
Use: Awards and credibility: #1 Overall, #1 Concept, #2 Presentation, #2 Enjoyment, #6 Use of Limitation, ranked from 58 ratings.
Authority: Official jam listing
Status: Checked May 24, 2026
Use: Audience signal only: confirms a major creator episode dated May 21, 2026 with a 35:34 runtime. Not used as gameplay authority.
Authority: Third-party popularity signal
Status: Checked May 24, 2026
Use: Timing reference for early room rhythm and general route pressure. Not treated as official gameplay documentation.
Authority: Specific public gameplay video
Status: Checked May 24, 2026
Use: Route comparison reference for longer progression and late-game pacing.
Authority: Specific public playthrough video
Status: Checked May 24, 2026
Use: Visual reference for late-game pressure and route collapse patterns.
Authority: Specific public gameplay video
Status: Checked May 24, 2026
Guide feedback
If a route changes, a new ending is verified, or a control prompt differs in the current build, send the page and what changed. This helps keep the guide source-based instead of rumor-based.
Report a correctionSources and uncertainty
Facts such as developer credits, platform, version status, jam rankings, and rating signals come from official itch.io pages, the official v1.7 devlog, and the official Major Jam listing. Route advice is written in original wording from current build observations, public video cross-checks, and aggregated community pain points, not copied comments.
