
What if a Rust restore leaves plugin balances from a later day?
If a world goes back to Monday while a shop still shows Wednesday’s balance, find where that plugin stores its records. Compare the game copy with the separate data before reconnecting the plugin to players.
Write down which records survived from each time
Check your plugin settings and the author's instructions. Oxide plugins can use local files or a database reached separately. For example, Monday’s world restores the shop building, but the plugin reads balances from a shared MySQL database that never rolled back. Note what modern records would be lost if you restored that entire database to Monday.
Keep the current game backup and a separate backup of the current plugin records. Use the database’s own backup and restore method or ask its operator to make the copy. If more than one world uses those records, identify the other worlds before deciding to change any shared data.
Check a pair of recovery points away from players
Restore the game to an isolated test location and use a separate copy of the plugin data with its own access, or keep the plugin disabled until that copy is ready. Confirm the test configuration does not connect to live services or send live notifications. For an example Monday recovery, use known test accounts to compare Monday’s saved world with balances from the proposed data copy.
| What you see | Review before opening |
|---|---|
| Known balance and shop both match Monday | Confirm what newer progress the chosen recovery would replace. |
| World is Monday, balances are newer | Ask the plugin author about combining or retaining those records safely. |
| Data is shared across several worlds | Get a separate export or supported restore scope before replacing shared records. |
Decide what you can explain to players
Keep the shop feature closed if you cannot reconcile its state. Reopen the whole game only if it behaves as intended without that feature, and explain the missing part in your update. When you do restore the plugin data, verify one expected balance and one normal test transaction on the recovery copy before using it on the shared world.