FAQ

Is it free?

Yes. ExyliaPlayerVaults is free and open source, under the GNU General Public License v3.0. Download it from Modrinth; the source is on GitHub. There is no licence key and nothing to buy.

I used the vaults of ExyliaSurvivalCore. Do my players keep them?

Yes, as long as this plugin opens the same database. The vaults stay in the same table, sc_vaults: point plugins/ExyliaPlayerVaults/database.yml at the database ExyliaSurvivalCore used and every vault is there. On the default H2 file nothing is copied for you. The settings and the permissions have new names, and /vaultadmin is now /pvadmin. See Coming from ExyliaSurvivalCore.

Every vault looks empty after installing

The plugin is reading a different database from the one the vaults are in — usually a fresh H2 file in its own folder while the vaults are still in ExyliaSurvivalCore's. Nothing has been lost; set the right database in database.yml and restart.

"That vault is open somewhere else right now"

Somebody has that vault open: the player in another window, on another server, or a member of staff. A vault closed on one server and opened on another straight away is handed over within a moment. After a server crash, its vaults stay shut for up to a minute, until the lock's lease runs out. See Network.

A player lost a rank and their items are gone

They are not. With hidden-slots: keep, the default, the stacks past the vault's new size stay stored out of sight and come back when the vault has enough rows again; staff see them with /pvadmin edit, which is always six rows. Vaults past the player's new count show as locked and keep everything inside. With hidden-slots: return, the stacks were handed back to the player, or are waiting for their next join.

A player cannot buy another vault

Either purchases are off (purchase.enabled), they reached max-purchases, or their rank's vaults plus the ones they bought already reach vaults.max-amount. Bought vaults count under that cap, so raise max-amount when you add ranks with more vaults. See Purchases.

A purchase took the money but gave no vault

That only happens when the database stopped answering mid-purchase, and the console logs it as an error with the player, the price and the count playervaults_buyers should hold. Check that row and refund the player if it was not raised.

Staff cannot edit a vault open on another server

Closing a vault on another server travels over Redis. Without Redis enabled in database.yml on every server, staff are told the vault is in use until its viewer closes it.

A player put something in, the server crashed, and it is gone

Open vaults are written every vaults.checkpoint (30 seconds) and on close, so a crash costs at most that much of a vault. /pvadmin history <player> <number> shows the copies kept before each change, and any of them can be put back.

My edits to the history menu disappeared

lang/<code>/menus/admin/history.yml is replaced from the jar on every start and every reload. The vault list under menus/user/ is yours and keeps your edits.

Where do I get help?

On the Exylia Discord: discord.exylia.net. Bug reports and feature requests are also welcome as issues on the GitHub repository.