Links
Creators
Details
1.4.0.1
Compatibility
Changes
BlockProt Legacy 1.4.0.1 Release Notes
Welcome to BlockProt Legacy 1.4.0.1, the first release of the edition for Minecraft 1.18.2 to 1.20.4. It brings the BlockProt Reloaded feature set to servers that still run Java 17 and older Minecraft versions.
Highlights
- Its Own Edition: BlockProt Legacy covers Minecraft 1.18.2 through 1.20.4 on Java 17. Servers on Minecraft 1.20.5 to 1.21.6 use BlockProt Reloaded Legacy, and servers on 1.21.7 and newer use BlockProt Reloaded. The version guide explains which one to download.
- Java 17: the plugin is compiled for Java 17 and runs on Paper and Purpur from 1.18.2 up to 1.20.4.
- Folia: supported on Minecraft 1.19.4 and newer, the first versions that have Folia builds. Console diagnostics pass on Folia 1.19.4 and 1.20.4.
- Chest Menus Only: native Paper dialogs need the Paper 1.21.7 API, so this edition opens every menu as a chest inventory. The
use_dialogssetting has no effect here and stays inconfig.ymlso a later move to a newer edition activates it. - Same Data, Safe Moves: all editions share the plugin data folder and never rewrite keys they do not know. The plugin records the edition in
plugins/BlockProtReloaded/.editionand makes a backup named with both editions when you move between them.
Changelog
Added
- Added the edition model shown in
/bp about, the boot banner and/bp debug. - Added a startup warning on Minecraft versions newer than 1.20.4 that names the edition for that version and links the version guide. The plugin keeps running.
- Added a startup message on Minecraft versions older than 1.18.2 that disables the plugin and tells you to read the version guide.
- Added console diagnostics checks for the edition marker and for statistics after ownership transfers.
Changed
- Materials that do not exist before Minecraft 1.19.4, such as hanging signs and chest boats, are resolved through guarded lookups with a plain fallback icon.
- Plugin versions are read through the plugin description API that exists on every supported version.
- Every paged chest menu now uses the same bottom row as BlockProt Reloaded: previous page, the menu's main action, and next page in the center, with Back in the corner. List menus show 45 entries per page.
- Update checks only offer releases of this edition (tags starting with
bpl-). - WorldGuard support is built against WorldGuard 7.0.9 so the plugin compiles for Java 17.
- Every console line, the first start guide and the debug reports now carry the name of the running edition instead of BlockProt Reloaded.
Fixed
- Fixed transferred blocks staying in the previous owner's statistics and increasing the global protected block count on every transfer.
- Fixed transfers leaving the previous owner recorded in the database block index.
- Fixed the statistics list hiding the Previous button on its last page.
- Fixed the entity information menu drawing friends over its navigation row when an entity had more than 36 friends.
- Fixed clicks on empty bottom-row slots of list menus selecting an entry from the page.
Not Included
- Native Paper dialogs: not available in this edition, see Highlights.
- New features: legacy editions receive bug fixes, security fixes and compatibility with new Minecraft releases inside their range. New features land in BlockProt Reloaded only.
Availability
- Modrinth only: BlockProt Legacy 1.4.0.1 is published on Modrinth and as a GitHub release. It is not published on CurseForge or Hangar.
Verification
Before publication this build was tested in GitHub Actions (run 36665051307). Every supported Minecraft version (1.18.2 - 1.20.4) 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:R0syLmu8:grjAH9my"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:R0syLmu8:grjAH9my"
}

