Tags
Creators
Details
All versions
1.0.0-alpha.15
Alpha
1.0.0-alpha.154 years ago 183
Compatibility
Minecraft: Java Edition
1.19.2
Platform
Forge
Supported environments
Client and server
Changes
-----{ 1.0.0-alpha.15 }-----
- It's a brand-new mod.
Notable Highlights:
- Apiaries are no longer a multiblock and have their own inventory. They also no longer have the unique bee requirement and can hold up to 20 bees at T4
- The Breeder now has its own inventory and is separate from the apiary.
- Honey Generator is now recipe driven and can be upgraded.
- Centrifuge multiblock can be confusing at first but can also become a very powerful multiblock. In a general sense, it's like taking a bunch of small multiblocks and turning them into one large one. It can be very simple, or it can be very complex. You decide!
- We will be making a video guide on using the Centrifuge multiblock very soon, which should be very helpful in using it.
- There is a
/resourcefulbeescommand which you can use to print json templates to the logs. The command isn't complete, but can get you started. Feel free to ask questions in Discord! - Bees have significantly more customization options than they did in 1.16.5.
- Most jsons are datapack driven.
- Machines are all recipe driven.
Please keep in mind this mod is still in alpha. There can and likely will be more breaking changes, and as such the mod should only be included in packs if you accept the risks.
We are releasing this publicly in such an early state because we would like to get more feedback from the community. We need to know what you like and don't like. What bugs are there? What is confusing and should be clarified better? How can we improve and make this mod the best bee mod there is?
Please report any and all bugs on our Gihub Issue Tracker
Feel free to ask questions in our Discord
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:jcJ8MbSV:LGSZ04aw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jcJ8MbSV:LGSZ04aw"
}

