Skip to main content

Log analysis

When the game crashes or misbehaves, log analysis helps you pinpoint the problem in a flood of log output.

Two entry points

Manual analysis

  • Copy the log text (from the game console, latest.log, or the launcher’s live log window)
  • Paste it into the input box on the Log analysis page
  • Click Analyze log
The launcher recognizes known error patterns in the log (crash stack traces, Mixin conflicts, mods with missing dependencies, out of memory, and so on), lists them by severity (Critical → Error → Warning → Info), and suggests common fixes.

Crash report analysis

When the game crashes, the launcher captures the crash report and starts analyzing it immediately — you don’t need to click anything:
  • By the time the crash dialog (the game exited unexpectedly) appears, the analysis is already done
  • The dialog only offers Copy all / Export report; the diagnosis is shown directly
  • The report is uploaded to mclo.gs automatically to generate a short link, shown in the dialog as a badge plus a QR code so you can share it when asking for help (there is nothing to enable and no switch for it)
When you ask others for help, include the mclo.gs link from the crash analysis result plus the list of mods you recently installed or updated. That’s far more effective than a screenshot saying “the game crashed”.

Live log

While an instance is running, go to Sidebar → Running (or use the live log window at launch) to watch the game output:
  • Filter by level (INFO / WARN / ERROR / DEBUG / FATAL / Other)
  • Search by keyword
  • Stop game to end the process directly when something goes wrong
  • The live log window has no export button; to export the full log, go to Settings → Logs