Big Walk

Big Walk Crossplay Join Code Not Connecting Fix

Step-by-step fix for Big Walk crossplay "couldn't connect" errors between PC, PS5, and Switch. The host-in-world rule, clock sync, version matching, and full restart sequence that actually work.

Connection fix PC / PS5 / Switch 5 min fix

Join code says "couldn't connect" across platforms

Friends share a join code but the connection fails or times out. This happens most often with PC + PS5 + Switch crossplay. The fix is almost never "crossplay is broken" - it is one of four specific causes, and the first one below solves most cases.
Steam (PC/Mac) PS5 Switch 2

The host must be fully loaded into the world

The single most common cause: joiners enter the code while the host is still on the main menu or Host Game screen. The code only works once the host has fully loaded into the world with their character visible. Multiple PC + PS5 groups fixed it instantly after applying this rule.
1Host selects Host Game, sets player count and an optional password, then starts the session.
2Host waits until the character is loaded in the world - not the loading screen, not the lobby, the actual playable area.
3Host opens Session Details (in-game menu) and reads the fresh Join Code at the bottom-left.
4Only now do joiners enter the code. Join Game > enter code at the top of the screen.
If the host generated the code before loading into the world, that code may be stale. Have the host re-open Session Details after loading in and share the new code.

Full fix sequence (in order)

1Confirm Crossplay is enabled in Settings on every device. It should be on by default, but verify - one toggle off blocks all cross-platform joins.
2Sync the system clock and date on every device. Especially common on Switch 2. An incorrect or unsynced date stops joining completely. Turn on automatic time sync if available. Multiple players fixed persistent "couldn't connect" errors just by correcting the date.
3Verify version compatibility. Only the first two version numbers need to match (e.g. 1.4.x works across platforms). Switch 2 has lagged behind PC updates in some reports - if Switch is on 1.4.5 and PC is on 1.4.7, the connection is blocked until both update.
4Completely close Big Walk on every device - not just returning to the menu. Fully quit the application.
5If still failing, fully reboot each device - not sleep/rest mode, a real power cycle. Then relaunch Big Walk and retry the host-in-world sequence above.
6Host watches the lower-left of their screen for connection warnings while joiners attempt to connect. These messages often pinpoint the cause.

Choices that affect connection

Same platform or crossplay?

Same-platform friends can often appear in the in-game friends list automatically once the host is in-world. Crossplay (PC, PS5, Switch) almost always needs the Join Code - friend-list invites do not work across platforms.

Set a password?

Yes. Codes are discoverable and community reports include random people joining by trying codes. Set a password in Session Details to keep the session private.

Who hosts?

The host owns the save. Stick with the same host for continued progress. If the host's device has connection issues, try swapping hosts as a test - but progress will not transfer.

Switch player can't connect?

Check the Switch system date first - this is the most cited Switch-specific fix. Then verify the game version is not behind PC/PS5, as Switch updates have lagged in some patches.

Mistakes to avoid

XJoining while the host is still on the main menu. The number one cause. Wait until the host is fully in-world.
XUsing a code generated before the host loaded in. Stale codes fail. Re-share a fresh code from Session Details after loading.
XIgnoring the system clock on Switch. Wrong date blocks all joins. Fix the clock before anything else on Switch.
XOnly returning to menu instead of fully closing the game. A soft quit does not clear the connection state. Fully close and relaunch.
XAssuming crossplay is broken when versions mismatch. Switch has lagged behind PC updates in some patches. Check that the first two version numbers match.
XLeaving the session open without a password. Random players have joined open codes in community reports. Always set a password.