“Wait, is everything gone?” is a rough way for a player to discover your wipe policy.
A wipe is part of running a Rust server, but that word gets used for different resets. Spell out what changes, what stays and when it happens. The announcement matters almost as much as the maintenance.
A map wipe and a blueprint wipe are different resets.
A map wipe clears the world save, including player buildings. A blueprint wipe clears learned crafting blueprints. A restart by itself is neither. Tell players exactly which reset you mean, and check Facepunch’s update notes before promising what will carry over.
Rust for PC“Fresh wipe” needs a little more detail
The map save holds the built world and its entities. Blueprint progress lives in a separate file. That separation is why an announcement should say whether blueprints are included.
Don't assume a routine restart means a fresh world. If a server unexpectedly looks empty, check that it loaded the intended identity and save before treating the old world as lost.
For players, the useful question is simple: what will still be here when I log back in? Put that answer near the top of the announcement.
Leave room for Facepunch’s update
A forced wipe can change the save protocol so the server creates a new save instead of loading the old one. Facepunch's server guide warns against renaming an old save to get around it.
Blueprint policy can also change. In November 2025, Facepunch announced a game-wide blueprint wipe and said it was not yet committing to a permanent monthly policy. That is a good reason to read the current update notes rather than repeat an old rule as a guarantee.
For your own server, publish the schedule you control and explain that required game updates may change the plan. This guide covers PC Rust; use the announcements for the edition you're actually running.
Write the announcement before touching files
Give an exact date, time zone, reset type and an estimate for downtime. If the map seed or size will change, say so. Put the same information in the places your players already check.
For example: “Map wipe on Saturday, October 10 at 2 p.m. America/Chicago. Blueprints stay unless the game update requires otherwise. New seed, same group rules. We will post again when joining is open.” That is a sample announcement, not a Sculk server schedule.
Choose the pace around your group. People playing a few evenings a week may want longer with their builds. A group that enjoys racing through a fresh start may prefer shorter rounds. Ask before the schedule becomes a surprise.
Keep wipe day boring
Before maintenance, save and shut down the server cleanly. Keep a complete backup of the server identity folder, configuration and any plugin data. Label it with the date and game build. A folder named “backup-final-new” is a small problem waiting for its moment.
Use the procedure for your host and current setup. Avoid a blanket deletion of the server folder: configuration, admin settings and other data are not all part of the reset you announced. Facepunch's file guide explains what the identity folder contains.
After the update and intended reset, join and check the map, rules and expected blueprint state. Confirm the plugins you depend on still work. Only then tell the group it is ready.
Keep the backup even after the new world starts. It may help recover settings or investigate a mistake, but it is not a promise that an old save will run on a newer game build.
Sources & useful links
The technical details behind this guide, if you want to dig further.
Keep reading
Sculk Hosting
Stuck on your own setup?
Send us the game version and what happens when you try. A log or error message helps.