Minecraft server offline? Restart it automatically

Did your Minecraft server stop overnight? An automatic task can now try to start it when it is offline. You can also make a Minecraft server or BungeeCord/Velocity proxy react to a CPU, RAM, storage, or player-count threshold.

To get started, open Automatic tasks, create an Action on condition task, then choose The server is offline and Start the server. Set the minimum delay between attempts. Your scheduled tasks are still available in the same place.

Run on a schedule or react to server status

When you create a task, choose its type:

Scheduled execution: the task runs at the chosen time, once or on a recurring schedule.
Action on condition: BoxToPlay checks the server about once a minute and attempts the action when the condition is met.

Scheduling is still useful for sending /save-all at night on Minecraft or a message at a set time. An action on condition responds to the server’s state instead of the clock.

Choose a trigger and an action

Choose when to act, which action to run, and a minimum delay between attempts. The delay prevents the action from repeating every minute while the condition remains true.

Three trigger families cover the essentials:

the server is offline
the server is online
a metric goes above, reaches or drops below a threshold (CPU, RAM, disk, players, network throughput, uptime)

The available actions depend on the trigger. If the server is offline, you can start it. If it is online or a metric reaches your chosen threshold, you can stop it, restart it, or send it a command.

Examples that actually help

With a 10-minute delay, for example, BoxToPlay can try to restart the server once it confirms that the server has stopped. After you stop it manually from the panel, the rule waits 15 minutes before any attempt. A scheduled task that sends /stop does not trigger this wait, so the server may restart sooner. If you want it to stay off, pause the rule.

Another classic: during an event, a latency spike comes with CPU usage repeatedly climbing above 90%. Choose A metric reaches a threshold, CPU (%), greater than 90, then Restart the server, with a 30-minute delay. The delay prevents back-to-back restarts. If the threshold is still exceeded, another attempt cannot happen until those 30 minutes have passed. This setting interrupts play, so use it only if you want to allow an automatic restart at that threshold.

You can also send a command instead of restarting. On BungeeCord, /alert can broadcast a message across the network. On Minecraft, /say can notify players when their count exceeds a threshold. The chosen delay prevents these messages from repeating on every check.

You can choose a minimum delay of five, ten, thirty, or sixty minutes to suit your needs.

What about alerts?

A task that acts on its own is good. Knowing that it acted is even better.

The Notification Center can notify you when an automatic task succeeds or fails, whether it is scheduled or triggered by a condition. Depending on the channels you enable, you can receive alerts in the panel, on your phone, on Discord, or on Slack.

To choose your alerts and delivery channels, read BoxToPlay Updates: Custom Notification Center and Real-Time Alerts.

In your BoxToPlay client area, open Automatic tasks for your Minecraft, BungeeCord, or Velocity server to create your rule. Then enable an alert if you want to know when it runs.