Tags
Creators
Details
All versions
0.0.1+dev-43b474ae
Beta
0.0.1+dev-43b474ae3 weeks ago 1
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Release 0.0.1+dev-43b474ae
Highlights
- Added recipe machine tick hook API with KubeJS bindings, persisted effective recipe runtime snapshots, and integrated public machine behavior contexts.
- Exposed controller screen scopes to KubeJS and added readable number formatting.
- Added a data storage overlay with localization support.
- Added custom rendering for JEI recipe slots.
- Added machine IO view, output simulation metadata, and extended recipe planning output transactions.
Fixes
- Preserved recipe hooks across chunk unloads and KubeJS machine behavior callbacks.
- Fixed recipe tick behavior.
- Fixed JEI recipe transfer counts, compacted JEI recipe quantities, and hardened JEI quantity rendering.
- Retried output planning with lower output parallelism after reservation failures.
- Rejected incomplete effective recipe runtime snapshots.
Performance
- Optimized factory runtime hot paths.
Maintenance
- Added tests for recipe machine tick hooks and tick IO lifecycle coverage.
- Updated README with development status and usage warnings.
- Updated documentation and localization examples for tick hooks and the data storage overlay.
Full commit list
- ci: rename (43b474ae)
- fix: preserve recipe hooks across chunk unloads (aa053e3a)
- feat: new 5 digital clear (c2e7ef52)
- fix: recipe tick fix / docs: example fix (f25d242f)
- test: cover recipe machine tick hooks (70d8a7a4)
- feat: invoke recipe machine tick hooks (bda0ea75)
- fix: preserve kubejs machine behavior callbacks (979e19f0)
- feat: expose recipe tick hooks to kubejs (19401c1f)
- stage commit: 这tick hook我自己还用不来真服了 (536e04ce)
- feat: add recipe machine tick hook API (066224ca)
- stage commit: add jade info / examples for tick (0d615eda)
- feat: max para set to long.max (14772764)
- feat: expose controller screen scopes to kubejs (0584ce93)
- test: update data storage overlay expectation (e083af87)
- docs: clean (b44c2a3d)
- temp commit / feat data storage overlay (b1e061c2)
- docs: specify data storage overlay localization (8d38e399)
- feat: JEI recipe slot custom render (2233f2ab)
- fix: address final review findings (a6eae6e2)
- fix: address Task 7 final review findings (f5fa61d3)
- test: propagate recipe callback assertion failures (ef61b073)
- test: complete Task 7 review assertions (cfd81bc2)
- test: strengthen Task 7 lifecycle assertions (71e6f3d5)
- test: cover Task 7 tick recipe io lifecycle (14e30220)
- fix: address Task 6 review findings (e8bfc2ce)
- test: verify tick recipe io lifecycle bridge (dd356f05)
- fix: address Task 5 review findings (50e384dc)
- feat: complete Task 5 machine tick IO lifecycle (84aae799)
- fix: address Task 4 review findings (88673ead)
- feat: persist effective recipe runtime snapshots (f6f7ef52)
- fix: reject incomplete effective recipe snapshots (9f032c29)
- fix: address Task 3 review findings (aef9ffef)
- feat: integrate public machine behavior contexts (72f3134e)
- fix: retry lower output parallelism after reservation failure (c6abb881)
- fix: address Task 2 review findings (9d1bd467)
- feat: extend recipe planning output transactions (c8e57c59)
- fix: harden JEI quantity rendering (04c0bb88)
- feat: add machine IO view and output simulation metadata (dfaffc32)
- fix: preserve JEI recipe transfer counts (dc60cf1d)
- fix: compact JEI recipe quantities (d4398d96)
- feat: expose readable number formatting (6ccd80a4)
- test: fix unstale gametest (60a61bda)
- chore: gradle直接爬 (70931e83)
- feat: 这个傻子Agent怎么不自己commit啊 (1da3194f)
- Update README with development and usage warning (f934880c)
- Revise README for development status and distribution (c1eca834)
- perf: optimize factory runtime hot paths (b852ce9d)
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:hXoDePkD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bUctkb7B:hXoDePkD"
}




