Tags
Creators
Details
All versions
0.0.1+dev-1e3aa33f
Beta
0.0.1+dev-1e3aa33f2 weeks ago 3
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Release 0.0.1+dev-1e3aa33f
Highlights
- Added the multiblock Detector screen, openable from air, with rendered selection mask, clear-selection action, and localized direction labels.
- Added a standalone Upgrade Bus; Upgrade Bus modifiers are aggregated and the bus texture updates dynamically when formed.
- Reworked block previews with mouse selection, async rendering, and a JEI preview transformer.
- Added independent custom machine text in Jade, controller text replacement, and data storage predicates; tick machines now expose component values and metrics.
- Made JEI recipe integration extensible while preserving item alternatives and custom recipe outputs.
Fixes
- Fixed JEI recipe display, sync, transfer output restoration, and unexpected JEI recipe loading during server start.
- Fixed recipes not invalidating when Upgrade Buses change.
- Fixed detector selection mask winding and hardened the detector export screen.
- Fixed a capability lifecycle lock inversion along with capability state/sync/display delegation issues.
- Fixed duplicate data storage binding on controllers.
- Fixed a Jade display error when ticking machines.
Performance
- Improved preview rendering and tick machine API performance; preview rendering is now async.
Maintenance
- Refactored recipe, capability, and modifier internals to registry/SPI-driven designs and isolated legacy/adapter layers.
- Strengthened JEI transfer, capability lifecycle, and adapter contract test coverage.
- Moved wiki content into a single source repo and updated changelog CI.
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:IhePW0fr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bUctkb7B:IhePW0fr"
}

