Tags
Creators
Details
1.4.0
Compatibility
Changes
Two fixes to how trees come down.
Leaf clearing now follows vanilla decay. With leaf breaking on, BlackTimber used to scan a fixed cube around each log. That left the outer one or two layers of a wide canopy behind and, in a forest, ate the leaves of a neighbouring tree that happened to fall inside the cube. Clearing now reproduces vanilla decay exactly: it removes only the leaves the felled tree was supporting and that no surviving log still keeps within range. The whole canopy comes down, outer layers included, on a tree of any size or shape, while an adjacent tree whose trunk still stands keeps every one of its own leaves, even where two canopies overlap. Player placed (persistent) leaves are still never touched.
Felling is now bounded by the axe's durability. An axe could get stuck at 1 durability and fell trees forever without ever breaking. Felling is now limited to the logs the axe can pay for, with Unbreaking honoured per log, so it can never outrun the tool. A worn axe fells the part it can afford and leaves the rest of the tree standing.
break-tool now defaults to true. The axe wears down and breaks like vanilla once it runs out mid-fell. Set it to false to protect the axe instead: it then stops at 1 durability and leaves the rest of the tree standing rather than breaking.
New: sapling replanting. A fourth per player toggle, off by default, replants a matching sapling where the tree stood. The species is read from the felled trunk: oak, birch, spruce, jungle, acacia and cherry plant one sapling; dark oak and pale oak plant their full 2x2 only when all four cells are clear; mangrove plants a propagule. It plants only on valid ground (dirt, grass, podzol, moss and the like, plus farmland; clay and mud for mangrove) and never over water, lava or an occupied block, so an unusual spot is simply left untouched. Toggle it in the player menu, with /blacktimber replant, or set the server default default-replant in the admin panel.
Config.
- New
leaf-clear-budget(default8192): safety ceiling on how many leaves a single fell may examine before deferring cleanup to vanilla decay. leaf-search-radiusis now detection only and no longer limits clearing.break-tooldefault changed fromfalsetotrue.
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:v6eAmMVH:IKHHt285"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:v6eAmMVH:IKHHt285"
}

