1.0.0-neoforge
Compatibility
Changes
Also as a NeoForge mod.
The same pack as the data pack download, without any extra code - put the file into mods/. No other mod needed. Same switch: /scoreboard players set #enabled flr_cfg 0 restores vanilla decay.
Run on a real Minecraft 26.3 NeoForge server against the same server without the file: with the file the leaf sweep removes non-persistent leaves, placed leaves stay, and all 14 leaf types clear; without it none of that happens. Only 26.3 is listed because that is the only version this file was run on.
On 26.3 the fast trigger does not cover poplar logs in this file; poplar crowns still clear with the slow background sweep.
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:rPBDo9Bk:7fPfiEza"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rPBDo9Bk:7fPfiEza"
}

