# Agrarian MVP Save Recovery Plan

This runbook covers the 0.1.M file-based `USaveGame` persistence path.

## Scope

- Save slot: `AgrarianMVP`
- Expected primary save file: `Saved/SaveGames/AgrarianMVP.sav`
- Automatic backup folder: `Saved/SaveGames/Backups`
- Backup naming: `AgrarianMVP-<UTC timestamp>.sav`

## Symptoms

Treat the save as suspect if:

- server startup logs show load warnings or repeated world-state restore failure;
- players spawn without expected survival, inventory, or placed-world state;
- the save file is zero bytes or much smaller than the latest backup;
- the server crashes immediately after startup load.

## Immediate Response

1. Stop the gameplay server or editor session.
2. Copy the current `AgrarianMVP.sav` aside with a `.suspect` suffix.
3. Identify the newest backup in `Saved/SaveGames/Backups`.
4. Copy that backup to `Saved/SaveGames/AgrarianMVP.sav`.
5. Restart the server.
6. Confirm startup logs report an Agrarian startup load attempt and no crash.
7. Run a manual admin save only after confirming the restored world is correct.

## If All Backups Fail

1. Move the primary save and backups to an incident folder.
2. Start with no `AgrarianMVP.sav` to generate a clean MVP world state.
3. Preserve the failed files for later format/migration debugging.
4. Document the failed save size, timestamp, commit hash, and server log excerpt
   in the handoff.

## Current Limitations

- There is no automated save-file validation tool yet.
- There is no multi-slot rollback UI yet.
- Backups are local to the running machine unless external VM/project backups
  copy `Saved/SaveGames`.
- The current recovery path is operational/manual by design for the MVP.
