All versions
1.1.0
Release
Every Detail Examined. Every Weakness Addressed.3 months ago 26
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Timbr Update 1.1.0
Fixed
- Corrected server version detection to ensure modern display features are identified reliably across supported Minecraft versions.
- Fixed an issue where breaking an axe during tree felling could trigger an unexpected server error.
- Mining Fatigue removal now affects only effects applied by Timbr, leaving potion and third-party plugin effects untouched.
- Improved compatibility with protection plugins by preventing unnecessary event spam and eliminating rare startup issues.
- Significantly improved tree detection performance while enforcing configured tree size limits correctly.
- Fixed version comparison for update checks, ensuring new releases are detected accurately.
- Added additional safety checks to prevent errors when plugin information is unavailable.
- Improved particle compatibility on older server versions with graceful fallbacks where newer effects are unsupported.
- Prevented rare issues caused by invalid item drops and introduced a hard limit on animated entities to safeguard server performance.
- Fixed animated tree remnants persisting after
/reload. All temporary entities are now cleaned up properly during shutdown. - Resolved several issues introduced during internal refactoring, improving overall stability.
- Corrected tree-felling calculations so the final log is always processed correctly, even if the player's axe breaks at the last moment.
Added
-
Laydown Mode
- Trees may now fall naturally and come to rest on the ground instead of disappearing immediately.
- Branches and leaves that collide with the terrain can break into drops, whilst the remaining trunk stays intact until mined.
- Added new configuration options for:
- Fell mode (
INSTANTorLAYDOWN) - Fall speed
- Slide distance
- Ground collision behaviour
- Clear-path requirements
- Fell mode (
-
Automatic Configuration Upgrades
- Missing configuration options are now added automatically during startup without overwriting existing user settings.
- Because configuration files should evolve, not self-destruct.
-
Improved Plugin Compatibility
- Added official soft dependency support for common protection plugins, ensuring a more reliable loading order.
Changed
- Internal systems have been reorganised to improve maintainability and reduce duplicated logic.
- Improved thread safety for tree-felling operations, resulting in greater stability under heavy server load.
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:zaS8dyfy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:LlEg5nIE:zaS8dyfy"
}

