Craft

Releases

A release, or version, is a frozen copy of the whole project. The project keeps a numbered list of them, and one is the published version: the one players see and new games start from. Usually that is the newest.

Creating a version

Copies the project as it is now into a new numbered version, and makes it the published one.

Part What it is
Title Optional. Without one it is the project's name and the number: "Ashfall v4".
Release notes Optional. Shown in the version history, on release previews and in the update players are offered.
Number Given for you, one more than the last: v1, v2, v3 …
Make public Optional. Makes the project public as well. Once a project is public, every new version is live at once.

To create one, click Create Version at the top right of the workspace.

Limits: only the project's owner can create a version; editors can't. Two versions can't be created at the same moment, so one waits or is refused until the other is done. A project restricted for its content can still create versions (people with the link get them), but can't be made public.

The form shows a summary of every change since the last version. Click it for the full list. Saving is turned off when nothing changed, and when the project has no game start type the form offers to create one.

See also: What a version holds, Starting a game with unpublished changes.

What a version holds

Everything a game needs, frozen as it was:

  • every file, file type and folder, with the links between files;
  • the music;
  • the project settings: the page and gallery, the art direction, the Game Master's name, picture and voice, its GM instructions, player options and tracker templates, the prelude, the handbooks, First Steps, the tags and the root map;
  • the files new games start with pinned in the side panel (kept with the version, though they are not a project setting).

Later edits to the draft don't change a version.

See also: Project settings.

Viewing a version

Opens an older version read-only, as it was, to compare or copy from. Nothing changes.

Versions are listed in Version History, in the menu beside Create Version.

Restoring a version

Replaces the draft with an older version. It is the undo for the whole project at once.

  • Edits since then are lost. Anything not in a version is replaced, with no way back. Create a version of the draft first if you might want it.
  • Settings come back too.
  • It doesn't publish. Players still get the published version until you create a new one.
  • Large projects take a while to restore.

See also: File versions, for undoing one file.

Promoting a version

Makes an older version the published one again, without touching the draft. Use it to roll back a version that shipped broken.

  • It also makes the project public, unless Craft has restricted or delisted it. On a private or unlisted world, change visibility back afterwards if you want it to stay that way.
  • New games start from it, and a public world's page shows it.
  • A public promote is reviewed, like a new version. A version the review found prohibited can't be promoted: publish a corrected one.

Deleting a version

Removes a version and its frozen copy for good. It can't be undone.

  • Deleting the published version makes the newest remaining one published.
  • Deleting the last version leaves nothing to start games from, and sets the project to private.

Starting a game with unpublished changes

New games, your test games included, start from the published version. When you start one while the draft has changes the version doesn't, you are asked first: create a version, or start on the published one anyway. A project with no version at all starts games from the draft.

How long versions are kept

Old versions thin out on their own: everything from the last 30 days is kept, then one a week up to six months, then one a month. The first version, the published one and any version a game started from or last synced with are always kept.