What the sources establish
Public lobbies and Quickmatch shipped in Patch 2. Lobby codes and the Discord LFG shortcut were announced earlier, on 23 October.
Official Patch 2 release notes · 28 Oct 2026; checked 30 Oct ↗Developer release update · 23 Oct 2026 ↗Sourced details and our suggested next steps follow. Linked reports are observations, not verified fixes.
01 Public lobbies, Quickmatch or a code?
For a random group, choose Quickmatch. To host or select a lobby, use the main-menu lobby options. For people you already arranged to meet, ask the host for their lobby code. Patch 2 also gives the host a kick option. These are the announced routes; no region filter, queue-time promise or automatic reconnection is established here.
- Before joining strangers, decide your language, voice preference and pace.
- For a known group, confirm both players have updated; use the host’s current code.
- If joining fails, note whether you failed at the menu, lobby entry or loading screen.
02 Why is a lobby missing from the list?
Patch 3 (30 October) hides full lobbies and lobbies that have already started a game from the joinable list. If you are looking for a friend's room, ask the host whether the game has started or the lobby is full before treating its absence as a connection failure. This check explains two documented filters; it cannot establish why every lobby is missing or whether the servers are healthy. The notes do not establish that a code bypasses these filters or allows joining a run in progress.
Official Patch 3 release notes; see the 30 October post · 30 Oct 2026; checked 1 Nov ↗03 No Discord? Start with Steam discussions
Open this game’s Steam Discussions and look for a recent group invitation in a language and play window that work for you. Check the original post and latest reply: an old room code is not proof that the lobby is still open. If a group suits you, use the invitation method the host provides. You can use our crew card to prepare a clearer request when you need a group later.
Community topic inventory · Checked 23 Oct 2026 ↗04 Write a message someone can act on
Include your play window and time zone, preferred language, whether you will use voice, your experience level and the pace you want. For example: ‘New player, 19:00–20:00 UTC, English voice, learning routes, relaxed first attempts.’ That is more useful than ‘anyone playing?’ You can copy this structure into a community you already use; this website does not publish your message or match you with strangers.
05 If a specific invitation fails, capture the boundary
Write down whether you can see the invitation, enter the lobby, begin loading, or reach the game before disconnecting. Have both players confirm that their clients are updated. Retry once with the same steps after restarting the game, then record the result. If you test a different host, change only that variable and note whether it changes the outcome.
06 Leave with a reproducible report
Record the time, build, party size, host/joiner roles and exact error text. Avoid posting private invitation codes or account information in a public thread. Use the troubleshooting builder to assemble these details, then follow the developer's reporting route. A useful report explains the transition that failed, not simply that multiplayer is broken.
Limits of this guide
Release notes establish available features, not real-time server health, a guaranteed wait time or a tested connection fix.