Skip to main content

Which Rust server changes should wait until after the wipe?

Write down the wipe you promised players. Keep the changes required for that version of the world together. Move an optional change to a separate session if you can verify it later without resetting player progress again.

Keep the work small enough to open on time

Suppose you announced a new generated world with blueprints retained. The new map and the blueprint check belong to that wipe. A new welcome message can wait, since players can join and play under the current message. A plugin that must be installed before the first players act needs its own decision before opening, even if you originally called it optional.

If the game update requires a matching framework update for the world you advertised, include that dependency in the wipe checklist. Facepunch’s wipe timer can announce the window, but use the job that actually performs the change to decide which steps must finish.

Keep the work small enough to open on time
Proposed changeCan you defer it?
New advertised worldOnly by telling players the wipe plan changed
Revised community messageYes, if the existing rules remain accurate
Plugin required to enforce the advertised first-session rulesOnly if players are told which rules or admission will change

Give postponed work a next check

On a spare world, run the smallest version you can open. Join as a regular player and check what you promised, such as the intended map and a retained test blueprint. If the rehearsal passes, label the other jobs with their own next rehearsal. When a change would require another wipe to verify, move it to the next planned wipe instead of testing it on the open world.

Sources

Analytics settings

Analytics are off.

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