Unity multiplayer architecture
Plans Unity multiplayer authority, spawning and connection lifecycles. Separates being connected from being authenticated, admitted and ready to play, with explicit rules for late joining.
unity-multiplayer-networking
Agents using this skill
When is it useful?
Use it when adding networking or integrating an existing stack with spawning, ownership and late joining.
What does it help you do?
- Assigns input, simulation, spawning and persistence authority.
- Separates transport, authentication, membership and scene readiness.
- Defines object lifetime, message ordering and late-join reconstruction.
Try asking this
Plan a four-player Unity arena using the installed networking stack. Define who creates characters, validates actions and owns persistent results. Walk through a late join during a round and a scene transition; the client should receive current state before gaining control, with no duplicate character after reconnecting.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Multiplayer Networking Contracts
Inspect Unity version, installed netcode/transport packages, topology, platforms and hosting constraints. Preserve the current stack; GameObjects, Entities and distributed-authority solutions have different contracts.
- Record who owns input, simulation, spawning, persistent state and presentation. Separate a client request from an accepted authoritative result.
- Define network object identity, ownership transfer, visibility and despawn behavior. Clear callbacks and pending actions when objects disconnect, unload or return to a pool.
- Distinguish connection, authentication, session membership, player spawn and scene readiness. Each can succeed or fail independently; avoid reporting readiness from transport connection alone.
- Use supported package APIs and serialization types. Read installed package docs before choosing RPC attributes, network variables or prediction features; version-2 examples are not universal across releases.
- State delivery, ordering, frequency and payload limits for each message. Keep continuous state separate from one-shot events and define late-join reconstruction.
- Check multiple participants under representative latency/loss, reconnect and server/host termination. Label local-host evidence and report what actually ran.
References: Unity NGO and Gaffer on Games. Select package documentation matching the project. Cloud setup, paid servers and public exposure require the user's authorization.
Included files 2
LICENSE.txtSKILL.md