LiquidLauncher provides a powerful game launching system that handles version management, resource downloading, and process execution automatically.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/CCBlueX/LiquidLauncher/llms.txt
Use this file to discover all available pages before exploring further.
Quick Start
Selecting Branches and Builds
Requesting Available Branches
The launcher fetches available branches from the LiquidBounce API:The launcher uses exponential backoff to retry failed requests, ensuring reliable branch fetching even with network issues.
Fetching Builds for a Branch
Once you’ve selected a branch, fetch available builds:The branch name (e.g., “nextgen”, “legacy”)
Whether to show only release builds (true) or include nightly builds (false)
Launch Parameters
The launcher uses a comprehensiveStartParameter structure to configure game launching:
Key Parameters
Java runtime to use. Options:
Automatic: Let the launcher choose (recommended)Custom: Specify a custom Java pathManual: Choose specific distribution (Temurin, GraalVM, Zulu)
Custom JVM arguments to pass to Java (e.g.,
-XX:+UseG1GC)Memory allocation in megabytes
Custom directory for game data. If empty, uses default launcher directory
Whether to keep the launcher window open after game starts
Number of parallel downloads for assets and libraries
Running the Client
The main launch command orchestrates the entire launch process:Launch Process
The launcher performs these steps automatically:Resource Setup
Downloads and prepares:
- Java Runtime Environment (if needed)
- Client JAR file
- Required libraries
- Game assets
- Native libraries
JVM Configuration
Builds JVM arguments including:
- Memory settings (
-Xmx,-Xms) - LiquidBounce API configuration
- Custom JVM args
- Classpath
Launch Events
The launcher emits events during the launch process:progress-update
progress-update
Emitted during resource download and setup
process-output
process-output
Game console output (stdout/stderr)
client-error
client-error
Emitted when an error occurs during launch
client-exited
client-exited
Emitted when the game process terminates
Java Distribution Selection
LiquidLauncher supports multiple Java distributions:Distribution Comparison
| Distribution | Java 8 | Java 11 | Java 17 | Java 21+ |
|---|---|---|---|---|
| Temurin | ✅ | ✅ | ✅ | ✅ |
| GraalVM | ❌ | ❌ | ✅ | ✅ |
| Zulu | ✅ | ✅ | ✅ | ✅ |
Temurin is recommended for most users as it supports all Java versions and has excellent compatibility.
Automatic Distribution Download
The launcher automatically downloads the appropriate Java distribution:Terminating the Game
You can stop the running game programmatically:Viewing Changelogs
You can fetch changelogs for specific builds:Troubleshooting
Client is already running error
Client is already running error
Only one game instance can run at a time. If you see this error:
- Close the existing game window
- Wait for the process to fully terminate
- Try launching again
Failed to fetch launch manifest
Failed to fetch launch manifest
This usually indicates:
- Network connectivity issues
- Invalid build ID
- Server downtime
Java binary not found
Java binary not found
If the Java binary is missing:
- Delete the
runtimesfolder in your data directory - Restart the launcher
- The Java runtime will be re-downloaded
Out of memory errors
Out of memory errors
Increase memory allocation in Settings:
- Go to Settings
- Increase the Memory slider
- Recommended: 4GB minimum, 8GB for better performance
Next Steps
Mods Management
Learn how to install and manage mods
Settings
Configure advanced launch options