
Wipes are part of Rust. Every server starts a fresh map on forced wipe day, and most communities wipe more often to keep things fair and fresh. Here's how to do a map, blueprint or full wipe on your server, which files to delete, and how to plan a schedule your players can rely on.
Stop the server and open server/<identity> (usually server/rust). Map wipe: delete the .map and .sav files. Blueprint wipe: also delete player.blueprints.*.db. Full wipe: delete the map files and every .db file. Keep the cfg folder, back up first, then start the server.
| Wipe | Resets | Keeps |
|---|---|---|
| Map wipe | The map and everything built on it | Blueprints, admins, bans |
| Blueprint wipe | Learned blueprints | The map, unless you wipe it too |
| Full wipe | Map, blueprints and player data | Admins, bans and server settings |
A map wipe gives everyone a fresh start but lets players keep the blueprints they've learned, so progress comes back quickly. A blueprint wipe resets that progress too. A full wipe is a clean slate for everyone.
Facepunch releases Rust's monthly update on the first Thursday of every month, usually around 7 PM UK time (2 PM Eastern). The update changes the save format, so every server starts a fresh map that day: your server can't keep its old map once it updates.
Blueprints are only force-wiped when Facepunch announces it with an update, so read the patch notes each month. Plenty of servers choose to do a full blueprint wipe on forced wipe day anyway, since everyone's starting over that day.
Stop it from your game panel. Never delete save files while the server is running.
In the file manager (or over SFTP), open server/ and then the folder named after your server identity. That's set by the +server.identity startup parameter and is usually rust.
.map or .sav, including numbered backups like .sav.1.player.blueprints.*.db. The number in the name changes with game versions, so check your own folder..db file in the folder (blueprints, player states, deaths, identities and the rest). Players may need to pair the Rust+ app again.Keep the cfg folder
cfg holds your server settings, admins and moderators, and bans. Leave it alone in every type of wipe.
For a brand new map, change the world seed (any number up to 2147483647) and, if you like, the world size in your server's startup settings. Keep the same seed and the same map regenerates, with no buildings on it. Sites like RustMaps let you preview a seed before you pick it.
The server generates the new map on startup, which can take a few minutes for bigger maps. Watch the console until it's ready, then let your players in.
Oxide and Carbon plugins keep their own data in oxide/data or carbon/data. Most reset themselves when they detect a new map, but some (shops, kits, economy) keep data on purpose. Check each plugin's docs to see what should reset at wipe.
There's no single right answer: it depends on your players.
Many servers wipe on Thursdays so their schedule lines up with forced wipe day. Whatever you choose, put it in your server name or description, for example "Weekly | Wiped 14/11", so players browsing the server list know what to expect.
Doing all this by hand every week gets old fast. On our Rust server hosting you can schedule automatic wipes by map, blueprint or both, weekly, every two weeks or monthly, from your control panel. Oxide and Carbon are ready to go, and daily backups mean a bad wipe is never the end of your server. If you move to a bigger map with more players, you can add RAM later without moving anything.
player.blueprints.*.db file wasn't deleted.Only when Facepunch announces a blueprint wipe with that month's update. Every forced wipe resets the map.
No, as long as you keep the cfg folder.
Yes. Keep the same seed and size, and the same map generates fresh, without any buildings on it.
Rust servers from $8.99/month, with Oxide and Carbon, scheduled wipes and free DDoS protection.