Pattern matching, not magic

The scan runs a set of rules collected from real broken servers. When a line matches one, we pin a finding to the top with the line number and what usually fixes it. No model, no guessing — if nothing matches, we say nothing.

1
You paste

Console log, crash report or config. Small logs are read before the page finishes loading.

2
Rules run

Each rule knows one failure shape — a Java version clash, a missing dependency, a port already in use.

3
Findings pin

Blocking problems first, then performance, then housekeeping. Each one links to its line.

What the rules catch today
Java version clash
A plugin compiled for a newer Java than the server runs — the single most common reason a server won't start.
Missing dependency
A plugin that declares a hard dependency on a jar which isn't in /plugins, so it is skipped entirely.
Plugin failed while enabling
Loaded, then threw — usually NoSuchMethodError, the classic sign of a build meant for a different server version.
Port already in use
Two servers on one port, or a ghost process still holding 25565.
EULA not accepted
The server writes eula.txt on first boot and refuses to start until you agree to it.
Out of memory
Heap exhaustion, and the point after which nothing else in the log can be trusted.
Crash report
A full crash dump, with the description pulled out and the trace left for you to read.
Watchdog kill
The main thread stopped responding long enough that the watchdog forced a crash.
Disk full
Writes failing — which is how a full disk turns into a rolled-back world.
Chunk or region damage
A region file that would not read or write, worth acting on before the next restart.
Tick stalls
"Can't keep up!" bursts, with how far behind the server fell and when.
Outdated plugins
Plugins reporting that a newer build is available.
Offline mode
Anyone can join as any username — correct behind a proxy, a problem otherwise.
Undeclared dependency
A plugin using another's classes without declaring it, which works until load order changes.

Missing one? The raw log is always right there — the scan never hides anything, it only points.