Publishing

Getting an experience to players goes build, release, then visibility.

Builds

A build is an upload of one world's files. Ember checks it the way Glowstone Create does: a build with errors is rejected, with the same diagnostics you'd see in the editor, and never goes live. A build that passes is ready. Builds never change once uploaded, so you can always go back to one.

Releases

Releasing a ready build makes it the world's live build: new servers start on it straight away. Rolling back is releasing an earlier build. The dashboard shows each world's live build and its release history.

Going public

Experiences start private: only their organisation sees them. Owners and admins can make one unlisted, playable by anyone with the link, from its settings in the dashboard, and back again whenever they like.

When yours is ready for everyone, open it in the dashboard and choose Request public on its Publishing card. Add a note for the reviewer if there's something they should know, like where to start or what changed since last time. Glowstone staff look it over, and it stays as it is until they do; you can withdraw the request while it waits.

If they approve it, it's listed for every player to find. If they don't, the Publishing card shows their note, and you can ask again once you've made changes. A public experience can go back to private or unlisted from its settings at any time; going public again means another request. While an experience is public, staff may also review its releases.

Uploading builds from Glowstone Create is on its way. Until then, you can make experiences and their worlds in the dashboard and see the builds and releases they already have.