All versions
1.10
Release
Mystian Apiary 1.103 days ago 40
Compatibility
Minecraft: Java Edition
1.20.1–1.20.6
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Mystian Apiary 1.10 Changelog
Flower Conversions
- Bees that convert their flowers now actually do it in the apiary. Sussy Bees turn sand into suspicious sand, Obsidian Bees turn a Redstone Bee egg into a Flux Bee egg, and so on.
- Fluid conversions have also been fixed (hopefully). Magmatic Bees create lava from cobblestone, and Frosty Bees turn water buckets into ice and hand the bucket back.
Bug Fixes
- Grave Bees, and possibly others, didn't work. Flowers are now checked straight from the Flower Box instead of being placed in the world, so graves are never eaten or duplicated.
- Fluid pipes pulling from a big Storage Box could tank TPS on 26.1. This should be greatly improved.
- Added some small communication between pipes and the storage box, hopefully improving transfer performance from slot checks.
- Having lava in a storage box could sometimes cause a crash
- Hoppers can no longer pull upgrades out of the Controller and push junk into its slots.
- Piping a Sturdy Bee Cage into the Bee Box ate the cage on 1.21.1 and 26.1. You get the empty one back now, like on 1.20.1.
- Automation could shove items into storage slots that were holding fluid.
- Fluids pulled out of storage would sometimes lose their NBT on 1.20.1.
- Small improvements for behavior genes
- The Gene Sampler no longer samples baby bees, matching Productive Bees.
- Damaged iron tools count as Iron Bee flowers on 1.20.1, like in a Productive Bees feeder.
Performance
- A full Storage no longer gets retried every single tick.
- Bees finishing a cycle stopped making the whole box re-check its flowers.
- Bunch of other backend improvements/tweaks.
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:4YKkzsCe:lMA9AJIR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4YKkzsCe:lMA9AJIR"
}

