Multiplayer gives a PERIPHERAL team more eyes and more search capacity, but the official description warns that a group guarantees nothing. The advantage appears only when routes, generator states, the key, and the unsaved code are shared. A scattered team with incompatible callouts can lose more information than a careful solo player.
Agree on landmark language early
Use room features and junction shapes rather than relative directions. “Generator beyond the green pipe junction” survives a return trip; “left generator” may reverse when a player approaches from the other side. Repeat important callouts once so every player uses the same name.
When splitting, define a return point and a time or objective condition for regrouping based on current game feedback. The map is procedural, so do not assume two branches reconnect because they did in another match.
Assign flexible team tasks
Route caller
Maintains shared landmark names and connects generators, key, code, hiding options, and exit.
Power lead
Reads fuse and repair feedback, confirms current generator state, and identifies uncertain machines.
Code backup
Repeats the unsaved code back to the finder and preserves it through the hunt.
Scout
Searches connected branches and reports discoveries before moving farther from the known route.
These are tasks, not exclusive classes. Every player should know the exit plan so one lost life does not erase it.
Share objective state, not just discoveries
Report a generator as located, ready, running, failed, or uncertain. Electrician requires all three running at the same time, so “we did that generator” is not enough. Include fuse or repair warnings because the official description links poor work with earlier power failure.
Announce who has the key if the current interface assigns ownership. When the code appears, one player reads and another repeats it. The game does not save the code, and a single keeper can lose focus or disconnect from the route.
Before the final generator, require a team readiness call: stable power, key, backed-up code, exit route, battery, cover, and regroup point.
Survive together without clustering
Stay close enough to share danger information and respond, but avoid stacking every player in one doorway, repair, or hiding interaction. The current build must establish capacity and collision behavior; public sources do not.
Use short creature callouts: landmark, direction, and immediate plan. Looking back, hiding, holding breath, and staying quiet are supported mechanics. Their exact controls and timings are not public, so every player should follow the prompt on their device.
The Rescuer badge confirms a friend can be saved from the creature’s grip. It does not publish the rescue control or window. Respond to the live prompt, and do not send the entire team into the same danger based on an invented timer.
Handle voice and the Not a Word challenge
The Not a Word badge says to talk to your team and escape without the creature ever hearing your voice. That wording confirms a voice-related challenge while requiring some team communication. It does not reveal channel, distance, volume threshold, or when listening is active.
For normal play, use concise communication and follow any current indicator. For the badge, preserve the exact condition rather than reducing it to “mute the microphone.” Simply never talking may fail the stated requirement. Keep text or non-voice alternatives available where the live rules allow them, but do not claim they automatically satisfy the badge.
Regroup for the final escape
The Nobody Left Behind badge requires escaping with the whole group alive. Before completing the exit, confirm that all intended players are alive and at the route. A player separated by a failed generator or creature encounter can turn an early exit into a missed team goal.
The normal Survivor badge only requires escaping the building, so decide before the match whether the team is pursuing the group condition. During the red-light hunt, keep the destination simple and avoid changing landmark names.
Recover when coordination breaks
If players disagree on the route, return to the last shared landmark. If the code differs between keepers, revisit the display through the known path rather than guessing. If a generator fails, send the player who knows its route and repair state while the rest preserve the exit plan. If a player loses a life, re-share key, code, power, and regroup state.
Disconnected or new players should receive a compact summary, not the entire history: current generators, key, code keeper, exit landmark, and hunt state.
Unverified multiplayer details
Team size, matchmaking, difficulty scaling, voice detection, rescue timing, death state, revival, objective ownership, and whether group membership changes rewards need live testing. The official facts still support a strong team method: agree on landmarks, share state, back up the code, split only along connected routes, prepare before the final generator, and regroup before the exit.