Tags
Creators
Details
All versions
0.4.1-alpha+1.21.1
Alpha
0.4.1-alpha+1.21.16 months ago 34
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
BTC - Better Trial Chambers Changelog
Version Update
New Features
Fan System
- FanBlock & FanBlockEntity: New directional fan block that applies cone force to entities
- Client-side Rendering: Full fan model with smooth spin-up/spin-down animations
- FanBlockEntityRenderer implementation
- FanBlockModel with visual state tracking (fanSpeed, visualRotation)
- Model layer registration and render layer integration
- Particle Effects: Cloud particle emission on client-side
- Smart Filtering: Creative and spectator mode players excluded from fan effects
- Physics: Configurable rotation speed with acceleration/deceleration logic
- Assets: Complete blockstate, model, and texture set
Trial Core Block
- New block and entity for trial chamber mechanics
- Foundation for future trial chamber enhancements
Improvements
Bonfire System Enhancements
- Client-Server Synchronization: Fixed fire rendering persistence after player death
- New BonfireSyncPayload packet system
- Proper client-server sync handler registration
- Configurable Radius: Radius now configurable per block and stored in NBT
- Data Persistence: Player bonfire spawn data storage on client with proper recovery
- Renderer Updates: Improved bonfire effect rendering for saved spawn locations
Bug Fixes
- Fixed bonfire fire rendering disappearing after player death
- Corrected entity drag calculations for improved physics accuracy
- Improved home position initialization for mounted entities
- Enhanced NBT data synchronization between client and server
Technical Details
Infrastructure
- Expanded client-server synchronization systems
- Enhanced NBT persistence for entity state recovery
- Improved particle rendering pipeline
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:PDkYCAeF:Wpsa7lbC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PDkYCAeF:Wpsa7lbC"
}

