For the complete documentation index, see llms.txt. This page is also available as Markdown.

Launcher Builds

Manage launcher versions and distribution

What "Deploy the Launcher" means?

Deploying your Launcher means that it will be processed in the server to create your launcher executable and installer. Usually, a deploy is needed when Game Launcher Cloud releases a new launcher version or when you changed something critical about the Launcher (e.g. Launcher Icon, Splash Screen image). You decide when you want to update your launcher. However very old launchers will not be able to be used by your users. It's highly recommended to be up to date.

Launcher Deploy Warning

Build Configuration

Platform
Format
Size
Build Time

Windows

.exe installer

~50MB

3 min

macOS

.dmg / .pkg

~60MB

5 min

Linux

.AppImage

~55MB

6 min


Managing Builds

Launcher Active Build Selection

1

Select your Launcher in the sidebar

2

Deploy your launcher build

Deploy your launcher build by clicking in this button

3

Navigate to Launcher Builds

4

In the Launcher Active Build section

Click Change Active Build button

Select the latest deployed build and click Set as Active button

5

Test & Distribute to Players

For existing launchers: Now in your Launcher just click the refresh button and you will see the Download Launcher Update button For new users: Copy and share your permanent links to your users (Automatically updated each time you deploy a new launcher update).

Installer Wizard

Installs the launcher on the user's system with a setup wizard. Includes automatic shortcuts and uninstaller.

Portable ZIP

A standalone version that runs without installation. Just extract and run, no admin rights needed.

Download Formats

Each build provides two download formats:

Launcher Builds
Format
Description
Use Case

Windows Installer (.exe)

Full installation package

Recommended for distribution

Portable ZIP

Compressed executable

Quick testing, portable use

Persistent Download URLs

Distribution

The active build is automatically available at a persistent URL:

How It Works:

  1. You activate a new build (e.g., Build 42)

  2. Files automatically copied to /Latest/ folder

  3. Download URLs remain the same

  4. Users always get the active build

Benefits:

  • Single Download Link - Share one permanent URL

  • Always Current - Users download the active version automatically

  • Easy Sharing - Copy button makes distribution simple

  • CDN Powered - Fast global downloads via Cloudflare CDN

Copy to Clipboard

Use the Copy to Clipboard button for instant link sharing:

  • One-click copy for both Installer and ZIP links

  • Share links on your website, Discord, or social media

  • No need to manually construct URLs


Self-Update System

Learn More: Check out How the Launcher Self-Updates for a detailed explanation of configuration updates vs. launcher deploys.


Best Practices

✅ Test Before Set as the active build

Always test your launcher builds before placing it as the new launcher active build

✅ Version Numbers

Follow semantic versioning consistently

Last updated

Was this helpful?