Data Safety

The rule every release follows: an update may fail, but it must never quietly change or throw away anyone's items, money or listings.

Backups before every new version

The first time a new ProtonAuctions build starts, before it opens your data, it makes a copy of:

• the files in plugins/ProtonAuctions, including config.yml, your other settings files and the proton.lock key file,
• the translations folder,
• the SQLite databases, both the auction house one and the economy engine one.

The copy goes into plugins/ProtonAuctions/backups, in a folder named after the date, the version and the build, and the console says where it went. The last three backups are kept and older ones are removed.

If the copy fails, the plugin still starts, says so in the console, and tries again on the next start. Copy the plugins/ProtonAuctions folder somewhere safe yourself in that case.

A MySQL or PostgreSQL database is not copied, only ProtonAuctions' own files are. The console reminds you each time a new version starts: back that database up yourself before every update.

Problems are fixed forward

If a release has a problem, it is fixed with a new release. Before every release, the new build opens a saved database from the previous release and checks that everything stored in it reads back exactly the same, so an update cannot reinterpret what is already in your database.

When the beta ends

Nothing is deleted when a beta key ends either. The plugin switches to recovery-only mode: trading stops, every listing and barter offer goes back to its owner, and players collect their items and money with /ah claim. See Beta Pricing for the timeline.