Roast my server: free Minecraft crash log analyzer

Paste a Minecraft crash log, mclo.gs link or spark profile. Roastd names what broke, which mod caused it, and the exact fix. Free, no account.

Your logs get stripped of addresses, tokens and passwords before anything is saved. Raw pastes are deleted on a timer. The shared report never contains them.

Both link types are read straight from the source, so an mclo.gs paste or a spark profile saves you copying anything. Running badly rather than crashing? Run /spark profiler start, let it sample while the server is slow, then paste the link it gives you. Roastd reads the tick times, the entity clusters and which plugin or mod the time went into.

What Roastd checks in a Minecraft crash report

Roastd runs your paste through a hundred-signature library built from the one we use on our own fleet.

Crashes. Out of memory in every flavour, including the exit code 137 kill. Java version mismatches, down to the release you need. Mixin and mod conflicts, with the mod named from the stack trace. Dependency failures, missing registries, corrupt worlds, full disks, port clashes, watchdog stalls.

Plugins and proxies. Unknown dependencies, wrong API versions, async abuse. BungeeCord and Velocity forwarding, Geyser and Floodgate setup, ViaVersion breakage.

Config. Add server.properties, your mod list and specs and it checks RAM headroom, view and simulation distance, spawn protection, watchdog settings, client-only mods and duplicates.

It knows what it's reading. Paper, Forge, NeoForge, Fabric, proxy and client logs each get the right checks. When one fault caused another it says so instead of listing symptoms. If nothing matches, it tells you rather than guessing.

Why does my Minecraft server keep crashing?

Most repeat crashes come down to one of four things: the heap is too small or sized past the machine's physical RAM, the Java version does not match the Minecraft version, a mod is patching game code that is not there in this build, or a mod is missing a dependency it needs to load. A crash log names which one it is. Paste yours above and Roastd reads the stack trace and tells you which of those you are looking at, and which mod is responsible.

How do I read a Minecraft crash report?

Start at the top. The description line says what the server was doing when it died. The first exception under it is the real fault; everything below is the call stack that led there. Further down, the System Details block gives the Minecraft version, the Java version, the JVM flags and the physical memory, which is where heap and Java mismatches show up. The mod list at the bottom tells you what was loaded. Roastd reads all of that and reports the fault rather than the symptoms.

Analyse a crash log in Discord

Most crash logs get pasted into a support channel long before anyone thinks to open a website. Add the bot and your helpers can diagnose one on the spot: /roast with the file attached, or right-click any message and pick Roast this message.

Run a community? Add the Roastd bot and anyone can roast a crash log right in your support channel: /roast, or right-click a message.

Add the Roastd bot
Cookies

We use a few cookies that are strictly necessary to sign you in and keep your account secure. We do not load any advertising or third-party trackers. We would also like to run our own cookieless analytics so we can understand which pages are useful. See our Cookie Policy for the full list.