1.2
Compatibility
Changes
Falling Trees v1.2 — The "Stability & Growth" Update (1.12.2) Performance & Core Engine Refactor Zero-Leak Memory Management: Migrated all internal data tracking to WeakHashMap. Your RAM will thank you—data for unloaded worlds and players is now automatically garbage-collected.
Thread-Safe Destruction: Implemented CopyOnWriteArrayList for block queues. Say goodbye to those annoying ConcurrentModificationException crashes when the server and client tried to talk at the same time.
Proper Sided-Proxy Architecture: Fully decoupled Client and Server logic. This build is now 100% Dedicated Server safe. No more "Client class not found" crashes on startup!
Mod Compatibility & New Mechanics Pam’s HarvestCraft Integration: Your favorite fruit trees are now fully supported! Fruits, nuts, and spices (cinnamon, etc.) are recognized as part of the canopy. They won’t hang in the air anymore—they’ll drop naturally with the leaves.
Optimized Tree-Search Algorithm: Rewrote the Breadth-First Search (BFS) logic. It's faster, smarter, and won't accidentally "eat" your wooden house if it's built too close to the forest.
Dynamic Stick Drops: Added a configurable chance for sticks to drop from decaying leaves. Nature is finally rewarding your hard work!
Visual Polish Fluid Leaf Particles: Updated LeafParticle with a smooth alpha-fade effect. Leaves now drift and vanish gracefully instead of just popping out of existence.
Stable HUD: The destruction progress bar is now more responsive and synced in single-player sessions.
Dev Note: This is the definitive "Legacy" edition for 1.12.2. With the architecture now stabilized, the foundation is set for the upcoming 1.20.1 port, which will utilize modern Minecraft Tags and Data-Driven mechanics.
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:gFbXtn5j:jHcdg4aC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gFbXtn5j:jHcdg4aC"
}

