
How to stop two Rust wipe schedules from colliding
Start with the next two dated occurrences. One world can have two jobs competing to wipe it, and two worlds can need the same staff at once. Give each world a single reset owner and check the full maintenance window for both.
Make each occurrence visible in one calendar
Read the next run in your panel, startup scripts and any maintenance manager. Write the world, actual date, local time with its zone, and which tool runs the job. Include the player warning, backup, wipe, restart and final join check. Use the time for the actual date, since the same named hour can move when clocks change.
For a regular wipe that collides with a required reset on the same world, select which job will own the reset and pause or skip the competing occurrence using that tool's own controls. Read back the next run before you rely on it. The in-game wipe timer uses separate inputs for its countdown, so check that it still describes the date you will actually run.
Give the worlds a sequence staff can cover
Example for Harbor Weekly and Harbor Monthly on one host. Replace these relative dates with next run dates from your own calendars.
| Window | Write down | Check before proceeding |
|---|---|---|
| Release window on the first Thursday | One approved required reset per world. Which operator verifies Weekly and who covers Monthly. | No competing regular wipe for either world. If one person must check both, arrange separate start points around the required update and keep players informed. |
| Optional cleanup or plugin job during that window | Which world it touches and whether it must finish before reopening. | Move a discretionary job if it could overlap the handoff or staff cannot verify it. |
| Following Thursday | Weekly's normal occurrence if that is your cadence. | Confirm the recurring job is back on its normal date and Monthly has no extra wipe. |
Decide when to postpone and how to reopen
If a world has no confirmed running version, no usable backup or no one to verify the reset, keep that world closed and communicate the revised opening. Defer the optional jobs. After each wipe, check the intended world in the client before announcing it. Confirm the calendar shows only the intended next run for each world.
In a disposable real Carbon rehearsal with overlapping jobs on one server, one scheduled change missed its intended start while the wipe used the server. The rehearsal did not test two simultaneous game instances. Check the schedule for both worlds yourself before relying on the handoff.