The launcher log (the file with STDOUT from the game) is extremely helpful for debugging crashes.
Sometimes, the game crashes without any errors in `latest.log`, but the relevant information is logged to the game’s STDOUT.
The most common cases are `module.ResolutionException` or certain mixin errors.
The `latest.log` file just cuts off, while STDOUT contains the error needed for debugging.
As the developer of the Crash Assistant mod, I’m active in all support channels, and asking users to disable “skip launcher” is a huge pain for everyone in the modding support communities.
Logging the game’s STDOUT to a file is very easy and quick to implement, and it would help the modding community a lot.
Modrinth recently added this feature — they log STDOUT to `logs/launcher_log.txt`. Here’s the PR where they implemented it:
https://github.com/modrinth/code/pull/3444
I recently contacted the ATLauncher devs; they loved the idea and are also planning to add this in a couple of weeks.
I think it would be good for logging STDOUT to `logs/launcher_log.txt` to become a standard for non-Mojang launchers.
This board is being moderated, if you wish for your idea(s) to go public, please consider the following:
If your idea already exists, vote for it, this will increase the chances for the idea to become reality. Duplicate ideas only split and lower votes
This board is for new ideas and feature suggestions, for technical issues or bug reports, visit/contact CurseForge Support
This ensures that the idea is accessible to a wider audience and makes it easier for others to understand and vote for the idea
Any ideas posted with foul language will not be published and get deleted
Avoid posting 'lists' of different ideas, we won't be able to address them with a proper status and they will get less votes from others, each idea should have its own post
Hi there,
This is now planned :)