Tags
Creators
Details
All versions
0.0.3+d8286afa
Release
0.0.3+d8286afa3 days ago 26
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Release 0.0.3+d8286afa
Highlights
- Added async machine and factory execution, including async structure matching, recipe/capability IO planning, chemical planning, shared IO fences, and cancelation, reducing blocking and idle gaps.
- Added AE2 integration: ME input/output/stocking interfaces, pattern-interface crafting bridge, pattern reservations/transactions, memory-card pattern routing, Terminal ME mode/network info, Jade connectivity, optional ExtendedAE support, and AppliedFlux compatibility.
- Added stage and machine-level recipe requirements with stage-aware UI: requirements are enforced/displayed, controller/factory screens and menus expose matched stage and stage count, and Terminal/build diagnostics report stage-specific status.
- Added Mekanism chemical and heat support: chemical/heat handlers, ports and screens, KubeJS declarations, JEI/Jade display, and consume-chance support for fluid/chemical inputs.
- Added blueprint preview and UI improvements: open preview from air use, shared preview panel in JEI, material grids, selection highlighting, controller recipe output display, progress bars, shift-scroll info, output interface priority, and wrench interaction with MMCR blocks.
Fixes
- Fixed a Mekanism overlay bug.
- Fixed AE2 pattern interface title/performance/lifecycle issues, single-lane and multi-thread crafting, output fallback/rollback, reservations, filters, and Jade registration.
- Fixed async regressions affecting
lastRecipein single- and multi-threaded modes, shared IO conflicts/continuations, factory fallback/search results, stale lifecycle cancellation, and batch rejection causing tick loss. - Fixed recipe stage structure checks and unforming, including non-current stage scans and
expandStructureBlockDirty matching. - Fixed KubeJS recipe pool reloads, validation, stale machine bindings, cross-pool conflicts, level requirement sync, and startup recipe/level visibility.
- Fixed Mekanism heat/chemical issues: heat port capacity on reload, ambient heat absorption, bidirectional/simulated heat handlers, namespace/failure reasons, and chemical performance.
- Fixed JEI/Jade compatibility for Mekanism chemical/heat recipes, chemical quantities/transfer slots, fluid/chemical consume-chance overlays, recipe output units, and Jade return output filtering.
- Fixed blueprint preview scaling/render/highlight/drag issues and the dynamic overlay lifecycle compile error.
- Fixed ExtendedAE input interface crashes, menu routing, interface data packaging, and extension performance.
- Fixed recipe output limit handling, data value limits, energy-prefetch missing inputs, consume chance 0 async bugs, and loot table loading when other mods are not present.
Performance
- Reused shared IO validation and factory lane analysis to avoid repeated work.
- Validated shared IO requests once and batched async coordinator work.
- Deferred shared IO start grants and completed continuations at tick fences.
- Added empty-tick jumps and continued last recipes without idle gaps.
- Added async cancelation and worker-based factory lane searches.
Maintenance
- Updated tests/CI for async controllers, AE2/Mekanism/ExtendedAE integration, recipe pools, and stage/level requirements; removed unstable tests and debug noise.
- Refactored package structure, config, public API/KubeJS adapters, recipe ownership/failure diagnostics, build scripts, and documentation/issue templates.
- Migrated recipe handling to versioned machine recipe pools; KubeJS/JEI recipes and level requirements sync through that pool path.
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
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:uyIYLJw7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bUctkb7B:uyIYLJw7"
}

