Tags
Creators
Details
1.6.0
Compatibility
Required content
Changes
There are many fixes for bone meal in this update! A couple of simple oversights made the whole feature almost useless, which hopefully now should be resolved. 🌸
➕ Additions
es_ES translations have been added this update. Thanks, Flatkat!
🔧 Changes
In visual news, spore blossoms will once again sit higher up in inventory and hotbar slots. Previously they were somewhat hiding behind the item stack counts so I'm hoping this will improve visibility, especially in distinguishing the different states from one another.
Additionally, spore blossoms no longer exclusively generate naturally beneath moss blocks. In fact, the generation location changes have been entirely reverted to vanilla. This is based on the fact that, anecdotally, spore blossoms seemed overly rare and when I found them they were almost always fully grown (no doubt as a result of having spent a long time in this particular survival world). I'm hoping that by making this change, the spore blossom variation will be more "captured in time" so to speak. If you have feedback, be sure to write a feature suggestion on the issues page!
The pink dye recipe output quantities have been rebalanced to fit better with the logic that the juvenile spore blossom states can be crafted just as easily as fully-grown ones. They have been brought down to match most small flowers, with the exception of a very slight boost for the supported Create milling and crushing recipes.
🐛 Fixes
- Spore blossoms should now correctly work with manual fertilization, fixing the following sub-issues:
- They did not display "happy villager" particles.
- They did not play the "crinkling bone meal" sound.
- They did not consume an item from the bone meal item stack.
- They did not emit the
ITEM_INTERACT_FINISHgame event.
- Spore blossoms should now correctly emit sculk sensor vibrations when recoiling and unfurling.
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:3KmV3g7F:l8ciKUfV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3KmV3g7F:l8ciKUfV"
}

