1.3.0
Compatibility
Changes
PlayerVaultZ 1.3.0
Security update. Everyone on 1.1.0 or older should update. This release rolls up everything since 1.1.0 (1.2.0 was never published separately).
Security
- Quick Pick duplication fixed. In
/pv selectorwith quick pick on, taking a stack (right-click) or all of an item (shift-click) gave the player the items while the vault kept them too. Items are now removed from the vault before they are handed over, anything that doesn't fit goes back into the vault, and only the exact item clicked is taken (named or plugin items that share a material are no longer swept up together). - Navigation bar duplication fixed. Buttons and filler panes could be pulled out of the vault GUI with a double-click (or an inventory-sorting mod) and kept as real items. GUI items are now tagged and can never be stored or saved.
- Free spyglass from vault search fixed. Every way of leaving the search anvil on Paper 26.x handed the player the placeholder spyglass.
New
- Language files. Every chat message and GUI label is now configurable. Set
language: enorlanguage: frinconfig.yml; the jar ships complete English and French files, and you can add your own inlang/. MiniMessage and&color codes both work. - Per-vault permissions.
playervaultz.vault.<n>grants a single vault number (for example vault 7 only) alongside the existingplayervaultz.vaults.<n>count permission. - MySQL storage and network support.
storage.type: mysqllets several servers behind a proxy share vaults, with locking so two servers never open the same vault at once./pvadmin migrate sqlite-to-mysqlmoves existing data. - Custom navigation buttons. Add your own buttons to the vault GUI in
gui.ymlthat run player or console commands.
Fixed
- Failed database writes were silently reported as saved, which could lose items. Saves now retry and only count as saved once they actually commit.
- Backup and restore menus no longer break when their titles are translated.
playervaultz.vaults.4now shows up in permission plugin tab completion.
Upgrading
Drop in the new jar and restart. Existing configs keep working: new message and GUI keys are added to your files automatically. The old messages.yml is no longer used; its text now lives in lang/en.yml.
Requires Paper (or a fork) 1.21.5 or newer, including 26.x.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:dJVm9lDf:Npe6tl0r"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dJVm9lDf:Npe6tl0r"
}

