1.0.3
Compatibility
Changes
Timbr v1.0.3
Realistic Tree Falling Animation & Java 21 Upgrade
A smoother, heavier, and more cinematic tree falling experience has arrived for Timbr
✨ What's New
Fully Reworked Tree Falling Animation
Timbr now uses modern BlockDisplay rendering for dramatically smoother and more realistic tree falling animations inspired by advanced physics-based tree systems.
Rigid-Body Rotation
Entire trees now rotate naturally as one connected structure instead of collapsing in disconnected pieces.
Ultra Smooth Motion
Client-side interpolation now makes animations feel fluid and cinematic, even at high FPS.
Realistic Falling Acceleration
Trees slowly begin tipping before rapidly accelerating downward, creating a heavier and more believable collapse effect.
Advanced Rotation Physics
Custom quaternion-based rotation allows trees to tilt naturally instead of staying locked to rigid axis movement.
Cleaner Visuals
Removed floating entity shadows during animations for a cleaner and more polished appearance.
Improved Landing Impact
Heavy wood impact sounds now play when trees hit the ground or water.
Internal Cleanup
Removed obsolete FallingBlock-related handling and simplified the animation system internally.
☕ Java 21 Support
Timbr now officially targets Java 21 for modern runtime compatibility and future stability.
Technical Improvements
- Migrated animation engine from
FallingBlock→BlockDisplay - Improved interpolation handling
- Better rotational math using JOML quaternions
- Reduced visual jitter during animations
- Removed deprecated listener logic
- General cleanup & optimization
Result
Tree felling now feels:
- Smoother
- Heavier
- More immersive
- More modern
- More cinematic
Thanks for using Timbr 🌲
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:LlEg5nIE:Ek6kDRKk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LlEg5nIE:Ek6kDRKk"
}

