Tags
Creators
Details
1.4.0
Compatibility
Changes
ChunkBlock 1.4.0
This release makes big island areas viewable and navigable on the chunk map, clears up who claimed what on team islands, and simplifies configuration by letting the protection range drive island size directly.
Highlights
- š” Scrollable chunk map with view modes ā Islands larger than the 13Ć13 dialog viewport now get a control row on the
/ch chunksmap: center the view on your island (ā) or on your own position (ā), with a directional arrow (8 directions) pointing at whichever one is off-screen. Clicking the arrow jumps to the other view. Small islands see the map exactly as before. [PR #49] - š” Claim messages name the claimer ā Team members used to see "Chunk claimed!" when anyone on the island claimed a chunk and thought they had done it themselves. The message now reads "PlayerName claimed a chunk!" so everyone knows who spent the credit. [PR #46]
- šŗ āļø
max-chunkssetting removed ā The protection range already determines how many chunks fit, so the separatechunkblock.max-chunkscap was redundant and confusing. Island size is now derived purely fromworld.protection-range: with the default range of 168, the largest ring is 10, giving a 21Ć21 = 441-chunk square. To change how many chunks players can claim, adjust the protection range. An existingmax-chunksentry in your config is simply ignored. [PR #48]
āļø Config Default Corrections
The bundled config.yml had several stale defaults inherited from AOneBlock that didn't match the code. Fresh installs now get the correct values [PR #47]:
| Setting | Was | Now |
|---|---|---|
world.protection-range |
240 | 168 |
world.island-height |
80 | 120 |
world.concurrent-islands |
1 | 0 (BentoBox default) |
world.nether.spawn-radius |
25 | 32 |
island.max-homes |
1 | 5 |
island.reset.on-join.* (inventory/health/hunger/exp) |
false | true |
island.reset.on-leave.inventory |
true | false |
Existing servers are unaffected ā your config on disk is not changed. These only apply to new installations. However, if you do delete it, then the replacement will be with different settings, so beware!
Other Improvements
- Resolved 84 SonarCloud issues across main and test sources: null-safety guards, cognitive complexity reductions, duplicate-literal constants, and test hygiene.
- š” All 17 translation locale files synced with the new dialog keys.
- Hangar publishing is now part of the automated release pipeline.
Compatibility
āļø BentoBox API 3.22.0 āļø Minecraft 1.21+ (Paper ā the dialog map requires Paper's dialog API) āļø Java 21
Upgrading
- Replace the ChunkBlock jar in
plugins/BentoBox/addons/and restart. - š” Delete
plugins/BentoBox/locales/ChunkBlock/(or justen-US.yml) so the updated locale files regenerate ā the claim message and new map keys won't appear otherwise. - šŗāļø If your config sets
chunkblock.max-chunks, remove it ā it is ignored. Setworld.protection-rangeto control island size instead (range 168 ā 441 chunks, range 240 ā 841 chunks).
Legend
- š” ā Locale files may need to be regenerated or updated
- āļø ā Config options have been removed, renamed, or added
- šŗ ā Special attention needed
What's Changed
- š” feat: scrollable chunk map dialog with player/island view modes by @tastybento in https://github.com/BentoBoxWorld/ChunkBlock/pull/49
- šŗ āļø refactor: remove max-chunks setting, derive limit from protection range by @tastybento in https://github.com/BentoBoxWorld/ChunkBlock/pull/48
- šŗāļø fix: align config.yml defaults with Settings.java by @tastybento in https://github.com/BentoBoxWorld/ChunkBlock/pull/47
- š” fix: include claimer name in chunk claimed message by @tastybento in https://github.com/BentoBoxWorld/ChunkBlock/pull/46
Full Changelog: https://github.com/BentoBoxWorld/ChunkBlock/compare/1.3.0...1.4.0
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:PPk6G8LJ:Z6q0IJfn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PPk6G8LJ:Z6q0IJfn"
}

