The practical answer to “three or six players?” is to start with three. The official Store page presents Shift At Midnight as co-op for up to three players, and the July 23 announcement says six-player lobbies can be selected but the game was designed around three. Larger lobbies are therefore an available option with a different communication problem, not proof that every mission is balanced for six.
Three-player assignment
Give one player the Detective call: inspect the ID, lead the computer comparison, and report behavior. Give a second player the Station call: handle stocking, deliveries, cleaning, or serving without taking over the evidence check. Give the third player the Route call: watch movement, keep an exit open, and announce the defensive transition.
Rotate those roles between shifts. The assignment is a coordination aid, not a class system, and the public sources do not promise exclusive abilities. If the Detective player is far away, the Station player should be able to continue the check rather than wait for a single expert.
Six-player assignment
With six players, duplicate the three responsibilities into two small teams, but appoint one person as the final callout owner. Without that owner, two players may accuse different customers or lead the team toward separate exits. The official announcement’s first-playthrough warning is a good reason to learn the core loop with three before adding the extra voices.
Keep proximity chat in mind. A player who moves out of range may miss the ID result or the defense plan. Repeat only the location, evidence, and next action when regrouping. Do not rely on everyone seeing the same screen state at the same moment.
Rotate the callout owner
The final callout owner should rotate between shifts so the team learns how to synthesize evidence. That player does not overrule the others; they repeat the current facts, name the missing check, and select the next safe action. A rotating owner is useful in both three-player and six-player lobbies because proximity chat can make a correct observation invisible to the rest of the group.
Lobby troubleshooting
If a player cannot join, compare the branch and build before changing the team plan. The July 22 official notice suggested the network-issues-patch branch with access code networkissues as a temporary workaround, and said every lobby member needed the branch. This code is troubleshooting text with a date; it is not a reward code and should not be treated as a permanent feature.
Keep troubleshooting dated
The lobby option and branch workaround belong to different kinds of information. Six players describe a selectable lobby capacity in the July 23 post; the network-issues-patch branch is a dated connection workaround from July 22. If the current build no longer needs the branch, remove the instruction or move it into an archived note. Recheck the official announcements before sending a whole group to a branch, especially when players are on different versions.
Before launching, agree on the number of players, the callout owner, and the branch everyone is using. That one-minute check is more reliable than troubleshooting after a customer has already arrived.
If the group changes size mid-session, repeat the assignment rather than assuming the missing player’s role is covered. Clear ownership keeps the investigation moving.
Confirm the plan in proximity chat before the shift begins.
A simple six-player split
If six players are selected, pair one Detective and one Route player with each half of the station, then appoint one person to merge the reports. The pairings are a communication pattern, not fixed game classes. If both halves find different suspicious customers, the merge owner should record each location and evidence state before the team moves. This keeps the selectable six-player option readable without claiming that every encounter was balanced for six.