Skip to main content

Which custom map file should you keep with a Rust backup?

Keep the exact .map file that went with the .sav, as well as its filename and download URL. The URL can keep working while the file behind it changes.

Put the map file beside the restore point

Keep the exact .map file, its matching .sav, and a small readme with the backup. Add the map filename, download URL, game build and the wipe that first used it. If the download location uses an access link that expires, record where you own the original map file so you can publish a working link when needed.

For example, Harbour’s map author sends a winter revision under the same filename as the autumn map. Store the autumn file beside the autumn backup and give the winter revision its own name at a new URL at the next planned wipe. Facepunch describes how the Rust client can reuse a map it has already downloaded by filename.

Check what a player who has never downloaded it sees

First confirm you can open the backup from separate storage and extract both files together. For a restore exercise, put the exact map at a direct download URL and use its original matching filename with the save. Start a private test world using a compatible game build and its own ports. Keep live bots, scheduled jobs and shared plugin data disconnected.

Try a client that has joined before and a client on another network that has never loaded this map. If the returning client loads in but the new one cannot download, check the new client's console for the exact map URL. Confirm it opens the map file from their network. Once the new client joins, have them find both a landmark and a known player structure. The landmark checks the map and the structure checks the saved progress.

Keep a recovery note with the pair

Write down the date, filename, backup location and what the new client verified. If they do not see the known structure, keep the test isolated and identify the correct pair before using it to recover the shared world.

Sources

Analytics settings

Analytics are off.

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