All versions
1.1.0
Release
PlayerVaultZ 1.1.03 months ago 1,341
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platform
Paper
Changes
[1.1.0] - 2026-05-27
Fixed
- Search crash — Replaced the WesJD AnvilGUI library with Paper's native
MenuType.ANVILAPI. The old library used versioned NMS packages (org.bukkit.craftbukkit.v1_21_R5) that do not exist in Paper 26.1.x, causing aNoClassDefFoundErrorwhenever a player opened the search GUI. - Search field pre-filled with "Spyglass" — The anvil rename field now starts blank instead of showing the item's material name.
- Security config not loading — YAML key paths in
SecurityConfigwere mismatched (e.g.security.input-validation.*vs the actualitem-validation.*), causing all security settings to silently fall back to defaults. logAllTransactionsfield rename —AuditLoggerreferenced a field that had been renamed tologTransactions, which would have caused a compile error on a clean build.- Plugin uptime showing Unix epoch —
getUptime()was returningSystem.currentTimeMillis()directly instead of subtracting the start time, showing billions of hours of uptime. ItemFlag.HIDE_ITEM_SPECIFICS— Replaced withHIDE_ADDITIONAL_TOOLTIPinIconSelectorGUIandVaultSelectorGUIto match the renamed enum in Paper 1.21.x.
Changed
- Security system — Stripped unimplemented Phase 3–5 dead code (duplication detection, anomaly detection, honeypot vaults). The three active layers (item validation, rate limiting, audit logging) are unchanged.
checkVaultAccess— Switched fromCompletableFuture.supplyAsync()tocompletedFuture()so the security check is synchronous and cannot arrive after the inventory event has already been processed.SecurityViolationType— Removed unused enum values:DUPLICATION_DETECTED,ANOMALOUS_BEHAVIOR,HONEYPOT_ACCESS,SUSPICIOUS_TIMING.
Removed
- AnvilGUI dependency —
net.wesjd:anvilguiremoved frompom.xml. The CodeMC Maven repositories that existed solely for this dependency are also removed.
Config
security.yml— Removed three sections that were never read by the plugin:performance,bypasses, and unused audit sub-keys (log-suspicious-patterns,file-prefix,max-file-size-mb,max-files,include-metadata).config.yml— Removedsecurity.audit-logging(dead key; audit is controlled bysecurity.yml → audit.enabled).
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:SRsfWtrv"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dJVm9lDf:SRsfWtrv"
}

