How the Launcher Self-Updates
Understanding how launcher and configuration updates work
Learn how different types of updates are delivered to your players and when a launcher rebuild is required.
How Updates Work
When you save your launcher configuration:
When you save your launcher configuration, every user gets the new changes as soon as they open the launcher or press the Refresh button.
When the launcher starts, it automatically checks for updates. If a new version is available, a button appears at the top so the user can download it.
When you publish a new build for an app:
The launcher compares the build the player has installed against the build published for the environment they are on, and starts the update when the two differ.
That check runs when they open the launcher, select the app, switch environments, or press Refresh.
Each environment is checked on its own, so a build published to a testing environment reaches testers on their next switch to it.
About forced updates:
The platform enforces a global minimum launcher version for security and compatibility.
If a player's launcher version is older than the minimum required version, they must update before accessing the platform.
This ensures all users benefit from the latest performance improvements, security patches, and bug fixes.
Future versions will allow developers to set custom minimum version requirements for their launchers.
Understanding "Launcher Deploy" vs. Regular Customization Updates
It's important to clarify what requires a Launcher Deploy and what doesn't:
A Launcher Deploy is ONLY needed when:
You change the Launcher Icon
You change the Launcher Splash Art
Game Launcher Cloud releases a new internal update of the launcher
A Launcher Deploy is NOT needed when:
✅ You update App customization
✅ You update Launcher customization
✅ All these changes are applied instantly and the launcher fetches them automatically
Next Steps
Last updated