Launcher Builds

Manage launcher versions and distribution

Build, version, and distribute your custom launcher to players. 📦


Overview

Manage multiple launcher versions, track deployments, and control distribution.

spinner

Build Process

Creating a Build

spinner

Build Time:

  • With Installer: ~7-10 minutes

  • No Installer: ~3-5 minutes

circle-info

Auto-build: Enable automatic builds when you change appearance or settings!


Version Management

Semantic Versioning

Launcher versions follow semantic versioning:

Examples:

  • 1.0.0 - Initial release

  • 1.1.0 - Added Discord RPC

  • 1.1.1 - Fixed crash bug

  • 2.0.0 - Complete UI overhaul

spinner

Build Types

Production Builds

  • ✅ Fully optimized

  • ✅ Code signed

  • ✅ Auto-update enabled

  • ✅ Analytics included

  • Secure

Use for:

  • Official releases

  • Public distribution

  • Stable versions

Beta Builds

  • Quick builds

  • Not code signed

  • ✅ Debug logging

  • ✅ Fast iteration

Use for:

  • Testing

  • Beta testers

  • Pre-release

Development Builds

  • ⚡ Fastest builds

  • ❌ No optimization

  • ✅ Full debug info

  • 🧪 Internal only

Use for:

  • Local testing

  • Development

  • Debugging


Platform-Specific Builds

Build Configuration

Platform
Format
Size
Build Time

Windows

.exe installer

~50MB

5 min

macOS

.dmg / .pkg

~60MB

7 min

Linux

.AppImage

~55MB

5 min

spinner

Managing Builds

Builds Tab

Access the Builds Tab in your launcher settings to manage all launcher versions:

DashboardLaunchers → Select Launcher → Builds Tab

circle-info

Location: Find build management in the dedicated Builds tab, separate from general launcher settings.

Active Build Selection

circle-exclamation

Setting an Active Build:

  1. Navigate to the Builds Tab

  2. Locate the build you want to activate

  3. Click Set as Active

  4. Users will now download this version

Safety Features:

  • Cannot delete the currently active build

  • ✅ Test builds before activating them

  • View complete build history

  • Roll back to previous versions if needed

Download Formats

Each build provides two download formats:

Format
Description
Use Case

Windows Installer (.exe)

Full installation package

Recommended for distribution

Portable ZIP

Compressed executable

Quick testing, portable use

Build Metrics

View detailed metrics for each build:

  • ⏱️ Executable ZIP Upload Duration - Time to upload the ZIP file

  • ⏱️ Installer Upload Duration - Time to upload the installer

  • ⏱️ Total Build Time - Complete build process duration

  • 📦 File Sizes - Size of each download format

  • ⚙️ Configuration - Build settings and parameters

Visual Preview

See your launcher's branding directly in the build list:

  • Launcher Icon - App icon preview

  • Splash Screen - Loading screen preview


Distribution

Persistent Download URLs

circle-check

Latest Folder System:

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


Auto-Update System

How It Works

spinner

Update Process:

  1. 🔍 Launcher checks version on start

  2. 📥 Download new version if available

  3. ✅ Verify digital signature

  4. 📦 Install update

  5. 🔄 Restart launcher automatically

circle-check
circle-info

Learn More: Check out How Updates Work for a detailed explanation of configuration updates vs. launcher deploys.


Best Practices

✅ Test Before Release

Always test beta builds before production

✅ Version Numbers

Follow semantic versioning consistently

✅ Changelog

Document changes for each version

✅ Monitor Analytics

Track adoption and issues post-release


Next Steps


circle-check

Last updated

Was this helpful?