Section 10. Publishing and troubleshooting
How-to
Republish and the primary build
To update the game at the public URL after you change it, publish again and make that build the primary build. For your first publish, see Publish your game.
What the primary build is
Each publish adds a row to Build history. The one row marked PRIMARY is the primary build, and the public URL (…/p/<project ID>/) always shows the primary build.
Each build also has its own URL (…/b/<build ID>/). Click the open-in-new-window icon on a row to open that build. The URL to give other people is the /p/ URL, which points to the primary build.
Publish again
- Make your changes and check them with ▶ Launch.
- In Publish / Download → Publish, enter a higher Version (for example,
1.0.1after1.0.0), describe your changes in Release Notes, and click Publish. - Wait until the new row shows a green check.
- On the new row, click
…→ Set Primary Build. With no confirmation dialog, the row is marked PRIMARY right away, and the Primary build field at the top of the window switches to that build. This step is what makes the public URL show the new build (1 run). - Reload the public URL and play to check that the updated game appears. In our tests, publishing took 9 to 90 seconds (3 successful runs).
Go back to an earlier build
If the new build you published has a problem, click … → Set Primary Build on the earlier build's row. Reload the public URL and the earlier build appears (1 run). Only the primary build changes; the project in the editor stays the same.