Skip to main content

How to tell your Rust players a wipe is delayed

If the old wipe job is still queued, pause or cancel that run first. Then correct the announcement players will find. If the replacement time is unknown, say when you will post the next update.

Keep the old run from firing

Open the tool that performs the elective wipe. If the old run is queued, pause or cancel it and confirm the scheduler no longer shows it at the old time. If it has already started, record what has happened and check the current world before deciding what to do. Leave the job alone until you know what it changed.

Correct the old post before the new message travels

Edit the pinned or linked announcement so it starts with “Wipe delayed”. Remove the obsolete timestamp from the current instructions. Put either the confirmed new time with its zone or the time of your next update in its place. Then post a short reply that points people back to that updated message.

For example, if Harbour was due to wipe at 19:00 UTC and the new map has not downloaded, try “Harbour’s map wipe is delayed. We’re checking the new map. Next update here at 19:30 UTC. Blueprints still stay.” The 19:30 UTC time belongs to the update, so label it that way in Discord and game chat.

Check the timer and any scheduled messages

Review messages that might still announce the old time. Once you know the replacement time, set it in the scheduler and check any in-game countdown separately. Discord timestamps display an actual instant for each reader, so replace the old markup as part of editing the announcement.

Ask a player who only reads the pinned post to tell you what time they should next look at it. If the answer is the previous wipe time or they think your update time is a reopening promise, change the message before you send it elsewhere.

Sources

Analytics settings

Analytics are off.

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