Get Started

Schedules

A schedule is a set of steps the server runs on time: a nightly restart with a warning to players, a daily backup, a console command every hour. Schedules are set up on the server's Schedule tab. Times are in the panel's time zone.

Create a schedule

New schedule. The easiest start is a template:

  • Night restart with warning — at 05:00 it sends players say 5 minutes and 1 minute ahead, then restarts the server;
  • Daily backup — at 04:00, keeps the last 7;
  • Backup with stop — once a week it warns players, stops the server, backs it up (keeps 4) and starts it again.

The say command works in Minecraft and Source/GoldSrc games. For other games, replace it with their own command.

When

  • Every day — at a set time;
  • By day of the week — on the chosen days;
  • Every N hours — at a set minute of the hour;
  • Cron — 5 fields (minute hour day month weekday) or @daily, @hourly, @every 2h.

The next runs are shown under the form, an easy way to check the expression.

What to do

Steps run in order:

  • Console command — e.g. say Restart in 5 minutes;
  • Pause — wait a number of seconds or minutes;
  • Restart — skipped on a stopped server;
  • Backup — with Keep latest N: older backups of this schedule are deleted (0 keeps all). Backups made by hand or by another schedule aren't touched;
  • Stop the server / Start the server — waits up to 5 minutes for the server to actually stop or start;
  • HTTP request — a POST with JSON about the run (schedule, server, step number); a 2xx response counts as success. Useful e.g. for a Discord notification through a service of your own. Addresses on internal networks are reachable only from an admin's schedules.

Steps have the options Only if there are no players on the server and Continue if step fails. Without the latter, a failed step stops the whole run.

Managing schedules

The list shows when each schedule fires next and how its last run ended. Run now runs it out of turn. Disable / Enable pause a schedule without deleting it. Run history — when, by hand or on schedule, and the result of every step.

Good to know

  • Steps run on behalf of whoever last saved the schedule, with their permissions on the server.
  • If the panel was down, missed runs aren't caught up.
  • While the server is suspended, schedules don't run.
  • The plan can disallow schedules, limit how many a server has (20 at most) and how often they fire (no more than once every 5 minutes by default), see Plans. These limits don't apply to admins.