Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 2 years ago
All versions
1.21.1-5.0.10-NeoForge
Release
Oh-The-Trees-You'll-Grow-NeoForge-1.21.1-5.0.10last year 15.3K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
5.0.10
- Fix trunks.
5.0.9
- Fix log decorators placing on leaves.
- Add more checks to fail tree growth.
5.0.8
- Fix placing tree decorator blocks.
5.0.7
- Rewrite tree growth logic to account for solid blocks and the surrounding environment prior to growing/placing.
5.0.6
- Track tree decoration positions when placing tree feature.
5.0.5
- Fix missing trunk/leave positions in tree decorators.
5.0.4
- Fix adding and sort trunk/leave positions and leaves to their respective sets. Fixes various issues with tree decorators.
5.0.3
- Fix canopy log builders piercing terrain
5.0.2
- Fix NeoForge Jar Missing AccessTransformer
- Make TREEFROMSTRUCTURENBT final
- Fix Deprecation of FMLJavaModLoadingContext.get in forge
- Adjust some Publishing Names
5.0.1
- Add check to prevent logs from being placed where bedrock is present
5.0.0
- Update to 1.21.1
4.0.0
- Update to 1.20.6
- Move Datagen to NeoForge
3.0.0
- Update to 1.20.4
2.0.0
- Update to 1.20.2
- Add NeoForge Support
- Remove CorgiLib Legacy Support
1.3.0
- Rewrite Build Script
- Generalize Registration
- Add TreeFromStructureNBTConfig constructor that has an empty tree decorator
1.2.0
- Move project to Arch Loom
- Add rotated block support
- Add example mushroom features
1.1.2
- Fix Tree Decorator Types not being registered on Fabric
- Use ForgeRegistries for Registration on Forge
1.1.1
- Fix incorrect Fabric version.
1.1.0
- Remove Regutils dependency
1.0.0
- Release
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:g8NOG5OR:BOcSuw5O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:g8NOG5OR:BOcSuw5O"
}

