Craft

Publishing

What you build is a draft that only you and your editors see. Publishing is how it reaches anyone else. You create a version: a numbered, frozen copy of the whole project (v1, v2, v3 …). Players meet that version, never your draft, so you can keep building without breaking anyone's game. Separately, the project's visibility decides who can find it: only you, anyone with the link, or everyone on Discover.

How it is used

  • New games start from the latest version. That includes your own test games. Changes you haven't put in a version don't reach them. A world with no version yet starts games from the draft, so test games see your changes at once.
  • A game is its own copy. It keeps the version it started from. When you publish a newer one, the game's owner can pull it in, and you can send changes made in your own game back to the world. That is game sync.
  • Visibility is a separate switch. Creating a version doesn't make a world public, and making it public doesn't create a version. A public world appears on Discover only once it has a version.
  • Public worlds are reviewed. Each version that goes public is read against the content policy and given a rating: General, Mature or Explicit. Players filter Discover by it. A version with prohibited content is set back to private.
  • Worlds are played, systems are built on. A published world offers players a game. A published system offers creators a copy to build their own world on. Publishing works the same way for both.
  • A slice can be shared on its own. A package is a set of files and the file types they need, which other creators install into their own projects. See Packages.

Publishing a version

To create a version, click Create Version at the top right of the workspace. Give it a title and release notes: players see the notes when they are offered the update. The rest of the details (what a version holds, history, restore, roll back) are in Releases.

Visibility

Change visibility and cloning in the Share project dialog, in the menu beside Create Version.

In the app Stored as Who can see it
Private "private" Only the owner and the project's editors can see it.
Unlisted "unlisted" Anyone with the link can see it (and play a world), but it isn't listed on Discover.
Public "published" Listed on Discover once it has a version, and reviewed against the content policy.
  • Cloning lets other people copy a world into a project of their own. A world can turn it off. A system is always clonable, since that is how worlds are built on it.
  • A public world is listed on Discover once it has at least one version. Its tags, play format and content rating decide where it shows up and to whom.
  • A link works for unlisted and public worlds once they have a version. The world's page shows the published version.

The content review

When a version goes public (published while public, made public, or an older one promoted), Craft reads it against the content policy in the background, and publishing never waits for it. Private and unlisted versions aren't reviewed. The review gives the world its content rating, which only Craft sets and which affects only Discover, and a world with prohibited content is set to private. What each rating means and how to get a world reviewed again are in the content policy.

Read the result in the Discoverability tab of your world's settings. You can correct the tags and play format the review assigned (a tag can only be removed), but not the rating. You can't promote a prohibited version.

Doing it well

  • Create a version before a big change. Restoring a version is the only undo for the whole project at once, and it works on private projects too.
  • Write release notes for players. Say what changed in their terms: "the harbor district is new, the rogue class was rebalanced". They read them when deciding whether to update a game in progress.
  • Look over the change summary before you publish. It lists every file, file type, folder and setting changed since the last version. An accidental deletion is easy to spot there and hard to undo later.
  • Give players a game start. Without one, players pick from every character in the world and the game opens in no place, with no map. See Game starts.
  • Test in your own game, then push back. Play shows what's missing. Fix it in the game and send it back as a version (see game sync).
  • Publish less with a package. A spell list or a bestiary that other worlds could use belongs in a package, not in a world people clone just to take it.

Mistakes

  • Public, but no version. The world is public and still not on Discover. Create a version.
  • A version, but private. Your games use it, but nobody else can see it.
  • Expecting games to change on their own. Running games keep their version until their owner pulls the update.
  • Restoring over unpublished work. Restore replaces the draft with the older version, and edits since the last version are lost.
  • Promoting to roll back on a private world. Promoting an older version also makes the world public. Change visibility back afterwards if that isn't what you want.
  • Deleting the only version. The world has nothing to start games from, and it is set back to private.

Reference

  • Game sync: How a game pulls in a newer version of its world, how the world's owner pushes a game's changes back, and what each one carries.
  • Packages: Sharing a slice of a project (files and the file types they need) for other creators to install, and how installs, updates and uninstalls work.
  • Releases: What a version of a project holds, and everything you can do with one, from creating it to restoring, promoting and deleting it.