# Roll back a plugin update that changed its data files

[Rust server guides](https://rustsc.com/learn/index.html.md) / [Updates](https://rustsc.com/learn/updates/index.html.md)

A plugin rollback needs compatible code, settings and data. Keep a matched copy from before the update and prove the old plugin can read it. If players have earned progress since that copy, decide what the recovery would cost before using it.

## Look for a conversion before the update

Read the author's release notes for changes to stored settings or data. Server Rewards describes an older version change that attempted to convert past data and asks owners to keep a backup. For the version you are considering, identify where the installed plugin stores its state, including any external store it names.

Make the rehearsal on a private copy with synthetic data. Record a known value such as a test player's balance. Stop the test server cleanly and save the old plugin, settings, data and required dependencies together. Keep that set outside the active game folder and separate from the copy you will update.

## Prove both directions on the private copy

Use separate copies for the post-update investigation and the attempt to go back.

1. Start one copy with the new version. Confirm it finishes loading and compare the recorded test value. Create one new test change to see what would exist only after updating.
2. Return a fresh copy to the old plugin with the old settings, data and required dependency versions. If an external store is involved, use a disposable instance and follow the maintainer's recovery instructions.
3. Start the old copy and check the reported version, the known pre-update value and the normal player action. Record whether the later test change is absent. If the old code cannot read the old copy, stop the rehearsal and ask the maintainer for a supported recovery method.

## Choose an outcome before reopening

Take and label the live checkpoint before a scheduled update. Keep player activity paused until you check that conversion succeeded. If a live change has already failed, keep the failed copy and console evidence available for recovery.

| What changed since the checkpoint | Decision |
| --- | --- |
| The server stayed closed while the new version was checked | Use your tested, supported recovery path if the upgraded plugin cannot pass the checks. |
| Players earned balances, made purchases or claimed rewards | Record what the old copy would lose. Keep access paused while you decide whether to repair the newer data or accept and explain the agreed loss. |
| You cannot verify the storage or a dependent version | Ask the maintainer before any live restore. Keep both copies available. |

## Sources

- [Server Rewards migration and backup instructions](https://umod.org/plugins/server-rewards)
- [Oxide data files and configuration](https://docs.oxidemod.com/guides/developers/data-storage)
- [Oxide plugin loading and reloads](https://docs.oxidemod.com/guides/owners/install-plugins)

## Related resources

- [Restore a backup](https://rustsc.com/support/guides/restore-backup/index.html.md)
- [What to save before rolling back a Rust server](https://rustsc.com/learn/recovery/save-current-rust-world-before-rollback/index.html.md)
- [Which Rust plugin updates belong on force-wipe day?](https://rustsc.com/learn/updates/should-you-update-a-rust-plugin-on-force-wipe-day/index.html.md)

---

HTML version: https://rustsc.com/learn/updates/rollback-plugin-update-with-data-conversion/
