Skip to main content

What schedule details should you keep when changing Rust tools?

Save more than the displayed next run. A recurring job needs a time zone, the worlds it affects, the actions it performs and what it does when the scheduled time is missed. A separate warning deserves its own line in the record.

Make a schedule record you can read without the old tool

If the current tool can export schedules, read the downloaded file and check which details it includes. Fill in any missing information from the schedule view. If there’s no export, record these fields once for each job you still need.

Make a schedule record you can read without the old tool
FieldExample
World and actionRestart Evening Builds.
Repeat time and time zoneSaturday at 08:00 in Europe/London.
WarningPost the notice to #updates before the restart. Keep its text with the schedule.
Missed runSkip it if the host misses its window.
Next checkCompare the next date in both schedules and check the first run next week.

Rebuild from the record while the old schedule is visible

In the new tool, compare the next two dates in the time zone you intend, especially around a clock change. Check that the warnings, execution order and missed-run behavior match what you promised players. Set up the replacement with the old job still visible. Before the new job’s first live run, turn off the old copy so only one sends a notice or acts on the game.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details