# Build Live Game

Builds and operates a live game's backend with Unity Gaming Services.

- Repository: https://github.com/Unity-Technologies/skills (1197 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-10-30
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Unity-Technologies/skills --skill build-live-game -g -a claude-code -y`
Codex: `npx skills add Unity-Technologies/skills --skill build-live-game -g -a codex -y`
Cursor: `npx skills add Unity-Technologies/skills --skill build-live-game -g -a cursor -y`
Gemini CLI: `npx skills add Unity-Technologies/skills --skill build-live-game -g -a gemini-cli -y`

## Description

Builds and operates a live game's backend with Unity Gaming Services. Make sure to use this skill when the user wants trusted server-side game logic, player progress, remote configuration, sign-in, achievements, battle passes or leaderboards.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Build a Live Game With Unity Gaming Services

## Before You Start

1. Read the Editor version from `ProjectSettings/ProjectVersion.txt` and the installed UGS package versions from `Packages/packages-lock.json`. Pick the steps below that match (for example `.ccmu` or `.ccmr` modules), because the right workflow depends on the Editor and package versions.
2. Check whether the project is linked to a Unity project ID and environment (**Edit > Project Settings > Services**), and ask the user to link it if it is not.
3. Create a restore point you can roll back to if your changes fail: commit the project in version control. If there is no version control, copy the project folder instead.
4. Before you go forward with a workflow or diagnosis, open and read the documentation pages for the service you will use (see [Documentation Map](#documentation-map)) and the matching file under `references/`, and name the pages you read in your response. This is because your training knowledge about Unity Gaming Services might be out of date, incorrect, or for the wrong package version.
5. Do only what's asked. Don't change unrelated assets or files. Avoid long explanations.
6. When you change runtime behaviour, add `Debug.Log` lines at the points you need to verify (sign-in complete, module call returned, config fetched). You read them in Play mode during [Validation](#validation).

## Glossary

The rest: https://github.com/Unity-Technologies/skills/blob/HEAD/skills/build-live-game/SKILL.md