> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabihosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Rust Server Wipes — Map & Blueprint Wipe Guide

> How to wipe your Rust server hosting instance — map wipes vs. blueprint wipes, monthly forced wipes, changing the seed, and automating wipes with Schedules.

Wipes are a core part of Rust's gameplay loop. A wipe resets progress so everyone starts fresh — and running them cleanly and on a predictable schedule is one of the biggest factors in keeping a server population healthy. This guide explains the two wipe types and exactly how to perform them on your Wasabi Hosting server.

## Map Wipe vs. Blueprint Wipe

|                | Map wipe                                                  | Blueprint (BP) wipe                                           |
| -------------- | --------------------------------------------------------- | ------------------------------------------------------------- |
| Resets         | Terrain, bases, entities, dropped items, player positions | Learned blueprints (crafting knowledge)                       |
| Frequency      | Every wipe cycle (weekly/bi-weekly/monthly)               | Less often — many servers only BP-wipe monthly or when forced |
| Files affected | `.map` and `.sav` files                                   | `player.blueprints.*.db`                                      |

Most servers map-wipe on their regular schedule and keep blueprints across several map wipes so returning players don't have to re-learn everything each week.

## Forced Wipe Day

<Info>
  On the **first Thursday of every month** (typically in the evening, European time), Facepunch releases a mandatory update that **forces a map wipe on every Rust server**. Blueprint wipes are only forced when Facepunch explicitly says so — most months, BPs can carry over.
</Info>

On forced wipe day you must: update the server, **update Oxide/Carbon if you run plugins** (see [installing plugins](/games/rust/install-plugins)), and perform the map wipe. Plan to be available around update time — players flood in right after forced wipes.

## Before You Wipe: Back Up

<Warning>
  Wiping deletes files permanently. Take a backup first from the **Backups** tab in the Game Panel — it takes a minute and lets you roll back if anything goes wrong. See the [backups guide](/server/backups).
</Warning>

## How to Perform a Map Wipe

<Steps>
  <Step title="Stop the server">
    In the [Game Panel](https://panel.wasabihosting.com), stop your server. Never delete save files while the server is running.
  </Step>

  <Step title="Open the identity folder">
    In the **File Manager**, navigate to your server identity folder:

    ```
    /server/my_server_identity/
    ```

    (The folder name matches your `server.identity` convar.)
  </Step>

  <Step title="Delete the map files">
    Delete the `.map` and `.sav` files, for example:

    ```
    proceduralmap.4500.1847520.264.map
    proceduralmap.4500.1847520.264.sav
    ```

    Older `.sav` backups of the same map can go too.
  </Step>

  <Step title="Optionally change the seed">
    For a brand-new map layout, change `server.seed` (and/or `server.worldsize`) in the **Startup** tab. Keeping the same seed regenerates the identical map, just empty. See [server configuration](/games/rust/server-configuration).
  </Step>

  <Step title="Start the server">
    Start the server. It will generate a fresh map — expect several minutes of map generation before players can join.
  </Step>
</Steps>

## How to Perform a Blueprint Wipe

<Steps>
  <Step title="Stop the server">
    Stop the server from the panel.
  </Step>

  <Step title="Delete the blueprint database">
    In `/server/my_server_identity/`, delete the blueprint database file(s):

    ```
    player.blueprints.5.db
    ```

    The number in the filename is a data version and may differ — delete any `player.blueprints.*.db` files present.
  </Step>

  <Step title="Start the server">
    All players will start with default blueprints on next join. BP wipes are usually done together with a map wipe.
  </Step>
</Steps>

<Note>
  Other `.db` files in the identity folder (`player.deaths.*.db`, `player.identities.*.db`, etc.) hold stats and identity data — leave them alone unless you intentionally want a "full wipe." Oxide plugin data in `/oxide/data/` is separate and survives wipes unless you clear it (some plugins, like Kits with saved cooldowns, may need their data reset on wipe).
</Note>

## Automating Wipes with Schedules

The Game Panel's **Schedules** feature can automate the routine: schedule a stop, file deletion (via schedule tasks/commands where available), and restart at your wipe time — or at minimum schedule a warning broadcast (`say "Wipe in 15 minutes!"`) and the restart, then delete the files manually. Combine it with a scheduled backup right before the wipe for a safety net.

## Communicating Your Wipe Schedule

Players pick servers based on wipe timing. Advertise yours everywhere:

* In `server.hostname` — e.g. `[EU] Wasabi 2x | Weekly Wipe Thu | JUST WIPED`
* In `server.description` — exact day, time, and timezone, plus BP wipe policy
* Keep it consistent — an unpredictable wipe schedule is the fastest way to lose a player base

<Card title="Wipe-day performance matters" icon="rocket" href="https://wasabihosting.com/game-servers/rust">
  Wipe day means max pop and fresh map generation — exactly where Ryzen X3D CPUs shine. Rust hosting from €9.99/month at Wasabi.
</Card>