
How to recover a Rust world after its custom map link stops working
If the old map link is gone, recover the exact .map file that belongs with the save. Publish it at a new direct download address that a first-time player can reach, and verify those two files together before changing the live server.
Get the exact map from storage you control
Look for the map beside the dated game backup or in the original map files. Compare its revision with the saved world's notes. If you cannot identify the original map, ask the author or the person who prepared that wipe for the exact file. A differently revised map with a similar filename is a new candidate, not a confirmed replacement.
Put the recovered file in a web location permitted by the map's sharing terms. Keep the matching filename from the working map and verify that the new URL downloads the map itself from another network. A link that opens a preview page or needs the owner’s browser session will fail for someone without that session.
Test an unchanged save against the replacement download
On an isolated compatible copy of the world, use the new address as server.levelurl. Copy the matching save into the test identity without placing the old map in the test cache. Keep the primary save and archive intact. Separate the test ports and storage and disconnect live plugin services and scheduled work. Start the test game and use its startup output to confirm Rust fetched the replacement URL.
Join from a Rust client without that map cached. Check the client console shows the new download URL. Then confirm the intended terrain and a named structure from the saved world. If Rust loads a blank world or mismatched terrain, keep the main server unchanged and check the pairing and game build before proceeding.
Once the new link and old world pass, record the replacement address beside the original archive. Use the normal maintenance window to apply it to the intended server and verify a fresh join there too.