Tags
Creators
Details
1.4.0
Compatibility
Changes

BlockProt Reloaded 1.4.0 Release Notes
Welcome to BlockProt Reloaded 1.4.0. This release launches the two legacy editions, so servers on Minecraft 1.18.2 through 1.21.6 have a supported BlockProt again, and it makes every console line and debug report name the edition that is running.
Highlights
- Legacy Editions Launch: BlockProt Reloaded Legacy 1.4.0.1 covers Minecraft 1.20.5 to 1.21.6 on Java 21, and BlockProt Legacy 1.4.0.1 covers Minecraft 1.18.2 to 1.20.4 on Java 17. Both are published on Modrinth only: BlockProt Reloaded Legacy and BlockProt Legacy. The version guide explains which one to download and how to move between them.
- Tested On Real Servers: every supported Minecraft version of the legacy editions is booted on a real Paper server in GitHub Actions, with Folia and Purpur on every version that has a build. Each server passes the plugin console diagnostics and a two-player protection test: the owner protects and opens a chest, and a second player can neither open nor break it. A legacy edition is only published when that run passes.
- Edition In The Console: the log prefix, the first start guide,
/bp debugand the debug reports now show BlockProt Reloaded, BlockProt Reloaded Legacy or BlockProt Legacy instead of always saying BlockProt Reloaded. - Version Baseline Unchanged: BlockProt Reloaded keeps supporting Minecraft 1.21.7 through 26.3. Nothing changes for servers already on 1.3.9.
Changelog
Changed
- The console prefix, the first start guide title,
/bp debugand the debug report header use the name of the running edition.
Status
- BEDev: pre-release builds of 1.4.0 are published on GitHub for testing before the stable release.
- Maintenance: the maintainer is taking a break to focus on other projects. Issues and pull requests are welcome for any change and are reviewed as time allows.
Verification
Before publication this build was tested in GitHub Actions (run 36665040826). Every supported Minecraft version (1.21.7 - 26.3) booted on real Paper, Folia and Purpur servers wherever that software publishes a build, 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:qeOAktT9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:C2ZYTu62:qeOAktT9"
}

