Nexardo

Rust Field guide

Test a custom Rust map before wipe day

Verify a custom Rust map (.map) on staging before wipe day: download URLs, navmesh generation, player spawns and monuments.

EugenePublishedUpdatedReading time3 min
Test a custom Rust map before wipe day

Deploying a custom map (.map file) directly on wipe day frequently derails a server launch: download URLs may fail external validation, navigation meshing can freeze on misconfigured monuments, and players might spawn under terrain or out in the ocean. A structured staging verification plan eliminates these surprises before public opening.

This guide targets Linux dedicated server administrators. As of October 27, 2026, custom Rust maps are loaded via the -levelurl command-line argument, which requires direct HTTP/HTTPS binary access without interactive landing pages.

Validating direct map download links#

Both the dedicated server process and connecting clients download the .map file from the specified URL. If that link directs to an interactive preview page (common with standard Google Drive, Dropbox, or OneDrive sharing links), downloads stall or fail entirely.

Test the URL from an external Linux machine using curl:

bash
curl -I -L "https://maps.example.com/wipes/island_v4.map"

Verify three crucial response header conditions:

  1. The final HTTP response status is 200 OK.
  2. The Content-Type header reflects application/octet-stream or binary stream data.
  3. The Content-Length header matches the exact byte count of your local .map file.

If your web server returns text/html, Rust clients will abort connection attempts with Checksum mismatch or Disconnected: Disconnected.

Launching an isolated staging instance#

Never test an unverified map against your production server directory: if arguments write to an existing server.identity, you risk corrupting or wiping your active world state prematurely.

Launch a disposable staging instance bound to an alternate port and isolated identity:

bash
./RustDedicated -batchmode \
  +server.port 28025 \
  +server.queryport 28026 \
  +server.identity "staging-maptest" \
  +server.level "CustomMap" \
  +server.levelurl "https://maps.example.com/wipes/island_v4.map" \
  +server.maxplayers 10

Monitor console output during boot. The server must retrieve the archive, parse the header signature, and begin navmesh baking. If console warnings report Prefab not found or enter an infinite Navmesh generation stuck loop, the map creator used obsolete, corrupted, or unsupported prefabs.

Step-by-step verification plan: direct link checks, staging instance boot, navmesh observation, in-game monument review, and real client download tests.

Reviewing monuments and spawn points in-game#

Once the staging console prints Server startup complete, join the instance as an administrator via the F1 developer console: connect 198.51.100.10:28025.

Execute this essential pre-wipe checklist:

  1. Player spawn points: Execute kill in console 3–4 times. Verify that you respawn safely on coastal beaches or designated spawn zones, rather than below mesh geometry or out in deep water.
  2. Monument aerial inspection: Enable noclip. Fly across both custom and standard monuments (Airfield, Sphere, Military Tunnels).
  3. Card puzzles and electrical circuits: Test backup generators, door switches, and green/blue/red keycard readers. Overlapping collider boundaries in custom prefabs frequently break electrical circuit logic.
  4. Loot crates and AI patrols: Ensure military crates, barrels, and scientists spawn in expected zones without falling through floors.

Testing real client download performance#

Have a staff member or moderator join the staging server from an external home network.

Confirm that:

  • The game client displays the "Downloading Map" progress bar smoothly.
  • Download time for a typical 30–60 MB map completes within 15–30 seconds over standard broadband.
  • Upon entering the world, the client renders terrain properly without black ground textures or invisible barriers.

Only after passing every item on this checklist should you update your production startup script for scheduled wipe night.

If you manage your gaming server fleet through Nexardo, maintain dedicated staging profiles for wipe testing: isolated verification environments safeguard production stability before peak player influx.

Sources#