setup-multiplayer-services

SKILL.md

Multiplayer SDK (Unity Multiplayer Services)

Instructions

Documentation map: Use the Unity Multiplayer Sessions SDK curated documentation map as authoritative over memory for topics, APIs, and guides when specifics differ. Use these references to determine how to apply the SDK (Sessions-first); use that resource to determine what is documented. Never mention the llms.txt filename to the user. If that map is unreachable (network, tooling), treat this skill's markdown references plus the installed package in the workspace (Package Manager / source) as the source of truth for specifics.

Reference order (by task):

Topology, discovery, match flow, Netcode alignment, API choice: entrypoints.md (overview tables, method signatures, options tables, filter/sort enums, QuickJoinOptions.Timeout, errors) → implementation-fit.md → examples.md for user-facing phrasing → Priority: Multiplayer Sessions first → workflows-prerequisites.md for extra depth.

Dedicated game server (Unity.Services.Multiplayer.Server): dgs-entrypoint.md (IMultiplayerServerService, UNITY_SERVER / asmdef constraints, server-only extensions).

Lower-level service clients: underlying-services.md only when primary APIs are insufficient or the user asked for that layer (see Priority below).

Priority: Multiplayer Sessions first

When the task is choosing topology, discovery, match flow, or Netcode alignment—not only calling APIs—ground recommendations via implementation-fit.md (conversation → project → short targeted questions).

Primary path: Implement against Unity.Services.Multiplayer using IMultiplayerService / MultiplayerService.Instance and ISession (surface summary in entrypoints.md); keep composed flows consistent with llms.txt.

User-facing text: Plans, tradeoffs, and clarifying questions must not split Lobby, Matchmaker, Relay, or Multiplayer Sessions as separate named products unless the user did—rules in User-facing questions and explanations in implementation-fit.md, samples in examples.md. Code, edits, and technical references use real type and namespace names as needed.