setup-multiplayer-services — Claude Code skill: Unity multiplayer

What setup-multiplayer-services does

This skill sets the order in which the agent works with Unity Multiplayer Services. The default route runs through Unity.Services.Multiplayer, using IMultiplayerService and ISession. Lower-level clients such as Unity.Services.Lobbies, Unity.Services.Matchmaker and Unity.Services.Relay come into play only when the main API cannot cover the task, or when the user names those namespaces directly.

Under the hood sits a folder of references. One covers the API surface with option tables and method signatures, another helps pick an implementation for the task, a third gives sample wording for questions to the user. A dedicated file handles dedicated servers: Unity.Services.Multiplayer.Server, IMultiplayerServerService, UNITY_SERVER and asmdef constraints. Package and cloud prerequisites are laid out in tables by workflow. Where the model's memory conflicts with the docs, the skill says to trust Unity's documentation map, and if that map is out of reach, the skill's own markdown plus the installed package in the project.

One rule concerns how the agent talks to you. Plans and clarifying questions keep Lobby, Matchmaker, Relay and Sessions together unless you separated them yourself. In code, real type and namespace names are used. Note that the whole thing assumes the Multiplayer Sessions package is already in the project and the cloud prerequisites are met; without them the guidance has nothing to attach to, so the skill starts by checking what is installed.