ROAST MY
SERVER

What it actually checks

Roastd runs your paste through a hundred-signature library grown from the one we use on our own fleet. Crashes: out-of-memory in all its flavours (heap, metaspace, direct buffers, the exit code 137 kill), Java version mismatches down to the exact release needed, mixin and mod conflicts with the offending mod named from the stack trace, Fabric and Forge dependency failures, missing registries, corrupt worlds, truncated region files, datapack failures, full disks, port clashes, watchdog stalls and ticking entities. Plugin servers: unknown dependencies, wrong API versions, async thread abuse and broken configs, each naming the plugin at fault. Proxies: BungeeCord and Velocity forwarding mistakes, forwarding secret mismatches, Geyser and Floodgate setup errors, ViaVersion breakage.

It also understands what it is reading: it identifies Paper, Forge, NeoForge, Fabric, proxy and client logs and runs the right checks for each, and when one problem caused another (a crash then a hang, a full disk then broken chunk saves) it folds them into a single diagnosis instead of listing symptoms. Adding server.properties, your mod list and specs unlocks the config checks: RAM headroom against the exit-137 kill, view and simulation distance, spawn-protection (the classic silent one), watchdog settings on modded servers, client-only mods in server packs, duplicate mods and more.

Everything is matched against known signatures. If nothing matches, it says so rather than guessing. Paste the newest crash report from your crash-reports folder for the best result; logs/latest.log works too.

Running ARK: Survival Ascended? Switch the toggle and paste GameUserSettings.ini, Game.ini and your launch command. It reads all three together, so a setting on the command line counts just as much as one in the files: the map, the mod list and any ?options and -flags are all understood. Roastd reads the config the same way as a log: a blank ServerAdminPassword leaving the admin console open, bUseSingleplayerSettings quietly rewriting your rates on a dedicated box, settings sitting in the wrong file where the game ignores them, DifficultyOffset with no OverrideOfficialDifficulty capping wild dino levels, breeding rates where 100% imprint is mathematically out of reach, a rate multiplier left at 0 or autosave switched off, the same setting written twice so an earlier edit is silently overridden, save-period and DinoCountMultiplier values that cost you performance, and curly quotes from a pasted guide that the INI parser drops. Every finding comes with the exact line to paste, and the shared report shows your config back with the problem lines highlighted.

Put it in your 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.