Shift At Midnight is an online co-op detective horror game for up to three players according to its official Store description. A July 23 official announcement added a selectable six-player lobby option, while also saying that the game was designed and marketed around three players and that larger groups were not recommended for a first playthrough. Treat those as two different facts: the menu may allow six, but the intended investigation rhythm is the three-player team.
Choose the team size
Three players map cleanly onto the game’s jobs: one person can inspect a customer, one can cross-check the computer or shop task, and one can watch the route and relay behavior. The roles do not need to be permanent. Rotate them so everyone learns the evidence loop and no single player becomes the only person who can identify a clue.
If six players join, expect more voices, bodies, and duplicated interactions rather than a simple two-team bonus. The official announcement explicitly cautions against larger groups for a first playthrough. Use a six-player lobby as a version-specific option, keep callouts short, and agree on who owns each customer before the shift begins.
Use proximity chat
Proximity chat is part of the Store page’s feature description and changes how information travels. A nearby player can describe an ID mismatch while a distant player may only hear the result later. Say the location and evidence in one sentence: “front customer, ID mismatch, computer check next.” Then move to the next useful action instead of narrating every thought.
During a breach, reduce the callout to the last known location and the route plan. Long explanations belong after the danger passes. If the group separates, each player should know where to regroup without making the same doorway the only exit.
Give every player an assignment
The Station workflow contains stocking, deliveries, cleaning, and serving. The Detective workflow contains ID checks, computer comparisons, and behavior observation. Assign one primary and one backup for the current customer; otherwise three players may all inspect the same object while no one notices a changed route.
The Survival workflow is also a team assignment. One player can announce the barricade, another can place a trap that protects the chosen retreat, and the third can keep sight or listen for the threat. Do not assume a tool is available simply because another player used it in a different mode or update.
Handle network problems
The July 22 official announcement gives a specific temporary workaround for players who cannot join a lobby: opt into the network-issues-patch branch and use access code networkissues, with everyone in the lobby on that branch. The announcement says a proper fix was planned. This is dated troubleshooting evidence, not a permanent Codes feature and not a reason to create a codes page.
The July 23 announcement also mentions a Russia lobby fix and other crash or cursor issues. If a connection fails, first compare the branch, build, and region context, then check the latest official announcement rather than copying an old code into a current guide. Never ask players to share account credentials or unknown executable files.
Share decisions, not every movement
Good co-op communication has a rhythm. The observer calls the evidence, the route player calls the safe space, and the final decision maker names the next action. Once that action is understood, stop repeating the same clue. This leaves room for proximity audio and for a teammate to report a changed customer or threat. If the plan fails, say which part failed—information, route, timing, or resource—so the next shift tests the right improvement.
Solo players can use the same rhythm as an internal checklist. Say the evidence quietly, look at the exit, choose the next interaction, and reassess. The Store page lists single-player and online co-op, so the guide should not imply that a second player is required for the core investigation. Co-op adds coverage and communication; it does not replace the need to verify the customer.
Recover after a split
If proximity chat separates the team, use a location-first regroup call rather than repeating the entire theory. The nearest player should keep the current customer or threat in sight, while the other players move toward a route that does not close every exit. When everyone is together, repeat the evidence and choose one decision maker. This is more reliable than three simultaneous accusations or three players placing tools in different rooms.
Keep the first run readable
For a first playthrough, use three players, agree on the callout format, and avoid six-player chaos until the team understands the customer checks. The Store page says shifts are randomly generated, so a short pre-shift plan is more durable than memorizing one route. After a run, record which role found the evidence and whether proximity range caused a missed callout.
Pick a mode-aware plan
Story, Endless, and Post-Story notes should be named in the callout when a behavior is mode-specific. The July 29 post’s Rakes and patience notes are explicitly tied to Endless/Post-Story, so a multiplayer group should not use them as a universal Story assumption. Save the mode with the run record and compare it with the latest official announcement before changing a shared strategy.
Sources and limits
Recommended guides
Choose the guide that matches what you want to do next.
All Multiplayer guides
1 focused guides with steps, checks, and current caveats.