the cabin game September 2026 Patches

September 2026 brought seven patches to the cabin game after the launch-week fixes. The first landed on 1 September, the second on 3 September, the third on 5 September, the fourth on 9 September, the fifth on 10 September, the sixth on 17 September, and the seventh on 26 September. The September 2026 patches move the baseline forward significantly: attic auto-end, turn-freeze fixed, chair bugs closed, The Knight simplified to one statue, accessibility toggles added, a critical soft-lock on the Knight win-death loop finally resolved, and exploratory work on random disconnects. This page covers all seven patches as the current build baseline as of 27 September 2026.

Twisted Corridor’s Early Access build on Steam app 4406280 received its third through ninth official patches in September. Read this page alongside First Round Patch, 2nd Wave Bug Fixes, and the Optimization Update for the full chronology from launch week.

Minor Patch: 26 September 2026 (Build 25553694)

Twisted Corridor posted a minor patch on 26 September 2026. This patch focused on connectivity improvements and explored fixes for random disconnect issues some players were experiencing. The studio noted this is not a guarantee to fix the problem for everyone, but hopefully some players are able to play without interruption now.

Connectivity improvements

This patch targeted random disconnects that were occurring during gameplay sessions. The changes were described as exploratory - the studio was gathering data on disconnect causes and attempting to address them at the network level. If you experienced random disconnects before this patch, verify your build is updated and test in a new session.

What this patch did not fix

The September 26 patch was described as exploratory for disconnects. It does not introduce new content or claim to fix the Neighbour crash issue that remains a community report. If disconnects persist after updating, capture the exact circumstances (player count, event active, time into run) and report to the official Discord.

Patch 7: 9 September 2026 (Build 25215574)

Patch 7 addressed one critical issue that could end a winning run in tragedy:

Knight win-turn death loop - FIXED

Patch 7 fixed a soft-lock where winning The Knight event would kill the player on the same turn they won. Players who completed the statue puzzle correctly were being eliminated at the moment of victory, which the studio called “Patch 7!” in the announcement. If your group has footage from before this patch showing a player dying after a successful Knight solve, that is the now-fixed loop. Winning The Knight should cleanly end the event without a death on the same turn.

This fix was listed alongside optimization changes in the patch notes. The studio had been working on The Knight since the 2nd wave shortened its turn length on 29 August and Patch 4 simplified it to one statue on 3 September. Patch 7 removes the final punishing edge case.

Optimization changes

Patch 7 included optimization changes so many players should see improved performance. The studio noted these were backend improvements to reduce hitching and frame drops during intense sessions. No specific settings or toggles were added in this patch - optimization was applied at the code level.

Patch 5: 5 September 2026

The fifth September patch delivered the most significant bug fixes since launch week. Several long-standing Early Access issues were officially closed:

Cannot start turn - FIXED

The “cannot start turn” issue that has been the top reported bug since Early Access launch is fixed in Patch 5. If the Start Turn button still hides or fails to respond, press T as a workaround. If it still fails on the same current build, capture the exact circumstances and report it. Do not treat a leftover miss as a clue failure - verify files and rejoin if the button is truly unresponsive.

Chair and sit bugs - FIXED

Chair-related bugs that prevented players from sitting properly or caused unexpected behavior when attempting to sit have been fixed in Patch 5. This addresses launch-week reports of players being unable to complete the sit action at the table.

Disconnect during a run returns to lobby - FIXED

Previously, if a player disconnected mid-run, they could end up in a void state with no way back to the lobby. Patch 5 fixes this - disconnects mid-run should now return you to the lobby instead of trapping you in an empty space. The studio noted candy compensation is still coming for mid-game drops, but the void-state problem is resolved.

Light switch locations - hopefully finally fixed

The September 1 patch listed the light-switch fix as “maybe.” Patch 5 uses the phrase “hopefully finally” for this fix, suggesting the studio believes this issue is now resolved. If clients still see wrong or missing light switches after Neighbor drops darkness, capture it and report it with your build number.

Small Patch: 1 September 2026 (Build 25065979)

Twisted Corridor posted this patch on 1 September 2026, noting it should have shipped a couple of days earlier. Play-facing changes:

Attic event auto-end on sit

If the attic event does not auto-end on a win, it now force-ends when all players sit down. This addresses the frustrating situation where players had completed the attic objective but the event refused to close, leaving them stranded in the rafters while the clock kept moving. After this patch, getting all players back to the table should reliably terminate the attic event.

Cursor recentering at turn start

Cursors now recenter at the start of every turn. Some new players thought they were frozen after their mouse hit another monitor and failed to interact with the table. This quality-of-life fix makes the cursor behavior predictable and prevents confusion during critical turn decisions.

Invisible cursor after opening overlays

The invisible cursor bug after opening the manual, goodie bag, or settings on your turn has been fixed. Previously, some players found their cursor vanished when interacting with these overlays during their active turn, making it difficult to select cards or navigate menus.

The Neighbor Delay Visitor now works

The Neighbor card’s Delay Visitor choice now actually delays the Visitor. Before this fix, choosing the delay option may not have functioned as described, meaning players who thought they were buying time were not actually gaining the intended benefit. Confirm this works in your current build by watching the monster pawn on the clock track when Neighbor fires.

Light switch locations (maybe fixed)

Missing or wrong light-switch locations for clients are listed as a “maybe” fix. This was a client-side issue where some players could not find or interact with light switches in the correct positions after Neighbor dropped darkness. Treat this as partially addressed rather than fully closed.

Difficulty scaling on weenie and first-timer

Deaths on weenie and first-timer difficulties are now more forgiving and scale with player count. Example: a four-player game on weenie difficulty loses 15 minutes per death instead of 30; first-timer loses 30 minutes instead of 60 per death. This makes lower difficulties more accessible for their intended audiences without changing how the game scales at higher player counts.

Connectivity and compensation

Connection issues and lag are still being actively worked. If you drop mid-game, the studio noted they will compensate candy you would have earned. An in-game clue tutorial is in progress. If you cannot start a turn, send screenshots or recordings to the official Discord.

Update: 3 September 2026 (Build 25111102)

SteamDB shows this build was published on 3 September 2026 at 21:31 UTC. Official patch notes were not publicly posted beyond the list of changed files in one depot, but play-facing changes have been verified through community reports:

The Knight: one statue (major change)

The Knight event now requires only one statue instead of the previous multi-statue layout. This is a significant simplification of one of the longest and most grueling events in the Early Access build. The studio had been actively working on making The Knight less taxing since the 2nd wave shortened its turn length on 29 August. The one-statue change makes the event more manageable while still requiring players to understand the mechanic.

If your group has footage from before this patch, that strategy is now outdated. The event plays differently with one statue. Re-learn the timing rather than relying on older runs. The Knight remains a tax on the clock, but the one-statue layout is substantially easier to manage than the multi-statue version. Patch 7 later fixed the win-turn death loop that could still kill players on the same turn they won.

Accessibility toggles added

The September 3 build added accessibility toggles. These are new options for players who need additional accommodations beyond the existing photosensitivity warnings. Specific toggle names and options are not fully documented in public notes, but the addition represents a meaningful step toward making the game accessible to more players. Check the settings menu for new accessibility sections if you or someone at your table needs them.

Lobby-return disconnect fixes

The September 3 patch addressed lobby-return disconnects. Players who returned to the lobby after a run or during an event were sometimes disconnected unexpectedly. This fix should make returning to the lobby more stable, particularly for groups that like to retry immediately after a wipe or successful escape.

Cannot start turn issue (still present at this build)

The “cannot start turn” issue remains the top reported bug as of this build. The studio continues to investigate. Patch 5 later fixed this issue. If you encounter this on an older depot, update to the latest build.

What these patches changed for your next session

The September patches move the baseline forward in several meaningful ways:

First, attic events now close reliably when the group sits. No more stranded rafters.

Second, The Knight with one statue is a different event than The Knight with multiple statues. If your group learned the multi-statue version, re-learn it. The one-statue layout changes timing and attention allocation. And with Patch 7, the win-turn death loop is closed - winning The Knight no longer kills you on the same turn.

Third, the “cannot start turn” freeze that plagued multiplayer lobbies is now fixed in Patch 5. If the Start Turn button hides, press T as a workaround before reporting.

Fourth, chair bugs that prevented sitting are now fixed in Patch 5. Verify files and rejoin if you encounter sit issues on an older depot.

Fifth, mid-run disconnects now return you to the lobby rather than a void in Patch 5. Candy compensation for drops is still being worked on.

Sixth, the September 26 patch began targeting random disconnect issues. This is an ongoing effort - verify updates and test in fresh sessions.

What these patches did not fix

Neighbour crashes on certain hardware configurations remain a community report. Connection instability is still being worked. The clue tutorial is still described as “in progress” rather than shipped. The studio continues to ask for detailed bug reports on Discord with build numbers, GPU/RAM/Windows version, exact reproduction steps, and whether the issue persists after verifying game files.

For the full chronology from launch, start with First Round Patch, read 2nd Wave Bug Fixes for the launch-week context, then Optimization Update for the 30 August performance pass. Use settings for the current recommended toggles, and check the roadmap for what Twisted Corridor has promised for future updates.

Community reporting

If you encounter issues not addressed here, 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.”