Precaution restart

Follow these steps if:

• snapshots are failing for an extended period
• an alert is fired based on deployment metrics

1. Around 20 minutes before you remove players from the game, stop players from joining the game.

   If you’re using your own authentication server, you’ll need to set up your own way of stopping players from joining the game.

2. Create a worker flag to let players know that you’re going to stop the game:

   1. In the Console, open the deployment and go to the Worker flags tab.
   2. From the drop-down list, select the worker type that you registered the callback for, and add a worker flag with the same name as you used when setting up the callback.
   3. Set the flag’s value. This is handled by the callback you set up above. For example, you could set the value to be a message to display to players.
   4. Click Submit. This sends the flag update to the worker.

3. Five minutes before you remove the players from the game, let them know by updating the worker flag.

4. Remove all the players from the game.

   You can use system entities to do this. For details, see Interacting with client-worker entities.

5. Take a snapshot of the deployment without players in it:

   spatial cloud history snapshot create <deployment_name>
   

   1. Download this snapshot: powershell spatial project history snapshot download <deployment_name> latest <snapshot_file> where snapshot_file is the file name you want to give the snapshot.

6. There may be elements of the game world that you want to edit or remove before restarting, such as battle debris or timestamps. To do this, you’ll probably need to convert the snapshot into a text file:

   spatial project history snapshot convert --input=<snapshot_file> --output=<text_file> --input-format=binary --output-format=text
   

   When you’ve finished editing the file, convert it back:

   spatial project history snapshot convert --input=<text_file> --output=<snapshot_file> --input-format=text --output-format=binary
   

7. From your project folder, run a cloud deployment using the snapshot:

   spatial cloud launch <assembly_name> <launch_config> <deployment_name> --tags=<comma-separated list of tags> --snapshot=<snapshot_file>
   

   1. Validate the deployment from the Console.

   2. On the Advanced tab, confirm that all nodes are healthy:

   3. In the World view, check you have the right number of different types of worker:

   It’s also a good idea to run an end-to-end connection test (either manually or automatically) in which a client connects to the game and performs an action (for example, jumps and shoots a wall down). We don’t provide anything out-of-the-box for automating these steps, so get in touch if you’d like help with this.

   1. Let your community know they can join the game again.

Search results