Craft

Game sync

Every game is its own copy of a world, made from one version. That is what makes play safe: the GM can change files mid-game without touching the world, and you can keep building without breaking anyone's campaign. Sync moves changes between the two, in either direction. The story itself (messages, rolls, what happened) is never part of it.

Sync is in Get updates, in the Menu at the top left of the game screen. When the world has a newer version than the game, the menu shows a dot and the item is marked New.

Pulling updates

Brings a newer version of the world into the game. Only the game's owner can pull; anyone else in the game sees the dialog but can't apply it.

  • What you see: every version since the one the game last synced, newest first, each with its release notes, then one row per change.
  • Rows: files, file types, folders, music and settings, each with a checkbox. Each row can show its changes, as the game will have them.
  • Ticked for you: additions and changes. Deletions are left unticked, so a pull never quietly removes something from the game.
  • Result: the ticked changes are copied into the game's files. If the game is already on the newest version, the dialog says so.

See also: Conflicts, GM instructions in a sync.

Pushing changes back

Sends changes made inside a game back to the world, as a new version. Only the world's owner can push, from any game of the world they can open. The dialog then has two tabs, one to pull and one to push.

  • What you see: every change the game made since it last synced, ticked, with the same rows and conflicts as a pull. Changes the world made meanwhile stay as they are unless you tick them back.
  • Title and notes: the new version's, as when you create one.
  • Set as latest version: on (the default) publishes it; players see it and new games start from it. Off saves it in the version history without publishing it; promote it later.
  • Result: an ordinary version, like one made from the workspace. A push into a public world is reviewed like any public version.
  • The game itself doesn't change. Its synced version moves to the new one only when the game already has everything the world changed since; otherwise the game gets the world's other changes at its next pull.

A push compares against the world as it is in its editor, unpublished edits included, so a change both sides made is a conflict, not an overwrite.

See also: Releases.

Conflicts

A conflict is something both the game and the world changed since the game last synced. It is never applied silently.

  • On a pull, the game's version is kept unless you choose the world's.
  • On a push, the world's version is kept unless you choose the game's.
  • Each side's change can be shown next to what ticking the row does.
  • An added file that the other side already has its own copy of is a conflict too, left unticked.

A change both sides made the same way isn't listed. A file saved again with nothing different isn't a change.

Deletions

  • Files and music: listed, unticked. Tick one to delete it on the other side.
  • File types and folders: can't be deleted by sync. Delete them by hand in the game (or the world) if you want them gone.

What never syncs

These stay with each game or each world, in both directions:

  • Game start files: they only matter when a game is created, so neither a pull nor a push carries them.
  • The prelude: it plays in a game's lobby, so each game keeps its own.
  • The world's tags: they are for Discover, and each side keeps its own.
  • Pinned files (the world's default sidebar): they reach only games started after you publish them, and each game keeps its own.
  • First Steps: it guides people who clone the project, and a game has none.
  • Which GM runs the game: a sync never changes it for the world, and a game changes only by its own upgrade row on a pull.

GM instructions in a sync

The world's GM instructions, player options and tracker templates are merged one item at a time, not replaced. Each one is compared in three versions: the one the game last synced, the game's, and the world's.

  • Only the world changed it: it comes in, ticked, removals included.
  • Only the game changed it (a rule the player added or edited): it stays, listed so you can put the world's back.
  • Both changed it, in different parts (the trigger in the game, the text in the world): both changes apply, each with its own switch.
  • Both changed the same part: you choose; the game's is the default on a pull, the world's on a push.
  • The order of instructions and of player options is its own switch.

Each row can show what changed, and unticking every row leaves the game's rules as they were. A rule you leave unticked counts as the game's own from then on. A template change doesn't alter a tracker already running in the game. More on game-side rules: GM instructions in a game.

Moving a game to GM Harness 2

A game on the original GM that pulls a version published on GM Harness 2 sees one more row, GM Harness, V1 → V2. Taking it writes the story so far into GM Harness 2's memory and brings the world's GM instructions, and the game can't go back. While it does, no turn can be sent. Leave it unticked to stay on the original GM for now; it is offered again at the next pull. See Moving to GM Harness 2.