How to Set Up Scheduled Tasks on Your Server

The Schedules tab lets you automate actions on your server — restarts, backups, commands — on whatever timer you want, without needing to be online to trigger them yourself.

What a Schedule Can Do

Each schedule is built from one or more tasks, run in order, with an optional delay between each:

• Send a console command — anything you could type into the live console (a save-all, a broadcast message, a plugin-specific command)
• Create a backup
• Power actions — restart, stop, start the server

Setting One Up

1. Go to the Schedules tab and click Create Schedule.
2. Set the trigger: minute, hour, day of month, day of week — standard cron-style scheduling (or use the simpler "every X" presets if your panel theme shows them).
3. Choose whether it's active, and whether it should still run if the server is currently offline.
4. Save the schedule, then add tasks to it — click into the schedule and Add Task, picking the action type and any parameters (like the exact console command to send).
5. Each task can have a delay before it runs relative to the previous task — useful for sequencing, like "warn players in chat, wait 60 seconds, then restart."

Common Real Examples

• Nightly restart at 4 AM to clear memory leaks and apply any pending plugin updates — very common on Minecraft/Rust servers with long uptimes.
• Scheduled backups every 6-12 hours, so you're never more than a few hours behind if something goes wrong.
• Rust wipe automation — a weekly task combining a server.writecfg, world regeneration flags, and a restart, timed to your community's wipe schedule.
• Warning + restart pairs — a chat broadcast task, a short delay, then the restart — so players aren't disconnected without notice.

Things Worth Knowing

• Schedules only run while your service is active (not suspended or expired) — an expired service's schedules simply won't fire.
• A schedule with no enabled tasks does nothing — make sure you've actually added and enabled at least one task after creating the schedule itself.
• Test a new schedule's individual tasks manually from the console first (run the exact same command by hand) before trusting the automation, especially for anything destructive like a world reset.

Once set up correctly, this is genuinely "set it and forget it" — the panel handles the timing, you just check in occasionally to confirm it's still running as expected.