
How to announce a Rust wipe across time zones
Open the next run of the job that will perform the wipe. Use its actual date and time to write the announcement. A Discord timestamp shows that instant in each reader’s local time, and a plain UTC time travels with the message.
Start with the full date from the wipe job
For example, Friday 11 December 2026 at 00:30 UTC falls on Thursday evening for a player at UTC−05:00. Write the date, time and zone together even if you normally tell regulars the weekday alone. For a local recurring schedule, check the next date in its named time zone. When clocks change, the UTC hour can move while the local hour stays the same.
| UTC | At UTC−05:00 | At UTC+10:00 |
|---|---|---|
| Friday 11 December at 00:30 | Thursday 10 December at 19:30 | Friday 11 December at 10:30 |
Write the Discord notice and the UTC fallback
Discord uses seconds since the Unix epoch. For the example above, use <t:1796949000:F> in a regular Discord message. The capital F asks Discord to show the full date and time. A copyable message is “Harbour map wipe at <t:1796949000:F> (Friday 11 December 2026, 00:30 UTC). Blueprints stay.” Replace the server, timestamp and what resets before sending.
Paste the timestamp as ordinary text in a private test message. Ask a player in another zone to read back the weekday and hour they see. Copy the plain UTC part into places that do not display Discord timestamps, such as game chat.
Check the two places that can get out of step
Compare the test message with the scheduler’s next run. If you also display Rust’s in-game countdown, compare that separately. Facepunch’s PrintWipe output shows the next timer date, which can come from an override. The announcement and the countdown need to agree with the job that will actually reset the world.
For a recurring wipe, generate a fresh timestamp from the next run before reposting. If a clock change leaves the game timer or the scheduler showing a different instant, correct the schedule or countdown before posting the new date.