Skip to content

Scheduled commands

Under Configure → Scheduled commands. Creating and changing schedules is an admin action; anyone with access can see what is scheduled.

There are two things to schedule.

Broadcast a message supports the same {{placeholders}} as any other broadcast. Placeholders are filled in when the message is sent, not when you save it, so {{hours_until}} in a nightly wipe reminder is right every night.

Restart the server runs Rust’s own restart with a countdown players can see, forcing a save and shutting down cleanly. Pick how much warning they get — 1 minute to 30 — and optionally a line saying why. Anyone with access can cancel a countdown that is already running, from the server’s Overview page.

At a time of day — a time and a set of days. “20:00, Friday and Saturday”.

On a repeat — every 15 minutes up to every 12 hours.

There is no cron field. The two shapes above cover what a Rust server actually needs, and a cron expression is a thing two people read differently.

A daily schedule means the wall-clock time where your players are. CerebRUST uses the timezone you set under Wipe → Schedule — the same one your wipe countdown uses, so there is only ever one to get right.

Clock changes are handled. A schedule set for 20:00 stays at 20:00 through the spring and autumn changes rather than drifting an hour.

If you change your server’s timezone, every schedule’s next run moves with it immediately.

If your server or CerebRUST is down over a slot, that run is passed over, not sent late. A wipe reminder delivered three hours afterwards is not late — it is wrong.

The list shows skipped with the time when this last happened, so you get an answer rather than a silence.

Unticking every day means the schedule never runs. That is allowed, and the page says so, because guessing “they probably meant every day” would be inventing an instruction you did not give.