NewSchokr 13 is here. A whole new UI, seven locations, snapshots and more. Read more →

How to wipe a Rust server (map and blueprint wipes)

Do a map wipe or a full blueprint wipe on your Rust server on Schokr by deleting the right save files, and prepare for the monthly forced wipe.

Updated · 2 min read

To wipe a Rust server, stop it and delete the save files. A map wipe removes the map and save files; a blueprint wipe also removes the player blueprint database. Schokr doesn't wipe for you, so you do this manually in the file manager or with a schedule.

Map wipe vs blueprint wipe

Wipe typeWhat resetsWhat stays
Map wipeBuildings, items, the worldPlayers' learned blueprints
Blueprint (full) wipeEverything above plus blueprintsServer settings, plugins, admins

Many community servers map wipe weekly or every two weeks and do a full wipe monthly.

The monthly forced wipe

Facepunch releases a major Rust update on the first Thursday of most months. These updates usually force a map wipe, because old saves aren't compatible, and sometimes force a blueprint wipe too. When an update lands:

  1. Restart the server so it downloads the update.
  2. If you use Oxide/uMod, update it as well. See Oxide plugins.
  3. Wipe if the update requires it.

Before you wipe

Take a backup or snapshot of the server first. If you delete the wrong file, you can restore it.

Doing a map wipe

  1. Stop the server.
  2. Open the file manager and go to the server identity folder:
server/rust/
  1. Delete the map and save files. These end in .map and .sav, and there may be several .sav backups with numbers after them, such as .sav.1.
  2. If you want a different map, change the seed in your Startup settings. Keeping the same seed and world size regenerates the same map layout, fresh.
  3. Start the server. It will generate the map again.

Doing a blueprint wipe

Do everything in the map wipe, and also delete the blueprint database in the same folder. Its file name starts with player.blueprints and ends in .db. Delete any matching -journal or -wal file next to it too.

Don't delete the cfg folder. It contains server.cfg and users.cfg, where your admins and moderators are stored.

Other data you may want to reset

  • Plugin data: Oxide plugins store data in oxide/data. Some plugins, like economy or kits plugins, keep data across wipes unless you clear their data files. Check each plugin's documentation before deleting anything.
  • Player deaths and identities: other .db files in the identity folder store things like player state. Leave them alone unless you know what they do.

Automating it

You can use the Schedules section to stop the server at a fixed time, but deleting files must be done by hand in the file manager. Some admins use an Oxide plugin to handle scheduled wipes instead.

Still stuck?

If the server won't start after a wipe, post the console log in the Schokr Discord.