
What will a Rust management tool tell you when a wipe fails?
Ask for a safe demonstration using a disposable world. You want an answer to three questions after something stops: which world, which change and where to see what happened. Check the tool can still show you that after you close and reopen it.
Pick a failure that costs you nothing
Ask the seller for a demonstration of a rejected wipe or use a new test world containing no progress to preserve. If the workflow supports custom maps, you could ask them to demonstrate what appears when a test map cannot be downloaded. Facepunch documents distinct connection and file failures for custom maps. A completed attempt to change the world with a failed return to play is a useful example to ask about.
Write down the expected failure and the world you intend to use. Keep live worlds, live integrations and recurring wipe jobs out of the exercise. If the tool says it accepted the request, wait for a final result or check the host state before doing anything again.
Read the result as the next person on duty
Close and reopen the tool. Find the attempted wipe by world name and time. Check whether you can tell if it stopped before changing the world or after making part of the change. If the result points to a startup log, open it and find the relevant line. Join the test server if it is actually accepting players.
Keep a note such as “Dunes, 18:10 UTC. New map URL set, startup failed retrieving the file. Panel shows the failed start. The previous test map is still in our separate copy.” If the demonstration only gives you a generic failure, ask where else you would verify which files and settings changed. Decide if you can use that fallback during your real maintenance window.