the cabin game Early Access Bug Tracker

This is a temporary Early Access troubleshooting hub, not a permanent pile of launch-day keyword pages. It stays indexed only while the issues are real, repeated, and useful to diagnose. Once a bug is confirmed fixed long enough that players stop searching for it, its section moves into patch history or a short troubleshooting FAQ.

Twisted Corridor’s Early Access build on Steam app 4406280 entered Early Access on 27 August 2026. The studio has posted five patches as of 7 September 2026. This page tracks bug status through that sequence. For full patch notes, see September 2026 Patches, Patch Notes, and Optimization Update.

Status table

Problem	Current status	What to do now
Attic ladder soft-lock / input	PARTIAL FIX — Aug. 29 fixed one collision issue and keybinding problems; other ladder issues still investigated	Update first. If still locked, record the exact interaction state and report it; do not trust old workarounds as permanent
Basement breakers keybinding	FIXED IN AUG. 29 PATCH	Update and re-test before changing bindings or reinstalling
Feeling Small toy disappears	FIXED IN AUG. 29 PATCH	Update before retrying the event
Musical Rooms popcorn / monkey blocking	FIXED / CHANGED AUG. 28	Old videos with blocked narrow halls are not current behavior
End-game forest / missing exit state	MAYBE FIXED AUG. 28 according to developer wording	If the end state still strands the group, capture the run and report it; do not assume the room deduction was wrong
Max FPS setting not applying	FIXED AUG. 28	Update first, then tune normal graphics settings
General low FPS / high GPU	PLAYER-REPORTED / HARDWARE-DEPENDENT — Aug. 30 shipped a larger optimization pass	Lower expensive settings / screen percentage as a diagnostic, not as an “official fix”
Attic event does not end after a win	FIXED SEP. 1 — event now force-ends once all players sit down	Update first; if it still hangs, report the current build
Cursor frozen / invisible on turn	FIXED SEP. 1 — cursors re-center each turn; opening manual/goodie bag/settings no longer hides the cursor	Update before assuming a freeze
Neighbor “Delay Visitor” does nothing	FIXED SEP. 1 according to the developer notes	Re-test on the current build; do not copy launch-week “it is broken” posts
Weenie / First Timer death time penalty	CHANGED SEP. 1 — more forgiving, scaled by player count (example: 4-player Weenie 30→15 minutes)	Old “one death costs half the clock” advice is stale on those difficulties
Cannot start turn in multiplayer	FIXED PATCH 5 — if the Start Turn option still hides, press T. Leftover misses are a report, not a clue fail	Update first. If the button is missing, press T, then report the lobby if it still fails
Dropped from multiplayer mid-run	OPEN — connectivity/lag still being worked on; candy compensation promised for mid-game drops	Stay on the same build (Aug. 30 added version mismatch blocking); do not treat a drop as a clue failure
Disconnect during a run dumps you in the void	FIXED PATCH 5 — you should return to the lobby instead of the void	Update before assuming a mid-run drop still strands you
Clients disconnect when returning to the lobby	FIXED PATCH 4	Update before assuming a leave-lobby drop is still the old bug
Chair / sit bugs	FIXED PATCH 5	Update before copying launch-week sit clips
Missing / wrong light switches for clients	HOPEFULLY FINALLY FIXED PATCH 5 (developer: “hopefully finally”)	If clients still see wrong lights, capture it; host-only views can still lie
Dead-body collision blocking players	CHANGED PATCH 4 — collision removed from corpses	Old “walk around the body” clips are stale

Attic ladder: do not publish yesterday’s workaround as today’s fix

The Steam discussion hub contains a launch report of a player soft-locked in front of the attic ladder after another player finished the event. The Aug. 29 developer patch then says:

• one attic-ladder collision bug was fixed;
• keybinding issues that caused many players to get stuck while climbing were fixed;
• other attic ladder issues were still being investigated.

That combination matters. A blanket “fixed” label would be wrong; a blanket “still broken” label would also be wrong. Update first, then report the exact interaction state with your build number.

Sparky’s fuse / breaker interactions

A current Steam discussion says, “I can’t get off the fuse box.” The Aug. 29 patch explicitly fixes basement breaker keybinding issues, but does not name every fuse-box report as resolved.

So the safest path is update → retry → report the exact interaction if it still reproduces. This site does not invent a key sequence that the developer has not confirmed.

End game: forest teleport, missing car and limbo states

The Aug. 28 patch uses unusually cautious wording: it (Maybe?) fixed the end game where some players thought they escaped by teleporting to the forest outside the cabin.

One supplied current-build session also reaches the end and finds an invisible/missing car state while the players are unsure whether the escape was wrong or bugged. That is exactly why this page separates game logic from technical state.

If you have strong clue evidence, reach the end, and the environment becomes unusable, treat it as a possible bug and capture a screenshot/video for the developer.

Performance: what is official and what is only observed

Official patch evidence:

• Aug. 28 fixed the max FPS setting not applying.
• Aug. 29 made “slight optimization updates.”
• Aug. 30 shipped a larger optimization pass labeled “mostly about pushing some big changes for optimization.”

Player footage observations:

• lowering GI / general quality improved one player’s frame rate;
• another player lowered resolution to 1600×900;
• a Steam review reports lowering screen percentage helped FPS while GPU usage remained high.

Those are diagnostics, not universal fixes. Different GPUs, resolutions and capture/streaming loads can change the result. Start from settings before buying new hardware.

Clock audio is no longer the same launch problem

Multiple early players complained about the ticking clock volume. The Aug. 28 patch added a separate audio slider for the ticking clock. Old reviews and videos are useful history, but the current guide should send players to that slider rather than repeat the launch complaint as if nothing changed.

Neighbour darkness crashes

The Neighbour card drops darkness and some clients crash when the cabin goes dark. This is not a skill check or a settings tuning exercise — it is a real Early Access stability issue.

If your machine hitching-steps on other events already, lower settings before sitting down at a Neighbour lobby. If a teammate already crashed on Neighbour this session, do not “test it again” on the same settings. Change something or skip slamming unread events until you have a stable run.

Report the bug on Discord with GPU, whether the crash hit at lights-out or at the scream, player count, and whether anyone was in the storage room yet. A reproducible darkness crash is more useful than a clip of the scream.

Full notes: Neighbour and settings.

When this page should be merged or removed

If a bug remains fixed for long enough that players stop searching for it, its section should move into patch history or a short troubleshooting FAQ. The site should not preserve short-lived launch problems just to keep extra URLs indexed.

As of Patch 5 (Sep. 5, 2026), the following bugs have been officially closed: cannot start turn, chair/sit bugs, mid-run void disconnect, lobby-return disconnects. These sections should be removed from this page within a few weeks if no new reports surface.

How this guide was verified

Primary evidence is the developer’s Aug. 28, Aug. 29, Aug. 30, Sep. 1, Sep. 3 (Patch 4) and Sep. 5 (Patch 5) notes. Steam discussion reports and supplied gameplay are used to show how the bug presents, not to upgrade unverified workarounds into official fixes.

Report a new bug

Verify your build number in Steam, then report to the official Discord with:

• Your GPU, RAM, and Windows version
• The exact event, room, or interaction that caused the problem
• Whether the issue persists after verifying game files
• Your player count and whether the issue is reproducible

Useful reports include screenshots, build numbers, and precise reproduction steps. “It crashed” without context is harder to act on than “Neighbour event, darkness dropped, client frozen, GTX 1070, 2 players, reproducible on weenie difficulty.”