Rust wipes: map resets, blueprints and server restarts

In Rust, a wipe usually means resetting part of server progression. Map data and learned blueprints are stored separately: Facepunch documentation distinguishes world data from player.blueprints. A map-wipe announcement should not automatically be read as removal of every learned recipe.

Before returning, establish what resets. Announcements may use Map, BP or Full, but confirm their practical meaning in server rules. This affects whether a team must relearn required items or focus mainly on resources and a new base.

Map wipes and blueprint wipes

The map save contains world state, including buildings, deployables and other entities. Blueprints represent learned crafting capabilities. This explains a familiar situation: the base is gone, but some items remain craftable. That is not necessarily a server error.

Previously retained recipes are not a promise of permanent retention. Administrators may schedule a separate BP wipe. Read the current cycle’s announcement rather than relying on an old server name. When wording is unclear, ask whether learned recipes reset instead of debating the label Full.

A restart is not automatically a wipe

A server may go offline for updates, maintenance or a routine restart. Reconnecting alone does not prove the world reset. Compare the administrator announcement, map state and availability of previous objects after joining.

A queue or required client update can accompany different events. If data appears missing after a restart, check that you joined the correct server: similar names and multiple servers from one community are easy to confuse. Keep the exact name, time and description of the change for a support request.

Finding the date and time zone

Facepunch documents Monthly, Biweekly and Weekly tags and a configurable wipe timer. Timer settings include day, hour, time zone and an exact-time override. A general tag therefore cannot replace a specific server announcement.

Check date, time and time zone. Thursday evening is insufficient for players in different regions. Put converted local time in the team calendar and keep the source link. If the schedule changes, update the existing entry instead of creating conflicting reminders.

Prepare for the next cycle

Agree on server, start time and reset scope before assigning team tasks. Do not plan around an old base when the world is being reset. Track blueprints separately as confirmed retained, confirmed reset or awaiting clarification, so uncertainty does not become a shared false expectation.

If considering additional products in the Rust section, check their status after updates independently of server timing. A new wipe cycle does not prove software compatibility with the updated client. Ordinary wipe planning requires the server’s announcement and rules.