Tags
Creators
Details
1.4.1
Compatibility
Changes
ChunkBlock 1.4.1
A quick follow-up to 1.4.0 that makes the large-island chunk map properly navigable.
š” Pannable Chunk Map
The 1.4.0 map gave big islands two snap views (island center / your position) with an arrow that only appeared when one of them was off-screen ā which confused players expecting to scroll, and left the corners of a large island unreachable. The /ch chunks control row now looks like this [PR #51]:
[ā] ā ā ā [ā] [ā²] [ā¢] [ā¼] [ā¶] ā ā ā [ā]
- ā ā² ā¼ ā¶ ā always-visible pan arrows: each click slides the view half a screen (6 chunks), so every corner of the map is reachable. An arrow disappears when the view reaches that edge of the map.
- ā jumps to the island center, ā jumps to your position ā filled white when the view is already there.
- ⢠ā the middle indicator becomes a gold arrow pointing at the island center (or an aqua one pointing at you) whenever that target is panned off-screen; clicking it jumps there.
- Clicking a chunk to inspect it keeps your panned position instead of resetting the view.
Small islands that fit in the 13Ć13 viewport see no control row, exactly as before.
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 locale files regenerate ā the pan-arrow tooltips are new keys. All 17 translations are already synced.
Legend
- š” ā Locale files may need to be regenerated or updated
What's Changed
- š” feat: pannable chunk map with always-visible scroll arrows by @tastybento in https://github.com/BentoBoxWorld/ChunkBlock/pull/51
Full Changelog: https://github.com/BentoBoxWorld/ChunkBlock/compare/1.4.0...1.4.1
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:Veb27zz2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PPk6G8LJ:Veb27zz2"
}

