free · for the server, and for the person reading the log
Crash Assistant catches the crash. Roastd reads it.
Crash Assistant is a client-side mod for Fabric, Forge, NeoForge and Quilt with tens of millions of downloads. When the game crashes it shows a window with every relevant log, lets you upload them to mclo.gs with one click, and runs the mclo.gs analyser over them. It is a good mod and it earns its download count.
It also does nothing on a server, by design, and nothing for the person on the other end of the support thread who now has a log link and a question. Roastd covers both: it reads server logs, and it reads the mclo.gs link Crash Assistant just produced, and turns either into a finding, a fix and a report link.
Where Crash Assistant is strong
- It is there when the client crashes. The window appears immediately with the game log, launcher log, crash report and hs_err file already collected.
- One-click upload to mclo.gs, and only when the player presses Upload. The mod has no servers of its own.
- Works across Fabric, Forge, NeoForge, Quilt and Legacy Fabric, and modpack authors can ship it in the pack.
- Source available on GitHub.
What Roastd covers that a client mod cannot
The server side
Crash Assistant does nothing on a dedicated server. Roastd reads server crash reports, latest.log, watchdog dumps, proxy logs and the container runner output around them.
The person reading the log
Paste the mclo.gs link a player sent you and get the finding, not the raw text. That is the half of the job a client mod cannot see.
Nothing to install
Roastd is a page and a Discord bot. Nobody has to add a mod to their pack, and it works for the player on vanilla who has never heard of mclo.gs.
A written rule per finding
135 Minecraft failures, each with a page that shows the exact line, the cause and the fix. Deterministic, so two people get the same answer.
The rest of the server
A spark profile, the mod list or server.properties alongside the log turns the report into a health check.
The Discord bot
Where Crash Assistant's links get posted is usually a Discord channel. The Roastd bot reads them there: /roast with the link, or right-click the message.
Side by side
| Crash Assistant | Roastd | |
|---|---|---|
| What it is | A client mod that collects and uploads logs after a crash | A log analyser for servers and clients, on the web and in Discord |
| Runs on a server | No, by design | Yes, that is the main job |
| Needs installing | Yes, in the client modpack | No |
| Upload target | mclo.gs | Reads mclo.gs links, pasted text and uploaded files |
| Analysis | mclo.gs analyser | 135 Minecraft rules, each with a reference page |
| Report | The mclo.gs paste | A permanent roastd.me link with findings, fixes and the redacted log |
| Discord | None | Bot with slash command and message context menu |
| Cost | Free | Free |
Based on each product's published features and pricing as of 22 September 2026. If something here has changed, tell us and we will correct it.
Using both
- 1Keep Crash Assistant in the client packIt is the best way to make sure a player who crashes ends up with a log link instead of a screenshot of the launcher.
- 2Paste that link into RoastdWhen the mclo.gs link lands in your support channel, paste it into the Minecraft analyser or run /roast on it with the bot.
- 3Roast the server log tooIf the client crash was a kick or a disconnect, the server log from the same minute usually names the reason. Paste both.
- 4Post the reportThe roastd.me link replaces the back-and-forth. The player sees the finding, and so does the next person with the same crash.
Every finding Roastd can raise has its own page in the Minecraft error index.
Questions you'd be right to ask
Should I remove Crash Assistant from my pack?
No. It solves a different problem: getting the log out of a crashed client and into a link. Roastd starts where that link ends.
Can Roastd read client crashes?
Yes. It recognises client logs, hs_err files and launcher output, and applies the client-side rules: graphics drivers, shader packs, resource packs, missing mods on join, version and loader mismatches.
Does Roastd need anything installed on the server?
No. Paste the log, or the link, on the web or in Discord. There is nothing to add to the server or the pack.
Where does the log go?
Addresses, tokens, passwords and session ids are stripped before anything is stored. The redacted text is kept on a timer for the report, then deleted. The report keeps only the findings.
The link is in the channel. Roast it.
Coming from another tool?