Tags
Creators
Details
1.0.1
Compatibility
Required content
Changes
ChunkBlock 1.0.1
Patch release fixing all bugs reported against 1.0.0, plus two compatibility problems that showed up when running ChunkBlock alongside other gamemodes.
Highlights
- Mining near the border no longer spams claim messages ā the border-claim detection ignored the block you actually clicked and passed through walls, so mining a generator within a few blocks of a locked chunk nagged "You need X more level(s) of credit" on every swing. Claims now only trigger when you genuinely aim at the border, and failure feedback is rate-limited. Fixes #14
- Respawns can no longer strand players on a stranger's island ā a respawn that landed in a locked chunk of an old or abandoned island used to relocate the player within that island and generate a landing block. Players who don't belong to the island are now sent to their own island home instead. Fixes #13
- š” Phases GUI respects the setcount permission ā "Click to change" is no longer offered to players without
chunkblock.island.setcount, and the GUI title now says ChunkBlock Phases. Fixes #11 - šŗ āļø Own flag IDs, no more AOneBlock collision ā the boss bar, action bar, and start-safety flags are now
CHUNKBLOCK_BOSSBAR,CHUNKBLOCK_ACTIONBAR, andCHUNKBLOCK_START_SAFETY. Previously they shared AOneBlock's flag IDs; BentoBox rejects duplicate flag registrations, so on servers running both gamemodes whichever addon loaded second silently lost its flags and those features broke. - šŗ āļø Default commands changed from
/cbto/chā CaveBlock already uses/cband/cbadmin, so ChunkBlock's defaults are nowch chunkblock(player) andchadmin chunkblockadmin cha(admin). Servers keep whatever aliases are already in their config.yml; only fresh installs get the new defaults. - Clean shutdown when Level is missing ā ChunkBlock requires the Level addon (island levels are the currency for claiming chunks). If Level is not on the server, ChunkBlock now disables itself with a clear message instead of leaving half-registered listeners that spammed errors on every join and move.
šŗ Upgrade note: if you changed the boss bar, action bar, or start-safety world settings from their defaults, re-apply them once after upgrading ā the flag rename means the old
ONEBLOCK_*/START_SAFETYvalues are no longer read.
š” Locale note: locale files gained renamed keys (
protection.flags.CHUNKBLOCK_*, phases GUI titles). Regenerate or update customized locale files.
Compatibility
āļø BentoBox API 3.13.0+ āļø Minecraft 1.21+ āļø Java 21
Upgrading
- Replace the ChunkBlock jar in
plugins/BentoBox/addons/and restart. - If you customized the boss bar / action bar / start-safety world settings, re-apply them (see upgrade note above).
- If your players relied on
/cb, either keep your existing config.yml aliases (nothing changes) or adopt the new/chdefault.
Legend
- š” ā locale files may need to be regenerated or updated.
- āļø ā config options have been removed, renamed, or added.
- šŗ ā special attention needed.
What's Changed
- Stop mining near the border from triggering claim attempts (fixes #14) by @tastybento
- Send non-members home instead of ejecting them within a stranger's island (fixes #13) by @tastybento
- š” Only offer 'Click to change' in the phases GUI to players who can use it (fixes #11) by @tastybento
- šŗ āļø Give ChunkBlock its own flag IDs and harden the flag listeners by @tastybento
- šŗ āļø Change default command aliases cb/cbadmin to ch/chadmin by @tastybento
- Disable ChunkBlock cleanly when the Level addon is missing by @tastybento
- Make every BossBarListener handler inert when the addon never enabled by @tastybento
- ci: pin publish-platforms workflow by @tastybento in https://github.com/BentoBoxWorld/ChunkBlock/pull/15
Full Changelog: https://github.com/BentoBoxWorld/ChunkBlock/compare/1.0.0...1.0.1
Optional dependencies
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:zhMgGehx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PPk6G8LJ:zhMgGehx"
}

