Tags
Creators
Details
26.1.2.124
Compatibility
Changes
26.1.2.124
Changes
- Updated CoolerConfig version to fix conflict with other mod that use newer version of it
Note: Legacy sapling, leaves, and leaf fragment are now deprecated and will be removed completely once this mod is marked as release (Once removed, block/item that is not migrated will disappear)
How to migrate?
- Download any ResourcesTrees 26.1.2 BETA version
- If you have any custom resources type in datapack, copy the JSON files to
/config/resourcestrees/resources_type/(Both server and client side) - DO NOT DELETE JSON in datapack until migration complete
- Load into the world
- Ensure the chunk that contain resources tree block/item loaded
- Migration done immediately the block/item is loaded
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:K5BPYFo9:9sDYqEAA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:K5BPYFo9:9sDYqEAA"
}

