Show STDOUT/STDERR in Console
Skip Launcher is a great idea, the official Minecraft Launcher never works and this lets you skip that, however sometimes it can cause crashes and turning it off causes the game to work, But more importantly unlike other launchers such as the official launcher, the Console shows latest.log but does not show STDOUT or STDERR like most consoles do. In the vanilla launcher this is stored as launcher_log.txt and also shows up in the Console, but the CursedForge App Console does not which is 1st deviant from the standard across launchers, and also leaves out lots of debugging info such as System.out.println as well as some errors, such as some SpongeMixin Errors and some JPMS errors, which are especially common on ModLauncher. A real world example is if you have 2 copies of a mod, especially an early loading one like CrashDetector on MCForge 1.21.10 it will crash due to duplicated packages however if you use the CursedForge console you would not be able to see the error, nor even have access to the error without 3rd party SysOut/SysErr proxy mods so you would never be able to see it. I have attached Screenshots of the output of both the vanilla launcher console and cursedforge console, so you can see the difference. The in-launcher-console is what most people use for debugging so it is important that it has all the information, in addition some mods for fixing errors will ask for a launcher log to be pasted.
-
Guest
- Oct 30 2025
- Future consideration
Related ideas
Hello,
Since the CursedForge App's console currently seems to omit STDOUT/STDERR, here are the best practices and workarounds for capturing this crucial information:
Check the Launcher Log File
Even if the CursedForge console doesn't display it, the official Minecraft Launcher saves this information to a file. When using the CursedForge App, the modpack is still run using an underlying version of the vanilla launcher components.
Search your Minecraft installation directory for files named similar to launcher_log.txt or jvm_log.txt. The location can vary, but it's often in the main .minecraft folder or a subdirectory related to the specific instance profile.
Use a Dedicated Console/Proxy Mod
You mentioned this, and it is a highly effective solution for troubleshooting in this environment. Mods like ConsoleFilter (for Fabric/Forge) or similar tools force the game to redirect or mirror the missing console output into the standard log file (latest.log) or a dedicated GUI/file, ensuring the information is available.
Run Minecraft Directly via Script
The most robust way to ensure you capture all output is to bypass the CursedForge App's launch method and run the game directly through a custom script (like a .bat or .sh file). This allows you to redirect the STDOUT and STDERR streams to a file yourself:
Locate the startup command: You would need to inspect the CursedForge instance details to find the exact Java command and arguments it uses to launch your modpack.
Create a script: Wrap that command in a script that includes a redirection operator:
java -jar <YourLaunchArgs> > full_console_output.txt 2>&1 E-ZPass Ohio
2>&1 redirects STDERR (stream 2) to the same location as STDOUT (stream 1).
This issue is a known pain point for developers and advanced users who rely on the full console output for diagnosing complex mod conflicts. You may want to suggest to CursedForge that they implement a toggle to display the full JVM STDOUT/STDERR streams in their console view.