Tags
Creators
Details
1.4.0-hotfix
Compatibility
Changes
BlockProt Reloaded 1.4.0-hotfix Release Notes
Note: As a targeted maintenance release, this hotfix does not include a release notes banner.
1.4.0-hotfix fixes the staff tier permissions of 1.4.0 and brings the documentation in line with what the plugin does. Servers that keep admin_tiers.enabled: false, the default, see no change in who can do what.
Fixed
- Admin hub checks each button: with
admin_tiers.enabled: true, any staff tier could open/bp adminand use every button in it, including the configuration editor, world protection deletion, reload, and staff role management. Each button of the hub now checks the tier of its action, in the chest menu, the Paper dialog, and the Bedrock form. - Lock menu on other players' blocks: with admin tiers enabled, the Paper dialog and the Bedrock form gave every staff tier owner-level control over other players' blocks, while the chest menu did not. All three now require Tier 2, and Tier 2 can unlock those blocks as documented.
- Tier 1 works as documented: Tier 1 now opens
/bp info, gets a read-only lock menu on other players' blocks with the block info and the audit log, and can teleport from admin block lists. - Startup warning: the warning shown on Spigot and CraftBukkit no longer says support ends in 1.3.6. They are not supported.
Documentation
- The README, the admin guide, the player guide, and the download page descriptions now describe commands, permissions, friend levels, staff tiers, and the optional MySQL index as the plugin implements them.
- Timed access and the ImageFrame integration were listed as features but never existed. They are no longer mentioned.
Testing
- Minecraft 26.1 is now tested on its newest server build, 26.1.2. Earlier test runs skipped it because no server software publishes a build named 26.1.
Verification
Before publication this build was tested in GitHub Actions (run 36803357003). 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:6ey5jkLg"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C2ZYTu62:6ey5jkLg"
}

