Tags
Creators
Details
All versions
0.0.2+efa2122d
Release
0.0.2+efa2122dlast week 14
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Release 0.0.2+efa2122d
Highlights
- Added standalone upgrade buses, aggregate upgrade modifiers, and automatic upgrade textures when formed.
- Added a network interface block with key cards, persistent connections, and KubeJS-exposed machine network requests.
- Added a multiblock detector screen with selection-mask visualization.
- Expanded terminal workflows with a configuration screen, persistent item storage, and synchronized controller/preview state.
- Added KubeJS/controller integration for custom controller screen text, Jade text, recipe tick hooks, and data-storage predicates.
Fixes
- Fixed crash when a multiblock structure is too large.
- Fixed shared IO recipes not restarting after recipe finish and cleared stale factory/controller state after structure changes.
- Fixed multiple multithreaded recipe runtime races and stale recipe failures.
- Fixed machine connection/data-storage serialization and made item storage deserialization atomic.
- Fixed Mix Port behavior and ItemBus/combined-port inventory handling.
- Fixed JEI recipe sync/transfer output restoration and removed unexpected JEI recipe loading during server start.
Performance
- JEI preview compilation no longer repeats schema calculations; the recorded large preview case dropped from about 300s to 1s.
- Structure checks are reduced and structure cache now builds on first placement.
- Optimized data-storage/network access and factory runtime hot paths.
Maintenance
- Refactored machine recipes and runtime onto registry-driven capability APIs; legacy recipe/controller compatibility layers were removed.
- KubeJS modifier registrations now use ID-based structure modifiers.
- Added extensible capability, transfer strategy, controller renderer, and JEI integration APIs.
Optional dependencies
Any compatible version
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:bUctkb7B:afdcSYPb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bUctkb7B:afdcSYPb"
}

