1.1.0
Compatibility
Changes
1.1.0] - 2025-04-26
Changed
Optimized planting logic to minimize performance impact:
Introduced event-based planting using ServerEntityEvents.ENTITY_LOAD to handle newly spawned Nether Wart items.
Added a fallback scan every 5 ticks (TICK_INTERVAL = 5) around each player in a 32-block radius instead of scanning the entire world.
Added a standalone LICENSE file (MIT) in the project root.
Restricted scanning to the Overworld only.
Fixed
Prevented unintended item merging by removing merge behavior (avoids premature despawn when items are clustered).
Eliminated global entity box scan to reduce CPU overhead on servers and clients.
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:JUfE5YgR:IuDzxZUG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JUfE5YgR:IuDzxZUG"
}

