Channels and publishing
Live, beta and custom channels; publishing and rolling back.
A release is one uploaded build of a game for one platform. Releases start as drafts; publishing puts one on a channel, and players on that channel get it.
Channels#
| Channel | Who uses it | Plans |
|---|---|---|
| Live | Everyone | Every plan |
| Beta | Players who choose Beta in the launcher | Starter and up |
| Custom channels (any short name) | For example qa or press | Pro and up |
Players switch channels in the launcher, when the game has more than one. Each channel has its own current release.
Publish a release#
- Upload a build from the plugin. It appears on the game's page as a draft.
- Choose Publish next to it.
Publishing needs a role that can publish (owner, admin or developer) and a confirmed email. Players' launchers see the new release the next time they open the game in the launcher, and offer Update.
Roll back#
On the game's page, choose Roll back to this next to an earlier published release to make it current again. Players update to it the same way they update forward: only what differs is downloaded.
A rollback is a new step forward in your release history, so a launcher can tell a real rollback from an attempt to replay an old release.
Keeping a release current#
Your live release is re-confirmed by Deltaship every few hours. You do not need to do anything; the game's page shows when the next refresh is due.