V Rising: Server Recovery & Backup Restoration
Whether it's a base-raiding disaster, a corrupted file, or a change of heart after a major PvP engagement, knowing how to manually restore your V Rising server to a previous state is a vital skill. V Rising takes automatic snapshots of your world every 10–30 minutes, stored as numbered "Autosave" files.
1. The Save Structure
V Rising saves are stored as .save.gz files. The server always tries to load AutoSave_0.save.gz by default. Restoring is simply the act of replacing "0" with an older file.
2. Finding the Right Time
Inside the saves directory, the Timestamp column in your file manager is your best friend. Look for the file created closest to the time before the disaster occurred.
3. Directory Naming
On Supercraft servers, your world data is typically found in a folder named IndifferentBroccoli (our internal technical identifier). Do not rename this directory!
How to Manually Restore an Autosave
- Login to your Supercraft Panel and Stop the server.
- Open the File Manager.
- Navigate to the following directory:
/saves/v3/IndifferentBroccoli/. - Locate the files matching your current Session ID.
- Example:
AutoSave_45.save.gz,AutoSave_46.save.gz, etc.
- Example:
- The Critical Step: Find the current
AutoSave_0.save.gzand rename it toAutoSave_0_OLD.save.gzas a backup. - Select the older save you want to restore (e.g.,
AutoSave_42.save.gz) and rename it to AutoSave_0.save.gz. - Go to the Console and click Restart. The server will now load the state from your selected backup.
Ensuring Success: Common Pitfalls
| Problem | Solution |
|---|---|
| Server starts a NEW world | Ensure you named the file exactly AutoSave_0.save.gz (Case sensitive!). |
| Progress didn't change | You may have restored an autosave that was taken after the event you wanted to reverse. Try an older number. |
| Metadata Mismatch | Each save has a corresponding SessionId. Do not move saves between different world folders. |
Note for 1.1 Update: If you are running the latest experimental build, the file path might be found in /v3_stable/ instead of /v3/. The logic for renaming remains identical.
Master the art of temporal management. View plans.