
How to test an existing custom map after a Rust update
Try the map on the updated server in a test instance. Check places that matter to your players even if the map loads without stopping the game.
Record a route that worked before the update
Pick one important route, such as reaching the loot room through a door and ladder. Record the game build, map filename and version, and what the player had to do. If the game is already updated, use a screenshot or a player's earlier account to establish what they expect without assuming you can still boot the previous build.
Read the official release notes for changes relevant to that route. Facepunch documents that a custom map can refer to a game asset that no longer exists. If your map author has already sent a revision, keep both files and give the new one a distinct filename and direct download URL.
Change one part of the test at a time
Use a separate empty test instance. Check the current map with the updated server and client before changing the framework or testing a new map file, if the old setup is compatible. Keep production integrations disconnected. If a route depends on a plugin, verify the matching framework build separately before enabling the plugin on the test.
| What happens on the current build | What to try next |
|---|---|
| The old map loads but the ladder is gone | Read the missing asset errors and check the same route on the map author’s revision. |
| The route works until the route-control plugin is active | Compare the plugin and framework versions and their startup errors. |
| The new map worked for staff, a first-time client cannot join | Check the direct map download from that client’s network. |
Tell the map author exactly what failed
Join from a client that has never cached the revised filename. Follow the route all the way to its intended reward or exit. Record the location and first relevant error if it fails. Keep the existing live map and save intact while you choose a corrected candidate. If the new map works only with a clean world, check separately what players would lose before you put it live.