Crash Link

CrashLink V2 Changelog

CrashLink V2 improves duplicate crash handling, crash-session reliability, and the overall support flow.

UI and support flow improvements

• Added a smaller, less intrusive main-menu mini prompt after broken sessions.
• CrashLink no longer opens the full upload screen immediately.
• Players can click the mini prompt to open the full crash/log upload screen.
• Improved and shortened wording across the upload flow to make it clearer and less intimidating.
• Renamed several buttons for clarity:
  • Open Folder → Open Logs Folder
  • Open mclo.gs → Open Link
  • Open Discord → Open Support Discord
  • Ignore This Time → Ignore

Modpack developer support links

• Added configurable support links for modpack developers.
• Developers can now add a Discord invite link in the CrashLink config.
• Developers can now add a GitHub Issues page in the CrashLink config.
• Developers can customize the support message shown after upload.
• If configured, CrashLink shows extra support buttons after upload:
  • Open Support Discord
  • Open GitHub Issues
• Default behavior remains unchanged if no support links are configured.

Repeat crash handling

• Prevented repeat prompts for the exact same handled crash/log file or session.
• Added matching-signature detection for new crashes that appear identical to a previous handled crash.
• CrashLink can now warn when a new crash looks like the same error as before.
• If a previous matching crash was uploaded, players can copy the previous link.
• Ignore now skips that specific crash/log instance rather than treating the whole issue as permanently resolved.

Broken-session reliability

• Fixed real crash reports sometimes being incorrectly marked as clean shutdowns.
• Improved reliability of broken-session detection after actual crash report creation.
• CrashLink still prefers the newest relevant crash report first.
• If no crash report exists, CrashLink falls back to the best available log file.
• Archived logs are preferred before using latest.log as the final fallback.

Oversized log handling

• Improved oversized log trimming behavior.
• Normal-sized crash reports/logs are still uploaded fully.
• If a selected crash/log file is too large for mclo.gs limits, CrashLink now keeps both:
  • the beginning of the log
  • the end of the log
• Only the middle of oversized logs is trimmed.
• Uploaded logs now include clear CrashLink notes explaining when trimming happened.
• Upload metadata now marks whether the uploaded log was trimmed.
• This preserves startup/environment/mod-loading information from the top of the log while still keeping crash/error/stacktrace details from the bottom.
• The original local log/crash file is never modified; trimming only affects the uploaded copy.

Privacy and upload behavior

• CrashLink still asks before uploading anything.
• CrashLink does not silently upload logs.
• The selected file is only uploaded to mclo.gs after the player chooses to upload.
• The success screen provides a copyable support link after upload.
• Players can still open the local logs/crash folder if they need to manually send the original full file.