Logs
View and manage launcher and game logs for troubleshooting.
Comprehensive logging system with real-time streaming, filtering, search, and export capabilities. Essential for troubleshooting crashes, bugs, and performance issues.
When reporting bugs, always include logs! Use the Export button to save logs as text files for sharing on GitHub or Discord.
Launcher Logs
Monitor Kable Launcher's internal operations, API calls, file operations, and errors.
Enable persistent logging in Settings to save logs to disk. Great for tracking down intermittent issues that don't happen every launch.
Game Logs
Capture and display Minecraft's console output (STDOUT/STDERR) with crash detection and error highlighting.
| Feature | Description |
|---|---|
| Per-Instance Logs | Separate log tabs for each running Minecraft instance. Perfect for testing multiple versions simultaneously |
| Output Capture | Real-time capture of game console output with line buffering for accuracy |
| Crash Detection | Automatically identifies crash reports and highlights them with red badges |
| Error Highlighting | Errors and warnings color-coded for quick visual scanning |
| Log Parsing | Formatted display of Minecraft log entries with timestamp extraction |
| Exit Code Display | Shows process exit codes (0 = success, non-zero = crash/error) |
| Multi-Instance Support | Run and monitor logs from multiple Minecraft instances at once |
Minecraft crash logs are also saved to crash-reports/ in your game directory. Kable displays them, but files persist separately.
Log Management
Control how logs are stored, compressed, and cleaned up to save disk space and maintain performance.
Set max_memory_logs to 10,000+ if you frequently scroll through long log histories. Lower it to 1,000-2,000 on systems with limited RAM.