All versions
1.0.3
Release
ChestLock999 The Bug Fix Update!last month 14
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Fixed
- Fixed containers being impossible to lock because no lockable container types were enabled by default; a default set of lockable containers now ships with the plugin, and an empty list makes every container lockable
- Fixed owners being unable to break blocks or build near their own locked containers
- Fixed owners being unable to remove their own locked containers; breaking a locked container now also clears its lock
- Fixed protection not covering explosions around locked containers
- Fixed creatures and entities such as endermen, withers and falling blocks being able to change blocks near locked containers
- Fixed hoppers and similar automation being able to move items into or out of locked containers
- Fixed locks, trust changes, group changes and ownership transfers being lost when the server stops unexpectedly; every change is now saved right away
- Fixed lock details, including the owner and trusted players, being shown to unrelated players; details are now only shown to the owner and trusted players
- Fixed locked containers in worlds that are not loaded at startup being loaded incorrectly and causing errors; such entries are now safely skipped
- Fixed the plugin's basic permission being declared but never enforced; commands now respect it
- Fixed ownership transfers being able to exceed the receiving player's lock limit or be sent to the current owner, and the receiving player is now notified
- Fixed the "trusted" and "untrusted" messages ignoring the configured messages
- Fixed player lookups creating records for names that have never played on the server
- Fixed lock dates and times being hardcoded; both display formats are now configurable
- Fixed a possible error when the plugin shuts down without having started correctly
- Fixed the JSON library not being declared as a dependency of the plugin
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:sapl4dJP:WjWDeRS4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sapl4dJP:WjWDeRS4"
}

