Rust force wipeDates, the force wipe and your own wipe cycle

Published on August 4, 2026 · last updated on November 8, 2026

What is the force wipe?

On the first Thursday of every month, Facepunch Studios releases the big monthly update for Rust - the so-called force wipe. Because this update changes the network protocol and procedural map generation, old saves are no longer compatible: every Rust server has to wipe its map on that day. The update usually arrives in the evening, typically around 8 to 9 p.m. German time. The next date is expected to be Thursday, December 3, 2026.

Between the monthly updates, there are weekly patches (usually on Thursdays). They do not force a wipe - only the monthly update on the first Thursday does.

Map wipe vs. BP wipe

Not every wipe is the same. There are two levels:

• Map wipe: The map is generated again, and all bases and placed objects disappear. The force wipe always forces a map wipe.
• BP wipe (blueprints): In addition, the learned blueprints of all players are reset - everyone starts from zero again. A BP wipe is optional and your decision.

Technically, you control this via the files that get deleted in the server identity folder: the *.map and *.sav files concern the map, while the blueprint data lives in the player.blueprints.* data files. In the web interface, you pick prepared profiles with the one-click wipe.

When a BP wipe makes sense, which rhythms have proven themselves and when it is more likely to drive your players away is covered in its own guide, Wipe blueprints.

Trigger a wipe with one click

This is how you wipe at MainHoster.de:

1. Open the wipe or reinstall function of your Rust server in the web interface.
2. Choose the wipe type: map wipe only or map wipe including BP wipe.
3. Optional: set a new server.seed or keep the existing seed.
4. Confirm - the server deletes the selected files and restarts with a fresh world.

If you want the same map at every wipe, enter a fixed seed and worldsize. Without a fixed seed, the server generates a new map at every map wipe.

Which wipe cycle fits my server?

The wipe rhythm shapes the character of your server. Common models:

• Monthly (force wipe only): Calm progression, large bases, long-lasting progress - ideal for PvE and relaxed communities.
• Every two weeks: A popular middle ground - a fresh start at regular intervals without progress evaporating too quickly.
• Weekly: High pace and recurring early-game action - a good fit for 2x/5x and active PvP servers.

Many servers communicate their cycle openly (for example "Wipe: Thu + Sun") and add extra map wipes without a BP wipe between the force wipes, so blueprints last until the end of the month. Automate recurring wipes with the task scheduler in the web interface.

What survives a wipe

Not everything disappears with the map. Knowing this split saves you half the work on wipe day - and keeps you from setting up things again that are still there:

The last point is regularly overlooked: everything a plugin has stored as coordinates - zones, markers, event points, saved base templates - points into nowhere after a new seed. That kind of data should be reset at the wipe, otherwise an event triggers in the middle of the water or a protected area sits on top of a mountain. Where these files are located is explained in Install & configure plugins.

Conversely: because ownerid, moderatorid and bans survive a wipe, you do not need to add your team again afterwards. Anyone who suddenly has no rights anymore never saved them permanently in the first place - that is not a wipe problem.

The routine on wipe day

The monthly update reaches all servers at the same time, and the ones that are playable again first get the players. A practiced routine is therefore worth more than rushing:

1. Back up first. Download the plugin folder, configurations and server.cfg. With us, backups are self-service across the board via WebFTP or SFTP, see Create backups.
2. Announce it. Mention the time in the description, chat and Discord, see Server name & description.
3. Wait for the update. Wiping before the rollout achieves nothing - the map would have to be generated a second time afterwards.
4. Update the framework. Oxide or Carbon has to match the new game build, otherwise not a single plugin will start.
5. Check the plugins. After the start, check which plugins are actually loaded - not which files are in the folder.
6. Update the server name. If the next wipe date is in the name, now is the time to update it.

Expect waiting time that is out of your hands: both the framework update and the adjustment of individual plugins are done by third parties. If you want to be ready to play right away on wipe day, a lean plugin list serves you much better than forty extensions, each of which can delay the start. A vanilla server is unbeatable in this respect - it is back online as soon as the update is through.

Frequently asked questions