Games, builds and releases

Game definitions

A game definition is a JSON document (schema version 1) that tells the platform how to run your server. It must declare: schemaVersion, gameName, executable, args, ports, configPaths, savePaths, logPaths, stopStrategy, console, health, resources and install.

• Console. How commands reach the server: stdin, rcon, telnet and none.
• Stopping. How the server is asked to stop: ctrl-break, stdin, rcon and signal.
• Health. How the platform decides the server is up: port, command, http, console-marker and rcon-status.

Definitions also name the server's ports, its configuration, save and log paths, and any resource limits it should run under.

A definition moves through draft, verified, active and archived. Versions of a definition are never edited in place: a change is a new version, and a definition can be cloned as the start of another.

Verify checks a definition by deploying a throwaway server from it and deleting that server afterwards, so problems surface before a real group uses it.

Adding builds

• Upload. Upload a build archive from the browser; uploads are resumable. Accepted formats: zip, tar, tar.gz and tar.zst. Every archive is checked for unsafe contents and scanned for malware, and one that fails either check, or cannot be scanned, is refused.
• Steam. Install builds from Steam with your studio's own Steam credentials, stored with your organization. When Steam asks for a Steam Guard code, you enter it in the browser.

For very large builds, contact us before you upload.

Versions

Each build is a version of your game, with a status of staging, available, deprecated and archived. Each host reports which build it actually has on disk, and the platform treats that report as the truth.

• Pin a group to a version.
• Promote a version from one group to another, for example from a test group to production.
• Roll back a group to its previous version.

Rollouts

A rollout moves a group to a new version using one of: all-at-once and rolling. A rolling rollout updates between 1 and 8 servers at a time.

A rollout pauses when a server fails to update. You can then resume it or cancel it.