1.0.2
Compatibility
Changes
Timbr v1.0.2 Changelog
Realistic Rigid-Body Sideways Tree Falling Animation 🌲💥
✨ New Features & Improvements
-
Enhanced Rigid-Body Rotation Physics
Trees no longer break instantly or collapse into a vertical pile. They now tilt and fall sideways based on the player's facing direction, creating a much more natural and immersive falling animation. -
Custom Proportional Feedback Controller
Added a custom real-time feedback controller that continuously overrides Minecraft's default gravity and entity drag to maintain precise tree alignment while rotating. -
Connected Leaf Canopy Animations
Leaf canopies are now included in the felling animation. An optimized single-pass BFS scanner detects and animates connected leaves falling together with the trunk. -
Immersive Trailing Leaf Particles
Falling leaves now emit matching environmental particles depending on tree type:- Cherry → pink petals
- Crimson → crimson spores
- Warped → warped spores
- Overworld leaves → green spore blossom particles
-
Accurate Item Drop Simulation
Block drops are pre-calculated before the fall animation begins, ensuring:- Fortune works correctly
- Silk Touch is respected
- Axe durability behaves properly
- Drops appear at the final landing location
-
Stability & Anti-Glitch Protection
Temporary FallingBlock entities are marked as non-persistent to prevent ghost blocks or chunk corruption during restarts and unloads.
⚙️ Configuration & Customization
New options added to config.yml:
# Falling tree animation settings.
animation:
# Enable realistic falling tree animation.
enabled: true
# Maximum logs to animate at once.
max-animated-logs: 128
# Maximum leaves to animate at once.
max-animated-leaves: 150
# Horizontal speed multiplier of the falling tree.
fall-speed: 1.0
# Enable trailing particles on falling leaves.
leaf-particles: true
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:RmQhb8aL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LlEg5nIE:RmQhb8aL"
}

