Tags
Creators
Details
All versions
2.2.1
Release
Better Trial Chambers 2.2.1last month 13
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Folia
Paper
Purpur
Changes
[2.2.1] - 2026-09-20
Fixed
- Trial spawners are found again after a chunk that another plugin was changing. When a chunk loaded, the plugin checked it for trial spawners. If another plugin was changing blocks in that chunk from a second thread at the same moment, the check failed with an error and that chunk's spawners were left off the list, so spawner waves could be missed there. The failure is now handled: the console says which chunk it was, and the spawners are picked up the next time the chunk loads or anything in it is broken or placed.
- Chunks load faster on busy worlds. The check above asked the server to build a full description of every chest, barrel, sign, hopper and banner in the chunk, just to find the trial spawners among them. It now asks only about trial spawners.
- A repeating problem no longer sends a repeating error report. Error reports are on by default and some are sent from places that run on every vault opened. One thing going wrong, such as a database that stopped answering, could send a report every time. Reports of the same kind are now sent at most once every ten minutes.
- Error reports no longer include the folder your server lives in. When a file or database problem was reported, the message quoted the full path, which names your hosting account. Reports now show it as
plugins/BetterTrialChambersinstead. Your own console keeps the full path, because that is where it is useful.
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:pLHeflqe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ownTWGOH:pLHeflqe"
}

