Tags
Creators
Details
0.2.3
Compatibility
Changes
ChunkVeil 0.2.3
This update improves admin diagnostics, performance tuning, packet protection, and fail-closed safety.
Added
- Added
/chunkveil compatfor Minecraft, Paper, Java, ProtocolLib, rewrite, runtime, enabled worlds, and warning diagnostics. - Added
/chunkveil inspect <player>for player-specific ChunkVeil state. - Added
/chunkveil reportto generate diagnostic report files. - Added
/chunkveil predictto estimate performance from live timing samples. - Added config validation warnings for common setup issues.
- Added configurable chunk update budgets and entity scan limits.
- Added optional adaptive scan quality below a configured TPS threshold.
- Added secondary packet protection counters for hidden explosions, world events, block break animations, and positional sounds.
Improved
- Improved
/chunkveil statuswith clearer grouped output and timing metrics. - Improved fail-closed behavior when raw chunk rewriting is unavailable or breaks at runtime.
- Improved packet rewrite handling for partial hidden sections.
- Improved Spigot and Modrinth documentation.
Fixed
- Fixed non-16-aligned
hide-below-yvalues exposing partial top sections before later updates. - Fixed sub-16 hidden ranges triggering fail-closed incorrectly.
- Split chunk masking timings into packet chunk rewrite and chunk update masking metrics.
Important: ProtocolLib compatibility matters. Use a ProtocolLib build compatible with your exact Paper/Minecraft version.
Full release: https://github.com/DeKaeyman/ChunkVeil/releases/tag/v0.2.3
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:g8Oz51N1:QKswEX1W"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:g8Oz51N1:QKswEX1W"
}

