All versions
1.3.0
Release
1.3.02 months ago 144
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Any compatible version
Changes
The performance release!!!
This release was mainly focus around performance, that why is significantly increased the release cycle
Performance upgrades
- Rewritting Bee job calculation
- Bees are no longer entities, but client side particles
- Large jobs are now processed over multiple ticks when calculating how bees need to fly for them, to not cause a huge spike in tps drop
- Bees only check if they are correct once they reach a checkpoint
- Bees actually only exist on the client side, the server side only keep tracks of where the be is, without any entity actually existing
The Schematic Deployer
- New block which can be used to automatically trigger a programed schematic via. redstone
- Use the relative or absolute mode to move set exactly where to place the schematic
The pickup planer
- A new tool to pickup any items in the area and insert them into your system
New upgrade system:
- Upgrades in the portable beehive are now a bit more unique and different to use than before, giving you more customizability to your likins ;)
New upgrades!
- Drone view, get a birds eye view over your builds and easily place schematics
- Honey Tank, increase storage of your portable beehive
- Inventory Access: Access shulker boxes in your inventory for items
New performance configs
- New options to match performance with your server, the mod set quiete defensive default values, increase them to your liking
Optional dependencies
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:eYbO4GyQ:3iVccu7Z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eYbO4GyQ:3iVccu7Z"
}

