1.0.63
Compatibility
Changes
Short changelog for 1.0.19–1.0.63: Added monitor networking, remote monitor services, monitor walls, terminal surfaces, screensavers, display links, and video cabling. Added full PLC systems: programming GUI, digital/analog I/O, timers, counters, latches, PID, trends, remote control, and dashboards. Added RedNet auto-provisioning, DHCP-style leases, router discovery, and network diagnostics. Added Universal and dedicated sensors with quality-aware telemetry, PLC bindings, Device API, and RedNet support. Added NAS storage, portable SSDs, and the Materializer automation block. Added extensive custom electronics models, textures, rendering improvements, and the Device Control Center. Added the searchable in-game TerminalCraft Guide and expanded PLC template library. Added 16-color Shielded Red Alloy and Network Cable, bundled Red Alloy/Network trunks, four-lane routing, previews, and diagnostics. Added SCADA supervisory control: tags, historian, alarms, roles, auditing, dashboards, and authenticated controls. Added advanced HMI dashboards with pages, widgets, touch controls, monitor walls, and a graphical designer. Added optional Create, Mekanism, and SecurityCraft integrations, including automation, chemical telemetry, machine sensors, and PLC templates. Evolved surface cabling through lattice routing to the final single-cable RedPower-style system. Added independent 16-channel computer bundled I/O and strict channel isolation. Added solid-color cable visuals, restored unshielded Red Alloy Wire, the Red Alloy Capacitor, and face-oriented cable selection shapes.
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:SObNSDVt:WmYm7idH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:SObNSDVt:WmYm7idH"
}

