How to wipe and update a Rust server
Prepare for Rust patches and monthly force wipes, back up the server identity, update Steam app 258550, refresh the mod framework, and control whether blueprints survive.
Rust receives routine patches between its monthly force wipes. A patch updates the dedicated files. A force wipe also advances the save protocol and creates a new map.
Facepunch's wipe timer guide sets the default monthly schedule to the first Thursday at 19:00 London time. Weekly and biweekly community servers can publish their own schedules with the matching browser tag.
Know what each wipe changes
| Maintenance | Dedicated build | Map | Blueprints |
|---|---|---|---|
| Routine patch | Updated | Preserved when compatible | Preserved |
| Monthly force wipe | Updated | Replaced for the new protocol | Usually preserved |
| Community map wipe | Current | Replaced by the owner | Preserved |
| Blueprint wipe | Current | Usually replaced | Removed |
The
Rust server file guide
explains that the protocol number in the .sav filename increases during a
force wipe. The updated server creates a current save. Renaming the old file
cannot convert its data.
Prepare the maintenance window
Tell players what will reset
Publish the date, timezone, expected downtime, map plan, and blueprint decision.
Save and stop
Run server.save, wait for completion, then use the normal Stop control. The
power guide covers berrybyte controls.
Create a backup
Back up the complete identity and config. Name the entry with the current build and wipe type.
Record the setup
Note the branch, framework, identity, seed, world size, and important plugin versions.
On berrybyte, open Backups → Create Backup. The
backup guide explains downloads and selected-file
restores. A self-host should archive server/<identity>/ and its startup
script outside the install directory.
Update on berrybyte
Keep Auto Update enabled under Settings → Game Settings. Starting the server checks the dedicated build before Rust launches.
Confirm the branch
Use the public branch for normal players. Staging and aux builds require clients from the same branch.
Start after the backup
Press Start and watch Console while the updater and game process run.
Wait for readiness
Keep public announcements paused until Console prints Server startup complete.
Inspect the framework
Confirm Oxide, uMod, or Carbon loaded. Review plugin errors before the first public join.
The connection guide covers protocol errors from mismatched client and server builds.
Update a self-host with SteamCMD
Run SteamCMD against the permanent install directory:
./steamcmd.sh +force_install_dir /srv/rust +login anonymous +app_update 258550 validate +quitFacepunch identifies 258550 as the dedicated-server app in its
installation guide.
Keep force_install_dir consistent during every update.
SteamCMD manages the vanilla Rust files. Apply the current Oxide or uMod build afterward when the server uses that framework. Carbon follows its own release instructions. Start with the same identity and port config.
Keep RustDedicated stopped while SteamCMD and the framework updater replace files. Retain the pre-update backup through the first clean restart.
Complete a force wipe
Review the map values
Check server.seed, server.worldsize, and server.level. A changed value generates a
different procedural map.
Install the force-wipe build
Update through berrybyte Auto Update or SteamCMD.
Start with the same identity
Rust sees the protocol change and creates the current save. Keep player databases in place when blueprints should survive.
Watch map generation
Wait through terrain and monument placement until Server startup complete.
Test direct connection
Press F1 in Rust and run client.connect IP:gameport. Check spawn, monuments, blueprints,
and core plugins.
The join guide explains the game port and browser listing.
Run an extra map wipe
Stop the server and back up its identity. Remove the active
protocol-versioned .sav selected for that map, then start with the intended
seed and size. Rust creates a fresh save.
Keep player.blueprints when the published schedule says map wipe. The
database sits under server/<identity>/ beside the save and other player
data.
Removing the complete identity can erase configs, bans, owners, blueprints, and Rust+ pairing data. Download the backup before deleting a save.
Add a blueprint wipe
A blueprint wipe removes player.blueprints for the active identity. Stop the
process first.
Announce the reset
State that researched recipes will disappear.
Back up the identity
Keep the blueprint database with the matching map backup.
Remove player.blueprints
Delete that file from the active identity while the process is offline.
Start and verify
Join with a returning account and confirm the research state matches the announcement.
Hardcore and custom modes can use different persistence rules. Check the active mode before publishing retention details.
Preserve server administration
A planned wipe should retain:
server.cfgand the startup command.users.cfgwith owners and moderators.- Ban data and
server.identity. - Plugin config and data intended to survive.
- RCON, Rust+, game, and query allocation settings.
The setup guide documents identity, ports, and owner access.
Verify the reopened server
The old map returned
Check the active identity, seed, size, and .sav files. Stop the process before changing
the save Rust selected.
Blueprints disappeared
Keep the server offline and restore the matching player.blueprints file from the backup.
Plugins fail after the patch
Update the framework, then update or disable the plugins named in Console.
Players get wrong connection protocol
Confirm Steam updated the client and server to the same branch and build.
For save damage and framework troubleshooting, open Common Rust server issues. Contact berrybyte support with the backup timestamp and update log when the identity will not reopen.
Frequently asked questions
When is the official Rust force wipe?
Facepunch's default monthly schedule is the first Thursday at 19:00 London time. Check the current release post before converting that time for players.
Does a Rust force wipe remove blueprints?
A normal force wipe replaces the map save when its protocol changes. Blueprints usually remain. A blueprint wipe also removes the player.blueprints database and should be announced separately.
How do I update a Rust dedicated server?
Save and stop it, create a backup, then run SteamCMD app_update 258550 validate against the existing install folder. Start the server and wait for Server startup complete.
Do Rust plugins break after an update?
A Rust update can require a matching Oxide, uMod, or Carbon build. Refresh the framework and review plugin errors before players return.
Can I change the Rust seed during a wipe?
Yes. Set the new seed or world size before map generation. Keep server.identity unchanged so configs, admins, bans, and intended plugin data remain.