We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Check out our current game server offerings.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!
Guide

Server Wipe Schedules Explained: Map, Blueprint and Full Wipes

By the ChicagoServers team · Updated · 8 min read

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.

Quick answer
  • 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 (Backups tab), and check your plugins and permissions afterwards.
On this page
  1. Why survival servers wipe
  2. Map wipe vs blueprint wipe vs full wipe
  3. When the game forces a wipe
  4. How communities choose a wipe schedule
  5. How to run a wipe safely
  6. Announce it well and protect returning players
  7. Frequently asked questions

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 typeWhat resetsWhat staysTypical use
Map wipeThe world, bases, containers, loot, resource nodesLearned blueprints/unlocks, permissions, plugin dataThe routine, frequent wipe
Blueprint / progression wipeWhat each player has researched or unlockedThe map, if you don't also wipe itOccasional; usually paired with a map wipe
Full wipeMap and progression (plus often player data)Server configuration, permissions, plugin settingsA clean slate: season starts, big updates
Partial resetA single area or world, such as a resource or event worldThe main worldKeeping 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 player.blueprints.*.db files; a full wipe removes both. On ChicagoServers, Rust's Wiper tab does these wipes for you (map, blueprint, player data and plugin data wipes), so you rarely need to delete files by hand. Other games name and organize 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, usually around 19:00 London time (about 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):

ScheduleHow it worksSuitsTrade-off
Weekly map wipeMap resets every 7 days, blueprints kept until the monthly wipeFast-paced PvP, players who want constant freshnessBases rarely mature; heavy admin load; players who miss a week fall behind
BiweeklyMap resets every 14 daysA balance of fresh starts and time to buildFewer wipe-day crowds than weekly
Monthly (force-wipe aligned)Only the forced monthly wipeBuilders, PvE-leaning and relaxed communitiesSlower to feel fresh for late arrivals, and quieter late in the cycle
Custom or seasonalWhatever your community agrees onRoleplay, events, themed seasonsPlayers 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 and ChicagoServers has a Wiper tab for it. Check your own game's save layout first.

  1. 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. The Server name and Description fields on the Startup tab are where players read them in the server list; click Save startup and Restart to apply.

  2. Update the game and your mod framework

    On Rust, the monthly update can leave Oxide or Carbon needing a new build. Click Update now on the Steam update bar when an update is out, then use the Plugins tab to update the framework and plugins (or tick Update uMod when the server starts on the Startup tab). Update them before players return, and check for plugin errors afterwards.

  3. Stop the server and back up

    Click Stop at the top of the page, then open the Backups tab and click Back up now. Whole server backs up everything; World and settings covers saves, configs and mods. Deleting files on a running server can corrupt what remains, and a backup is your undo.

  4. Run only the wipe you intend

    Open the Wiper tab and choose the wipe type: map, blueprint, player data or plugin data. For reference, a Rust map wipe removes the .sav and .map files, and a blueprint wipe removes the player.blueprints.*.db files. To change the layout, set Map seed (or Map, World size) on the Startup tab and click Save startup.

  5. Start and check the console

    Click Start and watch the Console tab for plugin compile errors and a successful world generation. Join yourself before announcing it's live.

  6. Announce that it's live

    Update the server description or countdown and post the all-clear.

To run a wipe on a timetable, open the Schedules tab, click Add a scheduled task, name it and choose When (Chicago time). Add steps with Add a step, for example Send console commands (a warning to players), Wait 5 minutes, Make a backup, then Install a game update (a Rust wipe, uMod and others), and click Add task. Tasks are listed on the same tab with Run now, Edit, Turn off and Delete. If you run a Rust server with us, that makes the cycle quick; 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. Plugin data is its own wipe on the Wiper tab, so only run the wipes you mean to. 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. Star it on the Backups tab so it isn't replaced.

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 usually goes live around 19:00 London time, which is about 2 pm US Eastern, but check Facepunch's announcements for the exact time. 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. On ChicagoServers, plugin data is a separate wipe on the Wiper tab, so only run the ones you mean to. Check your groups and perks after the wipe, and take a backup before you wipe.

We are your new 5-Star Hosting Company. At least according to ★ Trustpilot

Check out our current game server offerings.

All servers come with a 24-Hour Trial, Free Backups, and 40Gbps DDoS Protection included!

We offer quality support, a detailed knowledgebase, video tutorials on most topics, and even live support in case you prefer a live human.

Use code SAVE15 to take 15% OFF Your First Invoice with ChicagoServers! Limited Time!