1.9.5-beta
Compatibility
Required content
Changes

Logicore 1.9.5 — Rack Cleanup and Less Confusing Wake-Ups
Okay, this one is a small polish update. Mostly fixing Rack textures that were fighting each other and making sleeping networks less confusing to use.
Keep in mind this is still beta, so visual bugs, logic bugs and weird edge cases may still be hiding somewhere.
Rack polish
The IDD Rack keeps its current 3D model, but its textures should behave much better now.
- Exterior faces now show the normal machine-side texture cleanly.
- Removed the accidental green tint from the connector at the back of each slot.
- Every IDD capacity now uses its own existing drive artwork instead of one generic tinted overlay.
- Drive textures are rendered as authored, without runtime recoloring.
- The existing connected, transfer and offline status lights still render on top.
The Rack was already shaped correctly. This update just stops its texture layers from arguing with each other.
Overclock GUI
The green selected marker was slightly misaligned because apparently one pixel can be incredibly annoying.
It has been moved one pixel left and one pixel up. Button positions and hover areas have not changed.
Network wake-up feedback
When Power Off While Idle is enabled and an import or export wakes the network, the Data Terminal now prioritizes:
Initializing Network...
This stays visible while initialization is happening instead of being hidden by the normal importing or exporting message. Once the network finishes waking, the regular operation status takes over.
Energy notes
The energy paths were checked for client-side generation, duplicate generator ticking, buffer overflow and free energy during network initialization. No new balance changes were made in this release—the long fuel durations and strong production of later generators are still the existing intended values.
Overclock selection and network operations remain server-authoritative.
Still beta
This is still a beta build. Expect the occasional visual oddity, strange edge case or machine deciding today is the day it develops free will.
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:pS4hP5Tk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AJmOFSPL:pS4hP5Tk"
}


