Skip to main content

Prove a Rust backup belongs to the right world

A healthy archive can belong to the wrong world. Match its origin and date before restoring, then check something only the intended world should contain. Start with a spare destination and keep live files untouched during this check.

Use three independent clues

For example, Alder runs Weekly and Monthly with a similar seed. Two backup names might both say ‘Thursday’. Record the clues from your own inventory.

Use three independent clues
ClueWhat to compare
OriginThe named source server, its host and its Rust server identity. The displayed name alone can be reused.
World detailsThe backup date and time, expected map or seed and size, and the wipe that was active then.
Recognizable player stateA location, construction or other agreed marker that existed at the requested time and belongs to this world.

Open the strongest candidate in isolation

Use your backup tool's read or preview if available. Export or restore to a new destination using the supported procedure. Give the test server its own endpoints and restrict it to testers. Keep live Discord, shared plugin stores and Rust+ out of the test. Start it only after you have checked those boundaries.

Join with a trusted tester. Confirm the expected map and marker, such as a staff-built sign that only appeared in Monthly before the last wipe. If the map matches but the marker does not, check another clue from that date or try the next candidate. Similar seeds can regenerate a similar map without your actual progress.

Record which copy earned approval

Write the source, capture time, marker and what progress the selected backup would omit. A private Debian rehearsal backed up several different seeds and correctly refused an in-place restore for the wrong seed. That check distinguishes different maps. Your marker and records help identify worlds that intentionally share a seed. Keep live recovery on hold if the origin or game state is still uncertain.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details