the cabin game Host, Join, and Stay on One Build

the cabin game is a 1–4 player Steam Windows session. There is no local split-screen. If you want friends at the round table, someone hosts and everyone else joins over the network. In the first nights of Early Access that join step was a second horror game: codes that claimed they failed, lobbies that could not start a turn, and mixed builds that invented bugs the studio then had to chase. This page is the connection checklist. The social rules of the table live on co-op. The first-hour loop lives on getting started.

The game entered Early Access on 27 August 2026. English is the only interface and full audio; localization is planned. Price is $11.99 USD, with an introductory 30 percent Steam sale timed through 10 September 2026. Twisted Corridor is targeting a 6–8 month Early Access window. None of that helps if two people are on different depots.

Invite from Steam, then sit

Host from the in-game lobby after Steam has finished the latest update. Share the join code with the people you actually intend to play with. There are no public Roblox-style redeem codes for candy or cosmetics — candy is earned in-session and spent at the Boo Factory. If you searched this wiki for “codes,” you want this page for join codes, not a list of free cosmetics that does not exist.

Once everyone is in, sit. The Dining Room is the starting room. Press M. Assign a table caller so the clock track is not unsupervised while three people wander the Ranch. Voice chat exists in-game; use it. Controls covers sit, STAND UP, and the comfort sliders that keep a four-person session from melting.

Version mismatch is the real join killer

Twisted Corridor posted a dedicated news note: if someone in multiplayer cannot start their turn, have everyone verify game files. A version mismatch was causing that freeze. Same Steam library, different depot, broken table. Do not reinstall Windows. Do not blame the Knight. Verify, update, relaunch, then join again.

The Optimization Update then implemented a version mismatch check so mixed builds cannot play together. That check exists because mixed builds introduced bugs. If a friend cannot sit at your table after 30 August 2026, the first question is not “did you buy it.” The first question is “are you on the same public branch.” SteamDB’s public branch for app 4406280 was rebuilt on 30 August 2026 with that optimization pass. Close the game, let Steam update, verify files, then host.

A mismatch can look like a rules problem. It is not. Table rules assume a lobby that can actually take turns.

Join code said it failed — and maybe it didn’t

Early Access join codes sometimes printed failed to join when the join had worked. People left lobbies that were already valid. The Optimization Update fixed join code saying failed to join when it didn’t. If you still see that string, check whether you are already in the session before you spam the code again. If you are in, sit down. If you are not, verify files and try one more clean join.

Practical order:

1. Everyone updates on Steam.
2. Everyone verifies integrity of game files.
3. Host launches once and waits in the lobby.
4. Friends join with the current code, not a screenshot from last night.
5. If a code still fails, host generates a fresh one. Do not recycle a code from a crashed Neighbour lobby.

Firewall and VPN oddities are possible on any Steam co-op title. Try a direct invite from the Steam overlay if a typed code keeps bouncing. Then come back to the in-game code once Steam friendship routing works.

Performance is now part of hosting

The Optimization Update was “mostly about pushing some big changes for optimization.” Hosts on mid-range cards should still start from settings: Low graphics, VSync off, FPS cap actually applied (First Round made that cap stick), clock slider below master. Neighbour darkness still has crash reports; that is not claimed as an Optimization fix. If your GPU hitching-steps in the forest, you will throw the lobby even if the join code was perfect. Confirm system requirements before you promise a four-player night.

The studio’s own note on that patch is blunt: the game is still very early, and they apologized to anyone whose PC “caught fire.” That is a performance honesty check, not a joke to ignore. If a friend is on a GTX 970 at minimum spec, they may be the searcher who stays in well-lit rooms, not the chase runner.

After you are in the cabin

Do not drop tricks ‘n treats on a first join. Do not greed Event Cards while the notebook is empty. Do not all four stand up. The join was the hard part; the table still needs a caller. If The Knight lands, it is a long event that the 2nd wave shortened — dedicated notes are on The Knight. If someone gets stuck on the attic ladder, they may still be on a pre-2nd-wave bind; that patch fixed ladder collision and keybinds plus basement breakers.

Solo players can skip this page until they host. The moment you add a second body, this page is the first tab, then co-op, then survive events. Patch history is on the Updates Hub. Official Discord and Steam discussions are on Links.

This wiki is unofficial. Connection bugs still belong in an in-game report or on Discord, with GPU, player count, and whether the clock slider exists so helpers know your build. A clean join on one version is the cheapest win you will get all night.