Discord alerts for Crafty Controller servers
Keep Crafty Controller in Docker running your Minecraft servers, and add crash, disk and backup alerts in Discord or Slack, player history and scheduled backups.
Crafty Controller is a good way to run Minecraft servers at home. It doesn't tell you when one of them crashes in the night, when the disk is nearly full or when a backup quietly stopped working. MineOps adds that without taking anything away from Crafty: Crafty keeps running your servers, and MineOps watches them.
What you need
- Crafty Controller running in Docker on Linux, in a container named
crafty, with its servers and settings kept in folders on the machine. A Crafty installed without Docker isn't connected. - The MineOps agent on the same machine. Its installer finds the running Crafty container and connects it.
What MineOps adds
- Discord or Slack alerts when a server goes offline or crash-loops, the machine runs low on memory or disk or a backup fails, and when it recovers.
- Every Crafty server on the machine's Minecraft tab under its Crafty name, with status, players, memory and uptime, next to servers on your other machines.
- Start, stop, the console and settings from MineOps, carried out through Crafty, and player history with your quietest hour.
- Scheduled backups with checksums, on the Plus plan and up. Restoring from the dashboard is for servers MineOps creates.
- A live status message in your Discord.
What MineOps can do in Crafty
The connection asks Crafty to create a mineops-agent user that can reach the Minecraft Java servers Crafty has: start and stop them, use the console, read logs, change files such as server.properties and delete servers. Its token is kept on your machine, readable only by root and the agent. Servers you add or remove in Crafty show up in MineOps within a minute. New servers you create in MineOps are run by MineOps itself, not through Crafty.
Every action MineOps takes is recorded in your audit log with who asked for it. See what the agent can and cannot do.