Tags
Creators
Details
All versions
0.0.1+dev-234eb28e
Beta
0.0.1+dev-234eb28e2 weeks ago 1
Compatibility
Minecraft: Java Edition
26.1.2
Platform
NeoForge
Supported environments
Client and server
Changes
Release 0.0.1+dev-234eb28e
Highlights
- Introduced terminal services with persistent terminal data, richer terminal information, and a terminal configuration screen.
- Added machine network interface blocks and key cards, including KubeJS-accessible machine network requests.
- Added a controller renderer public API with custom controller renderer registration, data-storage snapshots, and formed structure block counts.
- JEI structure previews now use blueprints and can render level requirements as slots.
- Added colorful tooltips and UI text.
Fixes
- Fixed a crash when forming oversized structures.
- Fixed terminal controller access/stage validation, preview synchronization/build-state updates, dimension label conversion, action value bounds, and scan coverage for larger structures.
- Fixed JEI category level block slot placement and rendering order.
- Fixed controller renderer dispatch and hardened validation for controller machine IDs and data-storage snapshots.
- Fixed network interface connection persistence/coordination, serial additional data, mix port behavior, and key card target-result priority.
- Fixed falling-block checks during structure validation.
Performance
- JEI preview compilation is significantly faster for large structure-heavy previews: schema caching and multi-threaded mesh generation reduced one large preview from about 300 seconds to about 1 second.
- Structure cache is built on first placement, and redundant structure checks were removed.
- Optimized data storage and network access.
Maintenance
- Removed the Gecko dependency.
- Added tests covering terminal storage/resolver behavior, rejected terminal demolish drops, network interface lifecycle, and controller batch broadcast fixtures.
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:h4YkqjZt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:bUctkb7B:h4YkqjZt"
}

