Update to a new game version

Your fork is pinned to the version of the game it was created with. When Maketools publishes a new major version (new mechanics, reorganised content), the studio shows that an update is available. Updating is always your choice: nothing changes until you apply it.

Preview the update

Start with the preview. It shows your draft converted to the new version and warns you about:

• removed fields: content you customised that the new version no longer uses;
• added fields: new content, filled with default values, to review (and to rewrite in your source language if needed).

The preview changes nothing.

Apply the update

Applying converts the draft to the new version. Then:

• review the added fields and test the game;
• update your translations: an unchanged text keeps its translation, even if it moved; an added or changed text becomes "to translate";
• create a release and deploy it when ready.

Until you deploy a new release, players keep playing the currently deployed release with its original version. You can still roll back to a release made before the update.