-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ
No. It is strictly read-only — it analyzes, reports and recommends. Recommendations are data, never executed automatically. This is enforced by architecture tests, not just policy.
Yes. The universal jar carries both a plugin.yml and a velocity-plugin.json. Drop the same
file into a Paper/Folia server or a Velocity proxy.
- Single server with local disk → SQLite (default).
- A network → a shared PostgreSQL, MariaDB or MongoDB, pointed at by the proxy and every backend server.
- Just testing → memory.
See Storage Backends.
It bundles four database drivers; the MongoDB driver + BSON is the biggest. If you only use
SQL, drop mongodb-driver-sync from serverdoctor-storage/build.gradle.kts to slim it down.
No. ServerDoctor logs a warning and falls back to SQLite, then In-Memory. The configured backend is printed to the log so you can confirm what's active.
A proxy has no tick loop, so the Performance scanner is skipped there by capability gating. The proxy still records plugin, dependency, conflict and security findings.
Switching storage.type starts fresh in the new backend — there is no built-in migration
between stores.
Yes. The scheduler adapter detects Folia and switches automatically.
Install PlaceholderAPI on Paper/Folia; the serverdoctor expansion self-registers. See
PlaceholderAPI.
Yes — there's a small public API and event bus, and you can register custom scanners. See Developer API.
Yes. Enable the REST API for read-only HTTP/JSON access (see REST API) and/or webhooks to push Discord/Slack/Teams alerts on status changes (see Webhooks). Both are off by default and add no external dependencies.
ServerDoctor checks GitHub releases for the repo. If an update is found it logs the new version and download link (and, on Paper, disables itself until you update; on Velocity it goes inert).
ServerDoctor · read-only analysis for Minecraft servers & proxies · MIT · Repository