Tags
Creators
Details
1.10.1
Compatibility
Changes
New in this release
- šŗ Greenhouses no longer lets mobs slip past the Limits addon. If you run Limits with entity limits, a greenhouse could keep spawning a mob type after the island was already at its cap ā the reported case was ghasts at 4/3. Greenhouses did not cause the extra spawn directly: when Limits cancelled a spawn at the limit, Greenhouses carried on with the dead entity, ran its "does this mob fit inside the glass?" check and, when it did not fit (ghasts are 4Ć4Ć4, so often), called
remove()on it. Paper fires anEntityRemoveEventfor that even though the mob never entered the world, and Limits counted it as a real removal ā so its counter crept downward and the next spawn was let through. Cancelled spawns are now left alone entirely (#148).
šŗ If you saw this: Limits' counter for the affected island is still wrong until it is rebuilt. Have the player run
/is limits recount(or use the admincalccommand) once after updating. A matching hardening in Limits so it ignores such removals is in BentoBoxWorld/Limits#297.
Compatibility
āļø BentoBox API 2.7.1 āļø Minecraft 1.21.5+ āļø Java 21
Upgrading
- Take backups of your server, for safety
- Download this jar and put it in your addons folder - delete the old one
- Restart the server
- You should be good to go!
What's Changed
- Ignore cancelled mob spawns instead of calling
remove()on them by @tastybento in https://github.com/BentoBoxWorld/Greenhouses/pull/148
Full Changelog: https://github.com/BentoBoxWorld/Greenhouses/compare/1.10.0...1.10.1
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:ijw0Idmm:OqiE23JJ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ijw0Idmm:OqiE23JJ"
}

