Tags
Creators
Details
All versions
2.0.11-mc26
Release
Better Trial Chambers 2.0.11-mc263 months ago 42
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platforms
Folia
Paper
Purpur
Changes
[2.0.11] - 2026-07-26
Fixed
- Memory no longer stays high after a chamber resets. Putting a chamber's blocks back has to pull that whole part of the map into memory, and the server kept it there afterwards even when nobody was anywhere near it — so on a server with a lot of chambers, memory climbed a step with every reset and never came back down. The plugin now tells the server it has finished with that area once the reset is complete. (This is the same fix 2.0.9 made for chamber discovery, now applied to resets as well. Areas players are actually in are never touched.)
- Resets no longer flood the console. A reset used to print a progress line for every batch of blocks it placed — on a very large chamber that meant well over a thousand near-identical lines scrolling past, which looked for all the world like the reset was stuck repeating itself. Progress is now reported at every 10%, so any reset is about nine lines however big the chamber is. If you want to check a reset really is progressing, those lines now count upwards in clear steps.
- Reset progress could stop being reported at all. The old progress lines only appeared when a batch happened to finish on an exact multiple of 1000 blocks. That held at the default setting, but if you had changed
global.blocks-per-tickthe console could go almost completely quiet during a reset, leaving no way to tell whether anything was happening.
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:ownTWGOH:fgYjXDJX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ownTWGOH:fgYjXDJX"
}

