1.9.2-beta
Compatibility
Changes
Beta 1.9.2
Release date: 2026-08-30
Stage: Beta
Summary: Polishes the existing 1.9 visuals and synchronizes Terminal feedback and traffic pulses without changing the Core, Thread, Clock, IDD, or IP architecture.
Added
- Validation for physical five-pixel IDD Rack bays and four-piece one-pixel console frames.
- Server-timestamped Data Pulse events that clients interpolate across the cached route.
Changed
- Network Fiber uses a center-and-arm multipart model with non-stretched supplied UV regions and matching connection collision.
- Thread placement selects a directly adjacent valid compute axis before falling back to the clicked face.
- Successful transfers publish their committed physical IDD state before Terminal feedback is synchronized.
Fixed
- Removed the obsolete stretched grey LPU connection overlay while preserving native
lpus_lightsanimation. - Corrected Thread and Fiber model rotation so artwork follows block orientation.
- Made Data Terminal and DERM borders physical one-pixel frame pieces visible from side angles.
- Added physical Rack bay rails around the five-pixel recess while preserving six-pixel inserted drives and one-pixel protrusion.
- Prevented repeated shift-transfer packets from reserving the same player inventory slot twice.
- Removed duplicate numeric generator-buffer output beside the existing Jade/WTHIT buffer bar.
- Started transfer pulses when Requests are accepted instead of after storage has already changed.
Removed
- Per-step post-commit Data Pulse events and the unreferenced LPU grey strip model from active blockstate selection.
Known Issues
- Final texture orientation, multipart junction appearance, and multiplayer latency behavior still require manual in-game inspection when a graphical client is available.
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:AJmOFSPL:xBNbMegL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AJmOFSPL:xBNbMegL"
}

