Tags
Creators
Details
1.4.1-hotfix.2
Compatibility
Changes
BlockProt Reloaded 1.4.1-hotfix.2 Release Notes
Note: As a targeted maintenance release, this hotfix does not include a release notes banner.
1.4.1-hotfix.2 fixes locked blocks losing their protection after a server restart. No configuration or data format changes.
Fixed
- Hoppers drained locked chests after a restart (#22): the list of protected blocks was rebuilt at startup from a background thread and only from the statistics file, so locks that were not found stayed unprotected until they were locked again. A hopper under a locked chest could then pull its items. Protection is now verified against the block itself whenever a location is not yet known.
- Same cause, other protections: after a restart, locked blocks were also exposed to pistons, explosions, fire, redstone, and block breaking by other players. They all use the same check and are fixed together.
- Double chests: the second half of a locked double chest was never registered as protected. It is now verified like any other block.
Verification
Before publication this build was tested in GitHub Actions (run 37131912140). Every supported Minecraft version (1.21.7 - 26.3) booted on real Paper, Folia and Purpur servers wherever that software publishes a build (a declared version without a build of its own runs on its newest hotfix), and passed the plugin console diagnostics. On every version the test client supports, a two-player protection test also passed: the owner protects and opens a chest, and a second player can neither open nor break it.
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:C2ZYTu62:tVO9lJxt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C2ZYTu62:tVO9lJxt"
}

