Updating a live game
Pe această pagină
Updating a live game
Games are never frozen. You can upload a new build, change the listing text or swap artwork at any time. What happens next depends on the stage your game is in.
| Stage | New build | Artwork and listing |
|---|---|---|
| Draft | Replaces the active build at once. | Edit freely. |
| In review | Locked. Withdraw the submission to edit, then submit again. | Locked. |
| Basic launch | Goes live right after it passes the validator. | Artwork is staged and reviewed; see below. |
| Full launch | Waits for a reviewer, then replaces the live version. | Artwork is staged and reviewed. |
Shipping a new build#
- Make the change locally and test it in local mode and the Preview tool.
- In the developer console open the game, go to the Build step and upload the new zip. The validator runs exactly as for the first upload and shows every problem with the offending path.
- Run Preview on the new build (ads are on there) and tick through the checklist.
- In full launch, submit the update and add a note for the reviewer that says what changed and where to see it. Short, specific notes get faster decisions.
Keep the index.html path stable and every asset path relative. A build that only changes a few files still needs to be a complete zip.
What a reviewer looks at in an update#
Updates are re-validated automatically and, for live games, re-reviewed when they change gameplay, ads or monetisation. A review of an update focuses on what changed, but a rule break anywhere in the build can still lead to a request for changes or, in serious cases, removal. Re-read the requirements checklist when you add ads, accounts, multiplayer or external links.
Saved data across versions#
Players keep their cloud save when you update. Plan for old saves meeting new code:
- Store a
versionnumber in your save and migrate on load. - Ignore keys you no longer use instead of deleting them.
- Never rename a key without reading the old one first.
Changing artwork#
Covers and preview videos are part of the listing and go through their own review. Stage the new files, submit them as one artwork change, or compare versions first with an artwork experiment. Specs are on covers and videos.
Rolling back#
If an update breaks something, upload the previous build again from your own source control and submit it. In basic launch it is live as soon as it validates. In full launch, say in the reviewer note that it is a rollback. Test updates in the Preview tool before you submit so you rarely need this.
Telling players#
Put a short "what is new" line in the game or on your community page. The portal does not send patch notes to players on your behalf.