Neighbour Event in the cabin game

Neighbour is the event card players mention when the lights die and someone in voice chat starts talking about a crash instead of a jumpscare. The on-screen payoff is a bald, long-fingered figure in a suit and tie, mouth stretched open, standing in a dusty storage room of cardboard boxes, crates, and a warehouse scale. The mechanical problem is larger than the scream: the card drops darkness, and some clients crash when it goes dark. This page treats both halves as real.

Neighbour is one named event inside a 30+ card, 12 monster Early Access mix. It is not a lobby pick and it is not every darkness in the game. For the rest of the bodies, use the monster roster and the Monsters Hub. For how this card ranks against attic, monkey, and Cutting Corner, stay on event cards.

the cabin game entered Steam Early Access on 27 August 2026 (Twisted Corridor). 1–4 players, solo or online co-op, English only in-game. Press M if you can still reach the overlay after the lights drop.

What the card does

You play Neighbour (or the deck plays it into the table). The cabin goes dark. If your client stays up, you eventually meet the suited figure among the boxes. If your client does not stay up, the minigame never becomes a readable fail state — the run just ends in a crash. That is why Neighbour sits at the top of the danger/readability ranking: unreadability can be a hard quit.

The storage room is a set you should assume exists somewhere in the player-designed cabin. If your only box room is a one-door Garden Shed or Cellar, that is where you will be when the scream happens. Loops still help if you can move. They do not help if the process has already died.

Do not confuse this figure with the hallway gaunt (“Welcome to Reality” wall), the giant monkey, the headless table set-piece, the child’s-room toy-box, or Attic stalker. Neighbour is the suit in storage. Attic is totems in the rafters. Mixing tickets on Discord wastes the First Round patch window.

Crash reports and a practical workaround

Players report crashes when Neighbour goes dark. This wiki is not going to pretend that is a skill check. Early Access is allowed to be unstable; your job is to keep the lobby in the game.

• Lower settings before you sit down, especially if the machine already hitching on other events. Start with settings rather than debugging graphics in pitch black. Effects, shadows, and anything that spikes when lighting changes are the first knobs to try.
• 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 what you can still remember: GPU, whether the crash hit at lights-out or at the scream, player count, and whether anyone was in the storage room yet. The store page points community feedback at Discord and the discussion boards. A reproducible darkness crash is more useful than a clip of the scream.
• After a crash, check patch notes before you assume the bug is eternal. First Round already moved attic totems and monkey collision; lighting crashes can land in a later note. Also skim Early Access so you are not repeating a fixed issue.

If the client stays up, treat the scream like any other chase: do not reverse into a one-door room, do not spend a time-skip to “get past” a card that is still in the deck, and do not dump investigation just because the lights were rude.

How Neighbour fits the card priority

The Cards Hub order still holds.

1. Investigation and room connectivity first. Darkness is worse in a cabin you cannot walk.
2. Lifesavers in a pinch if the monster pawn on the clock track is about to catch you while the lights are out. Neighbour does not pause the rim.
3. Events you understand. After you have survived (or crashed) Neighbour once, you understand it well enough to decide whether your settings can take another copy.
4. Time-skips last. Skipping the clock inflates solo length and does not delete Neighbour from future shuffles.

Candy at the Boo Factory will not light the storage room. Cosmetics, lobby pets, and tricks ‘n treats are for the lobby.

Co-op habits when the lights die

Online co-op. Call darkness immediately. If one client hitching, say so before anyone walks into boxes. Host should be the person with the most stable settings if you have a choice — a host crash ends more than one scream. Keep one player near a known loop door, not all four stacked in storage. English-only audio means the suited figure will not politely localize a warning; you have to talk.

Solo. You cannot ask a friend whether they crashed. Lower settings first. Check the clock pawns before you play an unread event. If a lifesaver is in hand and the pawn is close, spend the saver at the table while you can still see it. Time-skips are an especially bad idea here: you lengthen the solo run and still have to draw darkness later.

After Neighbour resolves (or crashes)

If you are still in the session, sit down, check both pawns, and log a line in the clue notebook: lights-out, crash or no crash, storage scream or not. Then return to clues and how to escape. Neighbour does not name the exit.

If the session died, relaunch, confirm settings, and do not immediately slam the same unread event. Read survive events for minigame habits that are not darkness-specific, and getting started if this was your first shuffle. Attic problems (totems, running) belong on Attic stalker, not on this ticket.

Neighbour is a readable scream when the client lives. Until lighting is stable on your machine, treat the card as a settings check that happens to include a suited man in a room full of boxes.