Documentation
What each check means, why it matters and how to fix it.
- What Tickhound doesTickhound finds what is wrong with a Minecraft server and tells you how to fix it.
- How diagnostics workFrom raw files to findings: parsers, rules, scoring and rule categories.
- Connecting a serverThree ways to give Tickhound data: network probes, uploaded files and monitoring.
- Pterodactyl integrationLink your own Pterodactyl panel so Tickhound can read files and resource usage.
- Security scannerDefensive, non-intrusive checks for exposure and risky configuration.
- Understanding health scoresHow findings turn into category scores and the overall 0–100 health score.
- Understanding TPS & MSPTThe numbers behind lag: ticks, tick time, CPU, memory and garbage collection.
- Game config filesWhat Tickhound checks in bukkit.yml, spigot.yml and the Paper config files, and the values it recommends.
- World and entitiesWhat the Tickhound plugin reads from your worlds and how to act on it.
- Pterodactyl: import, checks and optimizerImport your whole network, what Tickhound checks in the panel, and how the optimizer applies fixes.
- Alerts and toolsGet messages in Discord, and use the helpers that work without a server.
- Security hardeningThe security checks, what they mean and how to fix them.
- Network map and Velocity wizardSee proxies and backends together, compare servers and set up Velocity forwarding everywhere.
- Log analysisThe problems Tickhound recognises in your server log.
- Fix buttons and autopilotWhere to fix every problem, and the buttons that fix it for you.
- Plugin diagnosticsDependencies, conflicts, version compatibility and runtime errors.
- Network diagnosticsDNS, ports, proxy architecture and origin exposure.