Configure blueprint (BP) wipes

On Rust, a map wipe (buildings, items on the ground) and a blueprint wipe (unlocked recipes, player.blueprints.* files) are two independent operations. Since late 2025, official servers wipe BPs on every map wipe, but on a private server you can choose to keep them.

Cause / The problem

Many admins delete *.map thinking they wipe everything, then are surprised players keep their recipes — or the opposite, lose BPs when they only wanted a map wipe. Without a clear strategy, the server economy drifts out of balance.

Solution

1. Understand the difference:
   • Map wipe = delete *.map and *.sav → buildings and ground loot disappear.
   • BP wipe = delete player.blueprints.*.db → unlocked recipes are lost.
2. For a map wipe while keeping BPs, delete only these files in /server/<identity>/:

   *.map
   *.sav
   player.deaths.*.db
   player.states.*.db

   Do not touch the player.blueprints.*.db files.
3. For a blueprint-only wipe, delete only:

   player.blueprints.*.db

4. Plan a common cadence: weekly map wipe (e.g. every Thursday) + monthly BP wipe. This keeps the server dynamic while giving players time to unlock their recipes.
5. Automate with a uMod plugin such as WipeInfo or ScheduleWipes (Facepunch ships no native scheduler):

   # Install the plugin into oxide/plugins/
   # Configure the frequency in oxide/config/ScheduleWipes.json

   Most of these plugins can distinguish a map wipe from a BP wipe.
6. Verify after restart in the console: a reconnecting player must no longer have their recipes if you ran a BP wipe, and must keep them otherwise.

Never delete files while the server is running: stop it first in the Pelican panel.