Release JPPlayerVaults 1.1.0 · Nameeees/JPPlayerVaults

Database storage and administrator tools.

Optional SQL storage (storage.type: mysql) next to the YAML files: any database over JDBC, MySQL/MariaDB preconfigured, tables created automatically and every vault written inside a transaction.
/pv admin subcommands behind the new jpvaults.admin permission (OP by default):
- /pv admin open <player|uuid> <number> - open another player's vault, online or offline.
- /pv admin info [player] - plugin status, or a report for one player.
- /pv admin delete <player|uuid> <number> confirm - wipe one vault.
- /pv admin migrate [force] - copy the YAML files into the database, in batches, keeping the originals.
Database settings in config.yml: host, port, database, credentials, table prefix, pool size, connection timeout, driver class and a raw JDBC URL for other engines.
When stored data cannot be read, the plugin refuses to open the vault instead of showing it empty and overwriting the real items on the next save.

A vault can only be open for one person at a time, so an administrator cannot edit a vault while its owner has it open (and the other way round).
/pv reload reports when storage settings changed and a restart is needed.

Integration harness: PASS on Paper 1.8.8 (47 checks) and Paper 26.3 (69 checks), covering both backends (the SQL one end to end against H2 in MySQL mode with the production schema) and every command path.
Real 1.8.8 client: open, store, disconnect, reconnect and the item comes back from storage.

Navigation Menu