Skip to main content

A Rust wipe stopped halfway. What should you check first?

Identify the last step that definitely finished. A wipe might have stopped before reset, after removing the old save, or after the new world began loading.

Preserve what you can still inspect

Pause future runs for that wipe. If a run is still active, let it finish or follow the wipe tool’s recovery instructions before changing files. Keep the pre-wipe copy and read the wipe tool's run result and the game console. Before taking a manual copy of any new save, stop the game and any other process writing to those files. Keep the new state separately from the pre-wipe copy.

Finish the smallest step your evidence supports

Correct the named problem first. If the reset completed and only startup failed, check the startup error and the intended map settings, then start the game without sending another wipe. If you cannot establish what was removed, leave the live world closed while you compare the current files with the expected result or ask the host for the failed step. Reopen after joining the expected world and confirming the wipe scope.

Finish the smallest step your evidence supports
What you can establishNext check
Game stopped, old save remainsCheck whether the wipe recorded a failed prerequisite before it reached reset.
New save exists, game won’t loadRead the startup error and verify the expected map settings.
Tool and files disagreeKeep both copies and get the failed stage confirmed before another write.

Sources

Analytics settings

Analytics are off.

Help improve RustSC with page counts and performance measurements. Privacy details