← ClaudeAtlas

unity-live-serviceslisted

START HERE for any backend, online or monetisation request: accounts, cloud data, multiplayer, voice, purchases, ads or a third-party API. Routes to the API skill.
tipoLi5890/unity-dev-skills · ★ 2 · API & Backend · score 75
Install: claude install-skill tipoLi5890/unity-dev-skills
# unity-live-services — the parts that are not an API call > **A backend turns a game you ship into a service you run.** The API is the small part. The > decisions below are the ones that are painful to reverse after real players have data. ## Request → where to go This skill is the entry point for everything that leaves the device. It routes the call-by-call work to the API skill that owns it and keeps the decisions none of those APIs can make for you. | Request or symptom | Go to | |---|---| | Accounts, sign-in, cloud save, remote config, economy, leaderboards, cloud code, analytics — the calls | `unity-ugs` | | Adding any of those to a game that has none; dev and production data got mixed up | §1–§5 here, then `unity-ugs` | | "Peer-to-peer, listen server or dedicated?"; a cheater affected someone else; lobby and game disagree; a player lost signal | [`reference/multiplayer.md`](reference/multiplayer.md) | | Sessions, lobbies, matchmaking, relay, dedicated-server sessions — the calls | `unity-multiplayer-services` | | Voice or text chat channels, tokens, the participant roster | `unity-vivox` | | Voice chat broke another microphone feature; mute is not instant; works in two editors, not on two phones | [`reference/multiplayer.md`](reference/multiplayer.md) §3–§4 | | Netcode APIs — client prediction, sending input or turns, networked scene management | Out of scope for this plugin; the topology and authority they implement: [`reference/multiplayer.md`](reference/multipla