
What to check before sharing your new Rust server address
Hold the announcement until someone outside the new host's network can join the intended world. A server that accepts connections can still be running with fresh world data or missing settings.
Choose what needs to arrive on the new host
Write down the current server identity, map or map URL, game version and the player data or plugins you intend to keep. Back up the settings and data before the move. If you are keeping the live world, stop the old server for the final copy so players cannot make more progress there while you move it.
On the new host, use the intended identity folder and map settings. For a move mid-wipe, pick an existing base or landmark and an account with a known learned blueprint. If the move coincides with a planned wipe, record which progress you expect to reset so the tester knows which changes to expect.
Send the join instruction to one tester first
Ask someone outside the host network to paste the exact new connect instruction into F1. Have them check the expected world and one thing you meant to carry over, such as that blueprint. If you advertise the server through the browser, have them find it there and join from the entry as well.
Once the checks pass, replace the join instruction in your Discord pins and other places players look for it. If a check fails, hold the announcement and keep the old server data available while you correct the copy or connection.