Ready to play?
Pick your game, choose a plan, and start playing in under 60 seconds. No lag, no excuses.
Woof! Let's go!

Wipes are what keep Rust fresh: new map, new bases, everyone back to a rock. To wipe a Rust server, you delete the map save, the blueprint data or both, then start the server again. This guide shows which files do what, how to run a map wipe or a blueprint wipe step by step, and what actually happens on force wipe day.
.sav and .map files in server/rust, plus player.states, then start the server. Blueprints stay.player.blueprints files.player. data file.| Wipe | What resets | Files to delete in server/rust |
|---|---|---|
| Map wipe | The world, bases, loot and where players are standing | proceduralmap.*.sav (and its .sav.1, .sav.2 backups), proceduralmap.*.map, sv.files.*.db, player.states.* |
| Blueprint wipe | Every blueprint players have learned | player.blueprints.* |
| Full wipe | All of the above, plus player history | Map files, player.blueprints.*, player.states.*, player.deaths.*, player.identities*, player.tokens* |
The numbers in those file names (map size, seed and save version) differ from server to server, so match the names you actually see. Running a custom map? Its save is named after your map file instead of proceduralmap.
Most community servers run map wipes weekly or every two weeks and save blueprint wipes for force wipe day or a big monthly reset. Whatever you pick, put the schedule in your server name or description so players know what they're joining.
Force wipe lands on the first Thursday of every month, when Facepunch releases the monthly update. It usually goes live around 19:00 UTC (2 PM Eastern) in winter and 18:00 UTC in summer. The next ones are November 5 and December 3, 2026, then January 7, 2027.
The update changes the save format, so every server starts a fresh map. Blueprints only reset when Facepunch announces a blueprint wipe with the update.
On BruceNode, your Rust server checks for game updates every time it starts. When the update is out, restart your server from the Console tab and it comes back on the new version, ready for the rush.
This is the quickest way to run a one-off wipe:
server, then rust.Server startup complete, you're live.If you wipe on a schedule, set it up once on the Startup tab:
server/rust/proceduralmap.* server/rust/sv.files.* server/rust/player.states.*; add server/rust/player.blueprints.* to wipe blueprints too.0 and every reinstall rolls a new random seed, so each wipe gets a new map. Set a number to keep the same layout.Then, whenever it's wipe time, go to Settings and click Reinstall Server. The reinstall also pulls the latest Rust build, so on force wipe day one click updates and wipes together. Your configs, plugin files and admin list stay where they are; only what is listed in Files to remove goes.
Double check Files to remove before a reinstall: it deletes exactly what you type, so keep it pointed at the save files above. If you'd rather not wipe on the next reinstall, switch Regen Server back off.
On BruceNode you can turn on Oxide (uMod) or Carbon from the Modding Framework setting on the Startup tab. The framework installs itself and stays current every time the server starts, which matters on force wipe day, when plugins need the new build.
Plugin data lives in oxide/data or carbon/data. A wipe by hand leaves it alone, and the reinstall method only clears the plugin files listed in Files to remove. Many kit, shop and clan plugins keep their data across wipes on purpose. If you want a clean economy too, check each plugin's page for its wipe setting, or clear its data file during the wipe.
A Rust wipe is a handful of files and a restart: map files for a map wipe, blueprint files for a blueprint wipe, both for a full reset. Set up Files to remove once and every wipe after that is a single reinstall. New to running Rust? Start with our Rust server setup guide. Planning a new community? Rust server hosting on BruceNode comes with Oxide and Carbon built in, and code BRUCE20 takes 20% off your first month.
Related posts on BruceNode: