Links
Tags
Creators
Details
All versions
1.1.1
Release
create-schematic-compute 1.1.14 months ago 159
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
v1.1.1
- ✨ Add: Encapsulation node — nest sub-graphs inside a single node, double-click to expand, 48→49 types
- ✨ Add: Monitor Redstone Input — Holographic Monitor can now read Redstone Link network signals via REDSTONE_IN node
- ✨ Add: Toolbar position toggle — bottom-right button to switch toolbar (X/Compile/Run/Grid/Style) between top-left and bottom-left; position persisted to config file
- 🐛 Fix: Control Seat view jump — smooth transition between Joystick and View Angle modes (Mixin-based raw mouse delta capture, zero GLFW cursor manipulation)
- 🐛 Fix: Monitor 3D renderer redstone — 3D holographic display now correctly evaluates REDSTONE_IN nodes (was passing empty InputSource list)
- 🐛 Fix: Monitor redstone registration — late-registered listeners now receive initial signal state via force-resend; dedicated MonitorRedstoneSyncPacket for lightweight client sync
- ⚡ Perf: Comprehensive code audit — NaN guards on all arithmetic nodes (ADD/SUB/MUL/MAP/INTERP), FORMULA compilation cache, volatile thread safety on all static fields, evaluator caching (60+ FPS → graph-change-only), Sensor reflection cache, ControlSeat entity scan radius 50→2 blocks
- ♻️ Refactor: RedstoneLinkHelper — ~400 lines of duplicated redstone link code (FreqLink, registerLinks, addLink, unregisterLinks, lifecycle hooks) deduplicated across 4 block entities (Blueprint, ProgramComputer, ControlSeat, Sensor)
- ♻️ Refactor: GraphBlockEntity interface — replaces 6-branch instanceof chains in BlueprintSavePacket/BlueprintTogglePacket with single interface check
- ♻️ Refactor: Star imports eliminated — all
import java.util.*expanded to explicit imports across 6 files - 🔧 Mixin infrastructure — added Mixin AP +
LocalPlayerMixinfor Entity.turn() interception in Control Seat - 🛡️ Player disconnect cleanup — PLAYER_INPUTS now cleared per-player on PlayerLoggedOutEvent
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:1bUvJALH:5D4OP41E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1bUvJALH:5D4OP41E"
}

