All versions
1.1.0
Release
Create: Buzzy Bees 1.1.04 months ago 48
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
v1.1.0
New Features
- External Schematic Browser — Browse, search, and download schematics from createmod.com directly in-game. Includes detailed schematic viewer with WebP thumbnail previews.
- Job Detail Screen — Right-click a construction job's bounding box to view live progress, status, batch info, and cancel the job.
- Crafting Recipes & Advancements — Added recipes for Construction Planner, Deconstruction Planner, and Drop Items. Added corresponding advancements.
- Portable Beehive Integration — Bees can now work from portable beehives carried in a backpack, tracking the player's position.
Improvements
- Schematic Ghost Preview — Refactored ghost block rendering for better performance and scalability when previewing large schematics.
- Beehive Range Rendering — Improved mechanical beehive range visualization.
- Bee Task Behaviors — Enhanced drop-off logic and item gathering. Bees handle edge cases more gracefully (stuck detection, orphan recovery, hive entry retries).
- Stale Component Purging — Bee networks now detect and clean up ghost components that weren't properly unregistered.
- Performance Improvements — Optimized rendering paths and network operations.
Bug Fixes
- Fixed construction rotation/mirror being lost when using Create's rotate/mirror tools before clicking Construct.
- Fixed cancel button in Job Detail Screen sometimes not responding to clicks.
- Fixed browser keybind (B) queuing up presses and instantly opening the UI when switching to the Construction Planner.
- Fixed Logistics Port ponder scene: resolved warning on last instruction and fixed text/icon clipping.
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:CqQAUFMD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eYbO4GyQ:CqQAUFMD"
}

