Know why it crashed — in seconds.

Real analysis, not guesswork

Most launchers dump a wall of log text on you. XMlauncher's detector opens the newest file in your crash-reports folder and extracts the stack trace — the exact code paths that were running when the game died.

It then reads every installed mod jar and maps its real top-level package structure (not guesses from filenames), so it can tell you which of your mods' code appears in the crash. That's the strongest automatic signal there is for "start here".

Patterns it recognizes instantly

• Out of memory — heap exhausted; the fixer re-tunes your RAM allocation
• Duplicate mods — the same mod present twice (two versions of one jar)
• Mixin injection failures — two mods fighting over the same game code, or a mod built for a different Minecraft version
• Mods involved in the crash — every installed mod whose packages show up in the stack trace

How to use it

1. Play normally. If the game crashes, the analysis opens automatically — no buttons to hunt for.
2. Read the summary: it names the mods involved and the pattern detected, honestly ("these mods' code ran during the crash", not "mod X is definitely guilty").
3. Apply a suggested fix in one click, or remove the suspect mod from the Mods tab and relaunch.

Honest limits

The detector won't pretend to know more than it does. If no installed mod matches the crash, it says so and points you at the full report instead of inventing a culprit. Diagnosis like proven mod-vs-mod incompatibility needs a compatibility database — so the launcher stays with what it can actually verify.

Pairs well with