Storage and Backups

Storage & Backups

The database

RoyalBank stores accounts, balances, tiers, transactions, and anti-abuse state in a single SQLite file:

plugins/RoyalBank/bank.db

The file name is set by database.file in config.

You'll also see bank.db-wal and bank.db-shm alongside it — those are the write-ahead log and shared-memory files SQLite uses in WAL mode. They're normal; don't delete them while the server is running.

Reliability model

• Every money operation moves through Vault and persists the balance in a single database transaction. If the write fails, the Vault side is rolled back — money is never created or destroyed by a half-completed operation.
• Online players' accounts are cached in memory (loaded on join, evicted on quit). GUIs and PlaceholderAPI read the cache, not the database, so normal play doesn't hammer disk.
• The database uses WAL mode with a busy timeout, so reads and writes don't block each other.
• Transaction pruning and backups run asynchronously on dedicated connections, off the main thread.
• Existing databases are migrated automatically on startup as new columns are introduced — no manual schema steps.

Backups

/bank admin backup

• Backups are written to plugins/RoyalBank/backups/.
• The command uses SQLite VACUUM INTO rather than copying the live file, so you get a clean, consistent snapshot even while the server is running (a raw file copy of an active WAL database can be corrupt).
• It runs off the main thread, so backing up a large database doesn't stall the server or cause lag.

Recommended routine

• Run /bank admin backup before major config edits, plugin updates, or economy changes.
• For scheduled backups, trigger /bank admin backup from a command-scheduler plugin (or copy the backups/ folder off-server on your own cron).

Restoring

1. Stop the server.
2. Replace plugins/RoyalBank/bank.db with the backup file (rename it back to bank.db).
3. Delete any stale bank.db-wal / bank.db-shm next to it.
4. Start the server.

MySQL?

RoyalBank uses SQLite. It's more than enough for a single server — SQLite handles a Minecraft server's account load comfortably, and WAL mode keeps it responsive. (The companion plugins RoyalAuctions and RoyalBazaar offer MySQL for network-wide shared data; RoyalBank's accounts are per-server.)

Housekeeping

• Keep transactions.max-per-player at a sane number (default 100) so the transaction table can't grow without bound. Pruning runs on startup when transactions.prune-on-startup is true.
• Don't hand-edit bank.db while the server is running. Use the admin commands, or stop the server first.