Tags
Creators
Details
Licensed ARR
Published 3 years ago
Updated 3 days ago
All versions
1.1.5-neoforge-mc1.21
Release
Ore Growth 1.1.5last year 1,709
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
Ore Growth 1.1.5
- Added compatibility for Applied Energistics 2 growth accelerators
- Fixed ore growth recipes sometimes being null when loading single player worlds, leading to no ore clusters
Ore Growth 1.1.4
- Fixed packet error when an ore growth recipe loot table condition could not be formatted
Ore Growth 1.1.3
- Fixed breaking particles for crystals showing the wrong texture
Ore Growth 1.1.2a
- Fixed Mekanism recipes not working
Ore Growth 1.1.2
- Fixed recipe result stack being leaked leading to weird drops
Ore Growth 1.1.1
- Fixed crystals not checking the used tool when giving drops
Ore Growth 1.1.0
- Ore growth recipes have been revamped:
- A single recipe may now have multiple 'base' blocks
- Recipes can now specify drops for specific growth ranges
- Items can now have a specific chance of dropping rather than always dropping
- Drops can now pull from a loot table
- All default recipes, including mod integration ones, have been updated
- Added integration with Roughly Enough Items to display ore growth recipes
- Added compatibility for Applied Energistics 2 growth accelerators
- Added recipes for ores from Modern Industrialization
Ore Growth 1.0.11
- Initial release of Ore Growth for Minecraft 1.21 & 1.21.1
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:psKAO98W:T10bBiq6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:psKAO98W:T10bBiq6"
}

