Tags
Creators
Details
Licensed MIT
Published last year
Updated 2 months ago
All versions
1.20.1-0.6.0
Release
Create: Mobile Packages 1.20.1-0.6.07 months ago 4,786
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Changes
Create: Mobile Packages - v0.6.0 - 01.02.2026
Breaking Changes
Logistics Network support
Warning! This will break all existing ports. They need to be replaced to link to a logistics network!
- Link a bee port to a logistics network or place one to create a new one
- Robo Bees will only fly to Robo Bee Ports and Players within their network
- The Robo Bee Item can be linked to a logistics network
- If a Robo Bee Item is not connected to a network, then the bee will fly to any port (closest)
- Players can add themselves to a logistics network by clicking the new button on the bee port GUI
- Players can see all networks they are part of with the hotkey
H - Players can pick up Robo Bees in their network by hitting them
Changes
- Simplify Robo behavior state system
- Add nametag
No valid targetto Robos - Add Abstractions for the target
- Bump create_version to 6.0.8-289
- Disable dimension travel for robos (nether & end portals) (#250)
- Update Translations (#243, #269)
Bug Fixes
- Add support for Create
6.0.7(#241) - Fixed item duplication in the Mobile Packager (#270)
- Fixed missing Robo Bee clear recipe (#276)
- Fixed recipe freezes (#279)
- Fixed bee port duplication bug (#252)
Additions
- Added support for EMI (#279)
- Added
/cmp robos clearcommand to remove all robos (#261) - Added Mobile Packager for packaging items on the go
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:1vXRfEHZ:b6GphAQ9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1vXRfEHZ:b6GphAQ9"
}

