Tags
Creators
Details
All versions
0.0.2+dev-2b881e07
Beta
0.0.2+dev-2b881e076 days ago 12
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Release 0.0.2+dev-2b881e07
Highlights
- Added an optional Mekanism bridge with chemical/heat handlers, machine port storage, transfer policies, screens, KubeJS recipe declarations, and JEI/Jade integration.
- Fluid and chemical inputs now accept
consumeChancethrough KubeJS and the public API; JEI shows the chance as an overlay/tooltip. - Jade controller tooltips now show a graphical recipe progress bar and localized recipe outputs without a redundant recipe ID row.
- JEI chemical recipe handling now works with Mekanism: recipes are no longer rejected, full stacks are shown, quantities display in buckets, and chemicals are exposed to transfer slots.
- Recipe IO planning now supports bidirectional capability directions, with auto-I/O gating and deduplicated port aliases.
Fixes
- Fixed Mekanism + JEI chemical recipe rejection, display, and transfer slot exposure.
- Fixed heat port behavior: output heat ports no longer absorb ambient heat, capacity survives reloads, Mekanism heat port simulation is correct, and temperature/heat display and clearing are fixed.
- Fixed Jade/JEI display of heat and chemical consumption amounts.
- Fixed failure reason reporting for output-limit, data-value-limit, and chemical I/O cases.
- Fixed startup collection so KubeJS startup machines are visible to server scripts; public recipes now complete after component binding.
- Fixed capability direction handling: ambiguous directions are rejected, runtime directions are preserved, and bidirectional capabilities are isolated from auto I/O.
- Fixed recipe search behavior in blueprint/recipe selection.
- Fixed block state export and up/down direction checks.
Performance
- Improved chemical handling performance.
- Improved blueprint/recipe search performance.
Maintenance
- Moved the new API into the public package and completed public API adapters; example machines now use the public Java API.
- Added tests for Mekanism ports, JEI chemical ingredient types, Jade recipe output data, and planner direction/rollback semantics.
Optional dependencies
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:MfkT02cK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bUctkb7B:MfkT02cK"
}




