跳到主要内容

How to Host a Custom Map on a Rust Server

Rust downloads a custom map from a URL when the dedicated server starts. Players who join also need to be able to download the map from that URL. This guide covers the Rust server startup setting for one custom .map file.

Before you begin​

  • Have a custom map file and a public direct-download URL that will stay available.
  • Have access to the Rust server's startup arguments.
  • Back up the server before changing maps. Plan the change for a fresh map or wipe: carrying an old save onto different terrain can leave bases and other entities in the wrong places.

Check the map URL​

Open the URL in a browser. It should start downloading the .map file directly without requiring a sign-in or another click. A public release download can work; a page that only displays the map does not.

Keep the file at a stable public URL. New players download it from that URL when they join, so an unavailable link can prevent them from connecting.

Configure the server​

  1. Stop the server and make a backup of its current files.

  2. In the server's startup arguments, add +server.levelurl with the direct-download URL:

    +server.levelurl "https://example.org/maps/my-map.map"

    Replace the example URL with the real map download URL.

  3. Remove +server.seed and +server.worldsize from the startup arguments. Those settings are for procedural maps.

  4. Save the startup settings and start the server. Check the console for a map download or loading error.

Verify the map​

Join the server and check that the intended terrain loads. Then have a player who has not joined this map before connect. Their client must be able to download the map from the same public URL.

Troubleshooting​

  • The server cannot download the map: open the URL in a browser again and confirm that the download starts directly and does not require an account.
  • New players cannot join: check that the map file remains publicly reachable. The server does not send this map file to clients from its own storage.
  • The server loads a procedural map: confirm that +server.levelurl is in the startup arguments and that +server.seed and +server.worldsize have been removed.
  • The new terrain does not match the old save: stop the server and restore the backup. Apply the custom map at a planned fresh map or wipe instead of reusing the old terrain save.

Sources​