Skip to content

Automatic Schedules

In the game panel: Your server → Schedules

Schedules can run power actions, console commands, and backups at set times.

The Game Panel uses five cron timing fields. Each field controls a different part of the schedule.

FieldAllowed valuesExample
Minute0 to 5930 means 30 minutes past the hour
Hour0 to 234 means 04:00
Day of month1 to 311 means the first day of the month
Month1 to 126 means June
Day of week0 to 71 means Monday. Both 0 and 7 mean Sunday

An asterisk (*) means every available value. For example, * in the month field means every month.

Other useful patterns include:

  • */6 means every 6 units.
  • 1-5 means every value from 1 through 5.
  • 0,30 means at values 0 and 30.

Enter the values into the matching fields in the Game Panel. Do not paste the full five-part expression into one field.

When the schedule should runMinuteHourDay of monthMonthDay of week
Every day at 04:0004***
Every 6 hours0*/6***
Every 30 minutes*/30****
Every Monday at 03:30303**1
Monday to Friday at 05:0005**1-5
First day of each month at 02:00021**
Every Sunday at midnight00**0

Convert your intended local time to UTC before saving the schedule.

This example restarts the server every day at 04:00 and gives players a five-minute warning.

  1. Create a schedule named Daily restart.
  2. Enter 0 for minute and 4 for hour.
  3. Enter * in the remaining timing fields.
  4. Save the schedule.
  5. Add a Send command task with the warning command supported by your game.
  6. Set the first task’s time offset to 0.
  7. Add a Power action task and select Restart.
  8. Set the restart task’s time offset to 300 seconds.
  9. Enable the schedule.

The exact warning command depends on the game. Test it manually in the console before adding it to a schedule. If the game does not support broadcast commands, create only the restart task.

  1. Create a schedule and choose a low-traffic time.
  2. Add a Create backup task with a time offset of 0.
  3. Enable the schedule.

Do not schedule a restart immediately after a backup. Backup times vary with the size of the server, so the restart could begin before the backup finishes. Use separate schedules with enough time between them.

Tasks run in sequence using their time offsets. For example:

TaskActionTime offset
1Send a five-minute warning0 seconds
2Run the game’s save command240 seconds
3Restart the server60 seconds

This gives players four minutes before the save command, followed by another minute before the restart.

Keep Continue on failure disabled for important task chains unless you understand the effect. When enabled, later tasks can run even if an earlier command or action fails.

  • Daily low-traffic restarts
  • Automatic backups before maintenance
  • Save or broadcast commands before a restart
  • Periodic cleanup commands supported by the game

Avoid schedules that restart too frequently or overlap. If a backup is still running when a restart begins, the copy may be incomplete.