Automating Tasks with Schedules

The Schedules tab runs actions on a recurring timer without you needing to be online — restarts, backups, or any console command.

Creating a Schedule

1. Go to Schedules → Create schedule
2. Give it a name
3. Fill in Minute, Hour, Day of Month, Month, and Day of Week — standard cron fields, each defaulting to * (every). Flip on Show Cheatsheet in the dialog if you want worked examples while you fill these in
4. Save, then add one or more tasks to it

# Cron quick reference
*/5 * * * *  → Every 5 minutes
0 3 * * *    → 3:00 AM daily
0 */6 * * *  → Every 6 hours
0 3 * * 0    → 3:00 AM every Sunday

Two toggles on the create dialog matter beyond the timing itself:

• Only When Server Is Online — on by default. With it on, the entire schedule is skipped while the server is stopped — including a Power Action task that would otherwise start it. Turn this off if you want a schedule to be able to boot a stopped server.
• Schedule Enabled — the master on/off switch, separate from timing.

Task Types

Each schedule is made of one or more tasks, run in order:

• Send Command — anything you could type in the console (say, save-all, gamerule, etc.)
• Create Backup — same as clicking Create Backup manually, see Backups
• Power Action — restart or stop the server

Common Uses

• Nightly automatic backups (see Backups)
• A scheduled restart every few days to clear accumulated memory/lag on long-running worlds
• Periodic save-all if you’re paranoid about power loss between auto-saves
• A recurring time set day or weather clear if you want a server that never experiences night or rain