Automatic Schedules
Your server → Schedules Schedules can run power actions, console commands, and backups at set times.
Understand the timing fields
Section titled “Understand the timing fields”The Game Panel uses five cron timing fields. Each field controls a different part of the schedule.
| Field | Allowed values | Example |
|---|---|---|
| Minute | 0 to 59 | 30 means 30 minutes past the hour |
| Hour | 0 to 23 | 4 means 04:00 |
| Day of month | 1 to 31 | 1 means the first day of the month |
| Month | 1 to 12 | 6 means June |
| Day of week | 0 to 7 | 1 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:
*/6means every 6 units.1-5means every value from 1 through 5.0,30means 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.
Timing examples
Section titled “Timing examples”| When the schedule should run | Minute | Hour | Day of month | Month | Day of week |
|---|---|---|---|---|---|
| Every day at 04:00 | 0 | 4 | * | * | * |
| Every 6 hours | 0 | */6 | * | * | * |
| Every 30 minutes | */30 | * | * | * | * |
| Every Monday at 03:30 | 30 | 3 | * | * | 1 |
| Monday to Friday at 05:00 | 0 | 5 | * | * | 1-5 |
| First day of each month at 02:00 | 0 | 2 | 1 | * | * |
| Every Sunday at midnight | 0 | 0 | * | * | 0 |
Convert your intended local time to UTC before saving the schedule.
Create a scheduled restart
Section titled “Create a scheduled restart”This example restarts the server every day at 04:00 and gives players a five-minute warning.
- Create a schedule named
Daily restart. - Enter
0for minute and4for hour. - Enter
*in the remaining timing fields. - Save the schedule.
- Add a Send command task with the warning command supported by your game.
- Set the first task’s time offset to
0. - Add a Power action task and select Restart.
- Set the restart task’s time offset to
300seconds. - 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.
Create an automatic backup
Section titled “Create an automatic backup”- Create a schedule and choose a low-traffic time.
- Add a Create backup task with a time offset of
0. - 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.
Run several commands in order
Section titled “Run several commands in order”Tasks run in sequence using their time offsets. For example:
| Task | Action | Time offset |
|---|---|---|
| 1 | Send a five-minute warning | 0 seconds |
| 2 | Run the game’s save command | 240 seconds |
| 3 | Restart the server | 60 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.
Good uses
Section titled “Good uses”- 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.