free · no monthly cap, no account
An MCDoctor alternative with no meter on it
MCDoctor reads a Minecraft server log with a language model and writes back an explanation. That is a reasonable way to build a log analyser, and the output reads well. The free tier allows five standard and one advanced analysis a month, paid plans start at $4.99 a month for 100, and saving reports needs an account.
Roastd takes the other approach. Every finding comes from a written rule, matched against the log, with a page that explains the exact line. There is no monthly cap, no account, no card, and no model deciding whether your crash looks like a crash it has seen before.
Where MCDoctor is strong
- Free-form explanations. A language model can describe an unusual crash in prose even when no rule exists for it.
- Wide loader support: Paper, Purpur, Spigot, Bukkit, Fabric, Quilt, Forge, NeoForge and vanilla logs.
- Larger uploads on paid tiers, up to 10 MB log files.
- Logs are described as analysed securely and never stored permanently.
What changes without the model
No cap, no card, no account
Roast as many logs as the day brings. There is no free tier because there is no paid tier.
The same answer every time
A rule either matches or it does not. Two people pasting the same log get the same report, which matters when a support thread is arguing about whose mod it was.
It says when it does not know
If nothing in the catalogue matches, the report says that. A crash that fits no rule is more useful reported as unknown than dressed up as a confident guess.
Every finding has a page
135 Minecraft failures, each with the exact log line, the cause and the fix, written by the people who run a hosting fleet on the same rules.
More than the log
Add a spark profile, mod list or server.properties and the report checks memory headroom, view distance, client-only mods and settings that cost tick time.
Share it, or run it in Discord
Every report is a permanent link on roastd.me. The Discord bot gives your helpers the same report from a /roast command or a right-click on any message.
Side by side
| MCDoctor | Roastd | |
|---|---|---|
| How it reads the log | AI analysis | Written rules, matched line by line |
| Free usage | 5 standard and 1 advanced analysis a month | Unlimited |
| Paid tiers | From $4.99 a month for 100 analyses | None |
| Account | Needed to save reports | None |
| Inputs | Crash logs and error reports | Crash logs, latest.log, mclo.gs links, spark profiles, mod lists, server.properties |
| Shareable report | Saved to your account | Permanent public link on roastd.me |
| Discord bot | Not offered | Yes, with a slash command and a message context menu |
| When nothing matches | The model still answers | The report says no rule matched |
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.
Trying Roastd on the same log
- 1Take the log you already havelatest.log, a crash report, an hs_err file or an mclo.gs link. Roastd reads them all, and it reads the whole file, not the last few hundred lines.
- 2Paste itOpen the Minecraft analyser and paste or upload. No sign-in step, no plan picker.
- 3Read the findings, then the pagesEach finding links to a page with the exact line, the cause and the fix. When one fault caused another, the report nests the symptom under the cause.
- 4Compare the two reportsIf the model and the rules disagree, the rule page shows you exactly what it matched so you can decide who is right.
Every finding Roastd can raise has its own page in the Minecraft error index.
Questions you'd be right to ask
Is a rule-based analyser worse than AI at unusual crashes?
At a crash nobody has catalogued, yes: a model will write something and a rule will not. Roastd reports that as no match, and every crash that turns out to be common gets a rule. For the crashes that account for most of a support channel, a rule that names the exact line and the exact fix beats a paragraph that might.
Where does my log go?
Addresses, tokens, passwords and session ids are stripped before anything is stored. The redacted text is kept on a timer so the report can show it, then deleted. The report keeps only the findings.
Do I need a Hostd server?
No. Roastd reads any Minecraft server log from anywhere. It is built by Hostd and uses the same detection our own fleet runs, and where a finding is something a different hosting setup would prevent, the report says so.
Is there a limit at all?
Only a rate limit to keep the service up for everyone. Nobody working through a stack of logs in a support channel will hit it.
No meter. Paste the log.
Coming from another tool?