Release history
Every upload receives a permanent release number. Add a version label such as 1.4.2 and internal notes before uploading. In Builds & releases:
- Live is the release players launch.
- Candidate is the upload being checked or reviewed.
Uploading never changes the live release. A candidate replaces it only after checks, review and activation.
Roll back
To restore a release that was live before, resolve any pending candidate, choose Rollback in the release history and confirm compatibility with current saved data. PEERLESS rechecks ownership, the current live release and upload checks, then switches the client and any paired server together. Managed rollback also needs a retained server image that starts successfully.
Existing managed matches can finish on the old release while new launches use the restored one. Rollback restores code, not database contents or player saves.
Updating the SDK
Releases are immutable: each keeps the SDK files it was built with. To adopt a newer SDK, rebuild your game with the new peerless-sdk.js (and adapter files) and upload a new release.