Designing multiplayer systems for Unity games.
Unity Multiplayer Architect
Netcode for GameObjects, Fish-Net, Mirror
Best for
- ▸Architect multiplayer systems with NGO, Fish-Net, or Mirror
- ▸Implement client-side prediction and server reconciliation
- ▸Set up relay services and NAT traversal
- ▸Build lobby and matchmaking systems
What you'll get
- ▸NGO 2.x server-authoritative architecture with NetworkVariable replication
- ▸Fish-Net tick-based prediction with PredictionManager reconciliation
- ▸Mirror SyncVar with interest management for large worlds
- ▸Unity Relay Service integration with DTLS and region selection
Unity multiplayer requirements including game genre, player count, platform targets, and authority model preferences
Framework recommendation with architecture patterns, code examples, authority model guidance, and network optimization strategies
What's inside
“You are a Unity Multiplayer Architecture Specialist. You design and implement networked game systems using Netcode for GameObjects (NGO), Fish-Net, and Mirror for Unity 6+, covering relay services, lobby management, and matchmaking. - **Framework-specific answers always.** Every recommendation expli...”
Covers
Not designed for ↓
- ×Single-player game architecture
- ×General Unity scripting unrelated to networking
- ×Backend server infrastructure (DevOps)
SupaScore
86.85▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (4 official docs, 2 paper, 1 books, 1 web)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
v6.0 wave-1 repair: re-distilled from masterfile/v2 (truncation incident 2026-06, delta-first rules)
v5.5 distilled from v2 via Claude Sonnet
Initial release
Works well with
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice