Minecraft Server Doctor
Drop your whole server folder, or its zip. This reads the log, the crash report, every mod jar's own metadata and your JVM arguments together, and tells you which file to change. Nothing is uploaded and there is no account. There is no upload limit because there is no upload, but the practical ceiling is your browser's memory: a zip is opened whole, ZIP64 archives need the folder picker instead, and the first 800 mod jars are inspected.
Drop your server folder or a .zip of it here, or
or a zip:
The more you include, the better the answer. logs/ plus mods/ is the minimum for naming a culprit file.
Why a folder and not a log
Every other analyzer takes one file, and that framing is why they stop at the exception.
A log says NoSuchMethodError was thrown from
com.simibubi.create.foundation.render.CreateRenderTypes. On its own that is
a shrug. Your mods/ folder says that class lives in
create-0.5.1.jar. That jar's own mods.toml says it requires
flywheel [0.6.10,0.6.11). And the folder says
flywheel-0.6.9.jar is what is actually installed.
Four facts, one sentence: replace flywheel-0.6.9.jar. Do not add RAM, do not change Java. That is the whole reason this reads a folder.
What it will not do
It will not tell you a mod is broken when it cannot prove it. A dependency range it
cannot parse is reported as unknown, never as a mismatch, because sending you to
replace a mod that was fine costs you an evening. A requirement on the loader, the
game or Java is never reported as a missing mod - those are not files in
mods/. If you did not include your mods/ folder it says so
rather than answering with less than you think. And it does not write anything: it
reads your folder and tells you what to change.
Want this on a real server? Supercraft hosts Minecraft →