The short answer
The short answer
Most PEAK connection reports fall into one of three paths: the lobby join path, the saved-world path, or the live connection path. Room-code errors and Loading hangs start with the join flow; death, skeletons, and missing items after Continue Run start with saved player or world state; voice and controller prompts need local input checks. The steps below separate official fixes from player-reported possibilities so a retry does not become a guess.
PEAK multiplayer issue matrix
Each row follows the same order: symptom, possible cause, steps, applicable version, current status, and official source. The possible-cause field is deliberately cautious. A symptom can have more than one cause, and a patch note proves that a case was addressed, not that every similar-looking failure has the same cause.
Start with the smallest reversible test. Verify the current build, use a fresh room, ask whether the host or the joining player saw the problem, and change one variable. Never publish a room code, account identifier, password, or token in a support report.
| Symptom | Possible cause | Solution steps | Applicable version | Current status | Official source |
|---|---|---|---|---|---|
| Join a friend and die immediately | Saved player state or a reconnect case carried a dead state into the lobby. | Update; test a fresh lobby; if using Continue Run, let the host load the campfire first; record host or joiner role. | 2.5.a-2.6.a | Fixed for named cases; new reproductions pending. | Patch 2.5.a and Patch 2.6.a |
| Reconnect as a skeleton | A save or reconnect loaded the player as a skeleton and an old case could kill them instantly. | Return to the same host; avoid repeated reloads; test a fresh run; keep the exact sequence. | 2.5.a-2.6.a | Named cases fixed; still version-sensitive. | Patch 2.5.a and Patch 2.6.a |
| Items disappear after loading a save | World state and nearby campfire luggage were not serialized consistently, especially for non-host saves. | Have the original host load the save; inspect the campfire; do not migrate the save between hosts while diagnosing. | 2.6.a | Mitigated; official caveat says non-host world state can still be odd. | Patch 2.6.a |
| Non-host save looks different | Non-host clients do not receive the complete world state in every save path. | Keep the original host as host; compare the item list at the campfire; report only the objects that differ. | 2.6.a | Still possible by official caveat. | Patch 2.6.a |
| Room code is rejected or menu hangs | Bad or nonexistent code, stale menu state, or a join path affected by an older patch. | Generate a new code; use JOIN GAME; check the code character by character; restart the menu; retest on 2.5.a or later. | 2.5.a-2.6.a | Named loading and button failures fixed; player report pending if current. | Patch 2.5.a and Patch 2.6.a |
| Loading screen never completes | Nonexistent room, cross-region route, or slow connection during a late join. | Confirm the host is still in the lobby; retry with a fresh code; test the same region; wait for the host to finish loading. | 2.5.a-2.6.b | Cross-region and late-join cases addressed; still possible on unstable networks. | Patch 2.5.a and Patch 2.6.b |
| Mid-game join shows a t-pose skeleton | Late-join player state or slow client initialization. | Update; let the host reach a stable area; join again once; record hardware and connection timing if it repeats. | 2.6.b | Fixed in the official post; repeat reports pending. | Patch 2.6.b |
| Cross-region connection stalls | A different part of the world can add latency or prevent the join handshake finishing. | Try the same region; compare host and joiner; use one fresh invite or code; do not call it a server outage without more evidence. | 2.5.a | Fixed for the named Loading case; local routing can still vary. | Patch 2.5.a |
| Voice chat stops working | Mute state, push-to-talk setting, device selection, or a patch-specific voice state. | Check the HUD mute indicator; confirm the input and output devices; toggle the setting once; test a fresh lobby. | 2.04.a and later | HUD mute feedback is fixed; the local device path is still report-dependent. | Patch 2.04.a |
| Controller cannot select Continue Run | Controller focus or menu state did not move to the save action. | Move focus with the controller, reconnect it before launching, test keyboard input once, and report the exact menu state if only the controller fails. | Player report; no matching fix confirmed in the checked posts | Player report pending. | Recent player feedback and official feed |
A controlled retest that preserves evidence
The fastest way to lose the useful detail is to change five things at once. Create a short test with the same host, the same joining player, and a new room code. Write down the patch, region, invite or code path, and whether the run was new or loaded. If the symptom disappears, that is a result to record, not proof of which variable was responsible.
When the problem is a save, keep the original host. Patch 2.6.a says non-host saves can still show a little world-state weirdness when another player hosts from a save, so moving the save between hosts can recreate the very condition you are trying to isolate. Use the save guide for item and achievement state before deleting anything.
- 1. Verify the version Use the current Steam build and note the patch title in the report.
- 2. Record roles Host, joining player, reconnecting player, and controller or keyboard input all matter.
- 3. Use one join path Test a Steam invite or a room code separately so the path is clear.
- 4. Preserve the save owner Keep the original host for a loaded run while comparing world state.
- 5. Stop after one change Restore a router, VPN, mod, or device setting if the test is not useful.
Voice chat and controller checks
A working lobby does not prove that the local audio path or controller focus is working. Patch 2.04.a added a HUD indicator for muted push-to-talk or push-to-mute states. Use that visible state, the operating system input device, and a short fresh lobby test to separate a local setting from a network report. Do not disable all security or privacy controls as a generic fix.
For Continue Run, describe the exact focus behavior rather than saying the controller is broken. Note whether the menu opens, whether the selection moves, and whether the same action works once with a keyboard. That comparison gives a later fix a reproducible input state without claiming that the official posts already confirm a controller bug.
| Area | Observe | Record |
|---|---|---|
| Voice | Mute HUD indicator, input device, output device, push-to-talk state | Which player cannot hear or speak and whether a fresh lobby changes it |
| Controller | Menu focus, button mapping, wired or wireless connection | Whether keyboard input can select Continue Run once |
| Region | Host and joining player locations, Loading duration | The approximate time and whether a same-region test succeeds |
| Privacy | Room code and account names in screenshots | Redact them before sharing any evidence |
Quick answers
PEAK multiplayer troubleshooting FAQ
Why do I die when joining a PEAK friend?
Patches 2.5.a and 2.6.a fix named reconnect and Continue from save cases where a player returned dead. Update first, test a fresh lobby, and keep the original host for a loaded save.
Why do I reconnect as a skeleton?
An older save or reconnect path could load a player as a skeleton and then kill them. Patch 2.5.a addresses the named case. A current reproduction should include the exact save and host path.
Can PEAK non-host saves lose items?
Patch 2.6.a makes non-host saves more consistent but explicitly says non-host players do not receive complete world state in every path. Keep the original host and compare campfire objects before changing hosts.
How do I fix a PEAK room code Loading screen?
Generate a new code, use JOIN GAME, confirm the host is still present, and test the same region. Patches 2.5.a and 2.6.a fix named nonexistent-code and Loading cases; current reports remain evidence-dependent.
Did Patch 2.6.b fix the t-pose skeleton?
The official post says mid-game joins should no longer sometimes see a t-posing skeleton when the game loads. Repeat reports should include hardware, connection quality, and whether the join was late.
Does PEAK have public matchmaking?
The official Steam page confirms single-player and multiplayer or online co-op categories, but the sources checked here do not confirm an in-game public lobby browser or matchmaking queue. See the solo and public-lobbies guide for honest options.
Sources and limits
How to read this page
The issue matrix uses official Steam patch notes for named fixes. The official posts do not confirm a universal cause for every network or input symptom. Recent player reviews are used only to show demand for easier public play and solo options; they are not a diagnosis.