Server Wipe Schedules Explained: Map, Blueprint and Full Wipes
A wipe resets some or all of a server's progress so everyone starts fresh. A map wipe resets the world and bases, a blueprint (progression) wipe resets what players have unlocked, and a full wipe resets both. How often you do it is the biggest single decision shaping what your server feels like.
This guide explains why servers wipe, what the different wipes actually delete, how communities pick a schedule, and how to announce it so players come back instead of drifting off.
- Map wipe = new world, progression kept. Blueprint wipe = progression reset. Full wipe = both.
- Some games force the issue: Rust's monthly update forces a map wipe. In others (7 Days to Die), save-breaking updates occasionally force a new world.
- Weekly wipes suit fast, fresh PvP. Monthly or longer suits builders and long progression. Pick based on how long your players take to reach endgame.
- Announce your cadence and policy in the server name or description, and warn players days ahead.
- Back up before you delete anything, and check your plugins and permissions afterwards.
On this page
Why survival servers wipe
Survival games are built on progression: gather, build, defend, expand. Left alone, a server reaches a steady state where the big bases are established, the resources near spawn are long gone and new arrivals have nothing to do but fight established players. A wipe resets that. The common reasons:
- Fairness for new players. A fresh start puts everyone on the same footing, which keeps population healthy.
- Pacing. Players enjoy the early and mid game most. A wipe lets them replay it.
- Game updates. New content, changed world generation or changed save formats sometimes make old worlds obsolete or incompatible.
- Server health. Very large, long-lived worlds with many objects can load slower and use more resources. A wipe is one fix, though trimming the world is another.
Map wipe vs blueprint wipe vs full wipe
| Wipe type | What resets | What stays | Typical use |
|---|---|---|---|
| Map wipe | The world, bases, containers, loot, resource nodes | Learned blueprints/unlocks, permissions, plugin data | The routine, frequent wipe |
| Blueprint / progression wipe | What each player has researched or unlocked | The map, if you don't also wipe it | Occasional; usually paired with a map wipe |
| Full wipe | Map and progression (plus often player data) | Server configuration, permissions, plugin settings | A clean slate: season starts, big updates |
| Partial reset | A single area or world, such as a resource or event world | The main world | Keeping long-term builds while refreshing resources |
In Rust, these map to different files in the server's identity folder (server/<identity>/). A map wipe removes the .sav and .map files and leaves player blueprints; a blueprint wipe removes the .db files; a full wipe removes both. Other games name and organise save files differently, so check your game's save layout before you delete anything.
Partial resets are common in games with several worlds or dimensions; for example, many Minecraft servers refresh a dedicated resource world on a schedule and leave the main world alone. That is community practice rather than a game feature, but it solves the same problem without erasing anyone's home.
When the game forces a wipe
Some games leave the schedule entirely to you. Others set a floor.
- Rust: Facepunch's monthly update lands on the first Thursday of each month, at 19:00 London time (2 pm US Eastern), and forces a map wipe on every server. Whether to also wipe blueprints is the owner's choice; Facepunch announces blueprint wipes when it changes systems that require one. Several host guides agree on this schedule, but confirm the exact date and time against Facepunch's own announcements each month.
- 7 Days to Die: There is no scheduled wipe. Occasionally a game update changes terrain generation, chunk format or save structure so old worlds won't load properly. The community wiki's advice is to read the patch notes for "requires new world" warnings, back up the whole Saves folder before updating, test on a spare instance, and record which game version each world was created in.
- Minecraft and Valheim: Neither imposes a periodic wipe, and worlds can last for years. Updates can still change the world format: Paper says a world upgraded to Minecraft 26.1 can't go back to an earlier version, which is one more reason to back up before updating.
If your game forces a wipe, your remaining choice is what to wipe on top of it and how you present it. Players on forced-wipe games already expect resets, so your cadence is the main thing they compare servers on.
How communities choose a wipe schedule
The right cadence depends on how long it takes your players to do what they enjoy. Ask: how many days does it take a typical player to reach the late game? How big are the bases you want to see? How many sessions per week do players manage? Common patterns (using Rust as the example, since its schedule is well documented):
| Schedule | How it works | Suits | Trade-off |
|---|---|---|---|
| Weekly map wipe | Map resets every 7 days, blueprints kept until the monthly wipe | Fast-paced PvP, players who want constant freshness | Bases rarely mature; heavy admin load; players who miss a week fall behind |
| Biweekly | Map resets every 14 days | A balance of fresh starts and time to build | Fewer wipe-day crowds than weekly |
| Monthly (force-wipe aligned) | Only the forced monthly wipe | Builders, PvE-leaning and relaxed communities | Slower to feel fresh for late arrivals, and quieter late in the cycle |
| Custom or seasonal | Whatever your community agrees on | Roleplay, events, themed seasons | Players have to learn your calendar |
One host's guide calls weekly the most popular cadence for Rust and notes that force-wipe day is typically the busiest day of the cycle, so a monthly wipe timed to it can bring players back. The right answer for you is your own population: if your server is small and quiet, wiping more often won't create players. If you have a base of regulars, ask them.
How to run a wipe safely
The steps below use Rust as the example because its files are well documented. Check your own game's save layout first.
- Announce it
Post the date, time, type of wipe (map only or map plus blueprints) and any required updates in Discord and the server description.
- Update the game and your mod framework
On Rust, the monthly update can leave Oxide or Carbon needing a new build. Update them before players return, and check for plugin errors afterwards.
- Stop the server and back up
Stop it first, then copy the whole identity folder. Deleting files on a running server can corrupt what remains, and there's no undo.
- Delete only the files for the wipe type
For a Rust map wipe: the
.savand.mapfiles. For a blueprint wipe: the.dbfiles. Optionally change the world seed for a new layout. - Start and check the console
Watch for plugin compile errors and a successful world generation. Join yourself before announcing it's live.
- Announce that it's live
Update the server description or countdown and post the all-clear.
If you run a Rust server, that makes the cycle quick, but the process above applies to any host.
Announce it well and protect returning players
- Put the cadence in the server name or description. Players filter on it. A label such as "Weekly map wipe, monthly BP wipe" tells them most of what they need.
- Say what resets. The most-asked question is whether blueprints are wiped. Answer it up front.
- Give notice. A few days is the norm; announce again on the day. Surprise wipes lose players.
- Keep permissions and donor perks intact. On Rust, Oxide and Carbon permissions and groups live in the data folder and generally survive map and blueprint wipes. After a wipe, check that VIP groups and kits still work. If you sell perks, say whether they persist across wipes.
- Help returning players restart. A starter kit, a short welcome message or a pinned guide to the new cycle helps people who've been away.
- Help players use their last session. Remind them to spend resources, screenshot builds they want to recreate and make a team plan for the first hour.
- Keep the pre-wipe backup for a while. If the wipe goes wrong, or players ask about the old map, you can still get at it.
A wipe schedule works when it's predictable. If you change it, announce the change as clearly as you'd announce a wipe.
Frequently asked questions
What is the difference between a map wipe and a blueprint wipe?
A map wipe resets the world, bases and loot but players keep what they've learned. A blueprint wipe resets those unlocks so everyone researches from scratch. A full wipe does both.
How often does Rust force a wipe?
Facepunch's monthly update arrives on the first Thursday of each month and forces a map wipe on every server. It is at 19:00 London time, which is 2 pm US Eastern. Blueprint wipes are at the owner's discretion unless Facepunch announces one.
How often should I wipe my server?
It depends on how long your players take to reach endgame and how long you want bases to last. Weekly or biweekly suits fast PvP, while monthly or longer suits builders. Choose a cadence, announce it, and keep to it.
Will I lose my plugin settings and permissions when I wipe?
Usually not for a map or blueprint wipe, because plugin configuration and permission data live in separate folders from the world files. Check your groups and perks after the wipe, and take a backup before you delete anything.