Rust runs on wipe cycles. At a set interval, the map resets: all bases, vehicles and placed objects disappear. Players start fresh with a rock and a torch. It is the core mechanic that keeps Rust feeling new, but as a server admin you need to understand the types of wipes and how to configure them.
Force wipe
Facepunch forces a mandatory map wipe on the first Thursday of every month. The server update is incompatible with the old map data. Your map resets automatically regardless of your schedule. Blueprints may or may not be wiped; Facepunch decides per month. The next force wipe is Thursday, October 1, 2026.
Three types of wipe
| Type | What resets | What stays |
|---|---|---|
| Map wipe | The map: bases, vehicles, dropped items | Blueprints (learned recipes) |
| BP wipe | Blueprints | The map (if you only wipe BPs) |
| Full wipe | Map and blueprints | Nothing |
Choosing a wipe schedule
- Weekly: most active players right after wipe. Popular for PvP servers. Downside: casual players get discouraged.
- Biweekly: the most common choice. Enough time to build, short enough to stay fresh.
- Monthly: only the force wipe. Good for casual and PvE servers.
How to wipe technically
- Make a backup (in case you want to revert).
- Stop the server.
- For a map wipe: delete the .map and .sav files, or change
server.seedfor a new map. - For a BP wipe: delete the
player.blueprints.*.dbfiles. - Start the server. The map regenerates.
What happens if I miss the force wipe?
You cannot run the old version after a Facepunch update. Update the server; the map resets automatically.
Can I prevent the force wipe?
No. It is mandatory and unavoidable. It is part of Rust's design.
Do players lose their skins?
No. Skins are tied to the Steam account, not the server. They are available again immediately after a wipe.
All Rust plans at HostValues support scheduled restarts and wipe automation through the game panel.
