Roastd reads your Minecraft server’s logs and config, works out what is wrong, and tells you without softening it.
Give it a crash report, a latest.log, an mclo.gs link or a spark profile. It goes through and names what is actually costing you: the view distance you set to 32 because bigger sounded better, the JVM flags you inherited from a forum post in 2019, the heap that is either starving the server or too big for the machine it runs on. Every finding says why it matters and what to change. The roast is the delivery. The fix is the point.
In Discord
/roast log: attach a crash report or latest.log
/roast link: if it is already on mclo.gs
/roast spark: for a server that lags rather than crashes
Or right-click any message > Apps > Roast this message, which is the civilised way to tell someone their modpack is the problem.
Every roast comes back with a link anyone can open, so you can hand it to whoever built the server or drop it in your support channel and let someone else break the news. Good for triaging “why is my server lagging” before a human has to open a log.
It matches a library of around a hundred known failures. When it does not recognise a crash it says what the report does know and which mods were in the frames it died on.
Free, no account required. Sometimes your config is the problem. Sometimes your host is. Roastd will say which.
Built by Hostd, a game server host that has read an unreasonable number of broken configs.
Try it in the browser at hostdservers.com/roastd
