← ClaudeAtlas

unity-multiplayer-serviceslisted

Sessions API: create/join, join codes, matchmaking, relay, host migration, dedicated servers.
tipoLi5890/unity-dev-skills · ★ 2 · API & Backend · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-multiplayer-services — one session API, and the layers under it you should not reach for > **`MultiplayerService.Instance` and `ISession` cover the whole flow** — create, find, join, > connect, reconnect, migrate the host, tear down. Lobby, Matchmaker and Relay are what that flow > is *made of*, not three products to assemble by hand. Code that drops to one of those clients > directly takes on a second lifecycle to keep in step with the session's, and the composed calls > that were doing that work for it stop being usable. ## Symptom → where to look | Symptom | Go to | |---|---| | "How do players get into a game together?" — create and join, join codes, quick join | §1, then [`reference/session-api.md`](reference/session-api.md) | | "Should this use Lobby, or Relay, or Matchmaker?"; code reaching straight for `Unity.Services.Lobbies` / `Matchmaker` / `Relay` | §2 — settle the requirement first; all three are below one API | | Netcode for GameObjects on a session's network; players join, but nothing is networked | §3 — the network is a session option, not a second start call | | Two gameplay netcode packages in `manifest.json` | §3 — pick one | | Server build breaks on `Unity.Services.Multiplayer.Server` types | §5 | | Ticket matchmaking into a playable match returns nothing — the queue was never deployed | §4 — the queue/environment does not exist yet | | Players drain out of a running dedicated match and never refill | §5 backfill | | A room / party / lobby list: