Fix buttons and autopilot

How fixing works

Every finding says where the problem lives (a file, a setting in your panel, your firewall or DNS) and, when Tickhound can do it, shows a button. Buttons never act without you pressing them. Anything that changes a file makes a backup copy next to it first and checks the result.

What can be fixed depends on what is connected: config changes and panel changes need your Pterodactyl panel linked, actions on the running server need the Tickhound plugin.

Config changes

Settings in server.properties, bukkit.yml, spigot.yml and the Paper configs are changed through the panel. Only those files, only the lines Tickhound knows, with a parse check and a read-back afterwards. Restart the server to use them.

Panel changes

Switch the Docker image to a newer Java, create a backup, or create a nightly restart or backup schedule. These use your own Pterodactyl Client API key. Restart after changing the image.

Startup command

For problems with memory or garbage collector flags the button reads the real startup command from your panel and shows it next to a suggestion for your container size and Java version: a heap of 80% of the container memory and tuned G1 flags (or ZGC when that is what you use). Everything else in the command, such as system properties, the jar and --nogui, stays as it was.

How it is applied depends on what the panel allows. If the egg has an editable flags variable, Tickhound fills that. If you added an Application key in Settings → Integrations, Tickhound replaces the startup command itself. Otherwise you can copy the new command and paste it in Panel → Startup. The result is read back from the panel before it is reported as done, and the dialog offers a restart.

Actions on the running server

The plugin can clear old dropped items, thin out one overcrowded chunk, unload chunks nobody is near, save all worlds and run garbage collection. It runs them within about 30 seconds and reports what it did.

Players are never touched. Named, tamed, leashed and ridden animals, villagers, bosses and armor stands are never removed. Items younger than ten seconds are kept. Every action is capped.

Autopilot

Switch it on in the Server optimizer and Tickhound applies the changes marked safe by itself after each automatic scan, then tells you what it changed through your alerts. Changes that players could notice, or that need a check first, are never applied by autopilot.

Panel owners: nodes

If you run Pterodactyl yourself, add an Application key (Admin → Application API) to your panel in Settings → Integrations. The Infrastructure page then shows every node with memory, disk and free ports, and checks them: overcommitted memory, a full node, almost no free ports, nodes without TLS, maintenance mode, servers without limits, and database or Docker ports that answer from the internet.

Fix buttons can turn maintenance mode off, lower over-allocation to 10% and add 25 more ports. The key is encrypted and never shown again; remove it any time.

What fixes never do

They never delete worlds, player data or plugins, never change passwords, never open ports and never restart your server on their own. The only restart-like actions are the ones you schedule yourself.