Game Server Hosting prompts you to upload your build files when you create a build. If you’re using a direct file upload, the files should be a loose set of unarchived (unzipped) files. The build will not work if it’s zipped into an archive.
Before you can use your build, you must create it into a release, which is a version of your build that’s ready to release to servers to run your game or application. The first version you create is Release 1.
The next time you update your build and create a new version, it will be Release 2. You can only use the latest version of a build.
When you update a build, it triggers a number of build installs. The number of installs depends on the number of servers using the build.
There are two methods to update a build called rolloutThe process of "rolling out" an updated game image to all the machines in a fleet. modes: progressive and forced.
A progressive rollout is a method of deploying a build update where you update servers only when they are empty. Game Server Hosting waits for your matchmakerA multiplayer networking feature in games that groups players into a game session. to deallocate the server if it has any connected playersConcurrently connected users (CCU) is the number of players simultaneously connected to a fleet, region, or server at a given point in time..
A forced rollout is a method of deploying a build update where you force servers to update even if the server has connected players. If players are connected when you start a forced rollout, Game Server Hosting kicks the players from the server.