Deploy and roll back

Deploy

Deploying makes a release the version played at /{your-organisation}/{fork}. Choose a release in the list and select Deploy. Players who start a session after that moment get the new version; sessions already in progress finish with the version they started.

Only people allowed to play can open the game. Players choose among the languages of the deployed release: the language of the site if the release offers it, otherwise the source language, and the Game language selector when there are several. See Translate a fork.

On the Free plan, one game can be deployed at a time; redeploying it is always possible. See Plan limits.

Withdraw the deployment

Withdraw the deployment (on the deployed release) takes the game offline: its address stops answering, sessions in progress finish with their version. The draft, the releases and the access rules are kept; deploy a release again to put the game back online. Withdrawing frees the fork's private game slot in your plan (see Who can play), and is recorded in the audit log.

Roll back

To go back, deploy an older release. The previous content, with its languages, is back immediately, and the action is recorded as a rollback in the audit log. You can deploy the newer release again at any time: releases are never lost.

When a fork cannot be played

The address answers "not found" when:

• no release has been deployed yet;
• the fork has been archived;
• its deployment has been withdrawn;
• the organisation or the slug does not exist (check the address after a rename).

A private game suspended by the plan limit (after moving to a lower plan, see Who can play and Plan limits) answers "This game is temporarily unavailable" to players allowed to open it. The fork list and its Releases page show it as "Suspended (plan limit)".

Suspension by moderation

Any player can report a game (illegal content, phishing, hate, exposed personal data…). The Maketools moderation team reviews every report and may suspend the game. The owners and admins of the organisation then receive an email giving the reason and the explanation.

A game suspended by moderation:

• answers "This game is temporarily unavailable" to players, with no other detail, and leaves their home page; its leaderboard is no longer shown;
• shows the "Suspended (moderation)" badge in the studio, and a banner on its pages recalls the date, the reason and the contact;
• can still be edited: you can fix its content, publish and deploy a release, but deploying again does not lift the suspension.

To contest the decision, or to ask for the game to be restored once fixed, write to the address given in the email and on the banner, with the name of the game. Once the suspension is lifted, the organisation is told by email and the game can be played again if it is deployed.