Launcher Settings

Configure launcher behavior and advanced options

Fine-tune your launcher's behavior, features, and performance. ⚙️

---

General Settings

Basic Configuration

Setting	Description	Default
Launcher Title	Display name in title bar	Game Launcher

Control Panel

Launcher Status Control

Manage your launcher's availability and communicate status to players.

Settings:

Setting	Description	Default
Enable Launcher	Enable or disable the launcher completely	✅ true
Maintenance Mode	Put launcher in maintenance mode	❌ false
Alert Message	Display custom message to all users	Empty

How It Works:

• Enabled (Enable Launcher: enabled) - Launcher functions normally, users can access all features

• Maintenance Mode (Maintenance Mode: enabled) - Launcher shows maintenance notice to users

• Disabled (Enable Launcher: disabled) - Launcher access is blocked completely

• Alert Message - Custom banner message displayed to all users

Use Cases:

• Maintenance Mode - Display "Server under maintenance" during backend updates

• Alert Message - Announce "New update released!" or "Event starting soon!"

• Disabled State - Temporarily block access during critical infrastructure work

Impact: When disabled, users cannot access the launcher. Use maintenance mode for scheduled downtime with user communication.

---

Update Settings

Auto-Update Configuration

Fully Automatic Updates

Settings:

• ✅ Check on every launch

• ✅ Download automatically

• ✅ Install silently

• ⚡ Players always updated

Ask Before Updating

Settings:

• ✅ Check on launch

• ❓ Ask before download

• ⏸️ Player decides

• 🎮 Can postpone

Manual Updates Only

• ⏸️ No automatic checks

• 🔍 Player clicks "Check for Updates"

• 🎮 Full control

---

Update Schedule

Schedule	Check Frequency	Best For
Every Launch	Always
Hourly	Once/hour	Active development
Daily	Once/day
Manual	Never	Development/testing

---

Feature Toggles

Enable/Disable Features

Control which features are available:

✅ News Feed

Display news and announcements

✅ Discord RPC

Show game activity on Discord

✅ Crash Reports

Send crash dumps for analysis

❌ Mod Support

Allow players to install mods

Tip: Disable unused features to reduce launcher size and improve performance!

---

Authentication Settings

Login Options

Mandatory Authentication

• ✅ All players must login

• ✅ Full analytics

• ✅ Cloud saves

• 🔐 Maximum control

Configuration:

Login Required: ✅ Yes
Guest Mode: ❌ Disabled
Remember Me: ✅ Enabled
Session Duration: 30 days

Guest Mode Allowed

• 🎮 Players can skip login

• ⚠️ Limited features

• 📊 Anonymous analytics

Configuration:

Login Required: ❌ No
Guest Mode: ✅ Enabled
Guest Features: Limited
Guest Reminder: Every 7 days

No Authentication

• 🔌 Fully offline

• ❌ No accounts

• 📦 Simple distribution

Configuration:

Login Required: ❌ No
Offline Mode: ✅ Full
No Internet Required: ✅ Yes

---

OAuth Providers

Connect third-party authentication:

Provider	Status	Configuration
Google	✅ Supported
Discord	🚧 Coming soon	Client ID, Secret
Steam	🚧 Coming soon	---

Platform Settings

Windows Configuration

Configure platform-specific settings for the Windows launcher build.

Basic Settings:

Setting	Description	Default
Enable Launcher	Enable Windows platform	✅ true
Executable Name	Name of the launcher .exe file	Empty
Maintenance Mode	Platform-specific maintenance	❌ false
Link Only Mode	Button opens URL instead of launching game	❌ false
Link URL	URL to open when "Link Only" is enabled	Empty

Link Only Mode:

When enabled, the launcher button opens a website instead of the launcher executable.

Use Cases:

• Redirect users to a download page

• Link to external platforms

• Redirect to new launcher version

Launch Arguments:

Setting	Description	Default
Enable Custom Launch Arguments	Enable custom launch arguments	❌ false
Launch Arguments	Arguments passed to launcher executable	--windowed --debug
Enable Global Games Launch Arguments	Enable global arguments for all apps	❌ false
Global Games Launch Arguments	Arguments applied to ALL apps in launcher	--language=en

Launch Arguments Priority:

Final Arguments = [Global Launch Arguments] + [Custom Launch Arguments]

Examples:

# Custom Launch Arguments (launcher-specific)
launchArguments: "--windowed --resolution=1280x720"

# Global Launch Arguments (applied to all apps)
globalLaunchArguments: "--language=en --log-level=info"

# Combined Result
--language=en --log-level=info --windowed --resolution=1280x720

Tip: Use Global Arguments for launcher-wide settings and Custom Arguments for launcher-specific configurations.

---

Advanced Settings

Advanced Configuration Options

Configure advanced launcher behavior and features.

Directory Settings:

Setting	Description	Default
Main App Subdirectory	Name of the apps root directory	Apps

How Directory Structure Works:

The mainAppSubdirectoryName defines where apps are installed:

Launcher Directory/
└── Apps/                  ← mainAppSubdirectoryName
    ├── Game1/
    │   ├── Game1.exe
    │   └── Data/
    └── Game2/
        ├── Game2.exe
        └── Assets/

Custom Examples:

mainAppSubdirectoryName: "Apps"     →  Launcher/Apps/Game/
mainAppSubdirectoryName: "Games"    →  Launcher/Games/Game/
mainAppSubdirectoryName: "Content"  →  Launcher/Content/Game/

Coordination: This should match the rootName setting in each app's advanced settings for consistency.

---

Launch Arguments:

Setting	Description	Default
Global Games Launch Arguments	Global arguments applied to all apps	Empty

Installer Settings:

Setting	Description	Default
Deploy with Installer	Include installer in launcher deployments	✅ true

Update & Verification Settings:

Setting	Description	Default
Check for Updates Interval	How often to check for updates (seconds)	3600 (1h)
Verify Files at Launcher Start	Verify launcher files on start	✅ true
Verify Files at App Start	Verify app files before launching	❌ false

UI Settings:

Setting	Description	Default
Slideshow Interval	Slideshow image interval (seconds)	5
Play Slideshow on Start	Auto-play slideshow when launcher starts	✅ true
Show Server Status	Display server status indicator	✅ true

Forced Updates:

Setting	Description	Default
Minimum Required Build Version	Minimum launcher build ID required to access	null

How Forced Updates Work:

When set, players must update to at least this build version before accessing the platform.

minimumRequiredBuildId: null     → No forced updates
minimumRequiredBuildId: 42       → Players must have build #42 or higher
minimumRequiredBuildId: 100      → Players must have build #100 or higher

Use Cases:

• Critical security patches

• Breaking changes in game protocol

• Major feature updates

• Deprecation of old launcher versions

Impact: Players with older versions will be required to update before they can use the launcher.

---

Custom Paths

Override default installation paths:

Game Install Path:
  Default: C:\Games\GameLauncherCloud\{appname}\
  Custom:  D:\MyGames\{appname}\

Launcher Data:
  Default: %APPDATA%\GameLauncherCloud\
  Custom:  C:\LauncherData\

Cache Directory:
  Default: %TEMP%\GameLauncherCloud\
  Custom:  E:\Cache\

---

Security Settings

File Verification

Verification Modes:

Mode	Speed	Security	Best For
None	⚡⚡⚡ Fast	Development
Quick	⚡⚡ Moderate	Most games
Full	⚡ Slow	Competitive

---

Localization

Language Settings

Available Languages:

• 🇬🇧 English

• 🇪🇸 Spanish (Español)

• 🇫🇷 French (Français)

• 🇩🇪 German (Deutsch)

• 🇧🇷 Portuguese (Português)

• 🇷🇺 Russian (Русский)

• 🇯🇵 Japanese (日本語)

• 🇰🇷 Korean (한국어)

• 🇨🇳 Chinese (中文)

Auto-Detection:

• ✅ Detect system language

• ✅ Fall back to English

• ✅ Remember user preference

---

Analytics & Telemetry

Data Collection

Control what data is collected:

Complete Data Collection

• ✅ Launcher usage

• ✅ Game playtime

• ✅ Error reports

• ✅ Performance metrics

• ✅ Feature usage

• 📊 Best insights

---

Notification Settings

Configure Alerts

Notification	Description	Default
Update Available	Notify when game update ready
News Posted	Alert for new news articles	✅ Enabled
Download Complete	Notify when download finishes
Maintenance Mode	Alert during maintenance	✅ Enabled

---

Advanced Settings

File Directories

Setting	Description	Default
Main App Subdirectory Name	Folder name where games are stored	Example Structure:

Launcher Directory/
├── Launcher.exe
└── Apps/              ← Main App Subdirectory
    ├── Game1/
    ├── Game2/
    └── Game3/

Update & Deploy Settings

Setting	Description	Default
Check for Updates Interval	How often to check for launcher updates (seconds)
Deploy with Installer	Build Windows installer (.exe) in addition to ZIP	✅ Enabled

Update Intervals:

• 3600 - Every hour (recommended)

• 7200 - Every 2 hours

• 86400 - Once per day

• 300 - Every 5 minutes (testing only)

News & Slideshow Settings

Setting	Description	Default
Slideshow Interval	Seconds between slideshow images
Play Slideshow on Start	Auto-start slideshow when launcher opens	✅ Enabled

Server & Verification

Setting	Description	Default
Show Server Status	Display server status indicator
Verify Files at Launcher Start	Check file integrity when launcher starts	✅ Enabled
Verify Files at App Start	Check file integrity before launching game	File Verification Impact:

• At Launcher Start - Slower startup, ensures all files are valid

• At App Start - Verifies only the game about to launch

• Both Disabled - Fastest, but no integrity checks

Performance: Enabling "Verify Files at App Start" may cause 1-5 second delay before game launches, depending on game size.

Forced Updates

Setting	Description	Default
Minimum Required Build ID	Force users to update to specific build	None

How It Works:

1. Select a build ID from completed builds dropdown

2. Users with older versions must update before accessing the launcher

3. Set to "No minimum" to make updates optional

Use Cases:

• Critical security patches

• Breaking changes in launcher functionality

• New required features

• Major platform updates

Important: Setting a minimum required build will block all users with older versions. Use carefully and communicate updates to your users.

Example:

Minimum Required Build: Build #42 (v2.5.0)

User with Build #41 → Must update to #42+ to access launcher
User with Build #42 → Can access normally
User with Build #43 → Can access normally

---

Best Practices

✅ Test Changes

Test settings before pushing to production

✅ Document Changes

Keep changelog of setting modifications

✅ Backup Config

Export settings regularly as backup

✅ Use Presets

Start with presets then customize

---

Next Steps

📰 Create News

Engage players with updates

📊 Analytics

Track launcher performance

📚 API Reference

Integrate with custom systems

---

Need Help? Check our troubleshooting guide or join Discord!