Links
Tags
Creators
Details
All versions
1.1.5
Release
create-schematic-compute 1.1.54 months ago 366
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Unavailable version
Changes
v1.1.5
- ✨ Add: LATCH edit panel — Configurable default set/reset state toggle with real-time current state display 🇨🇳 新增:锁存器编辑面板 — 可配置初始置位/复位切换,实时显示当前状态
- ✨ Add: PRIVATE_IN/PRIVATE_OUT on Program Computer — Private signal channels now available for cross-block communication 🇨🇳 新增:编程计算机支持私有信号 — PRIVATE_IN/PRIVATE_OUT 节点可用于跨方块通信
- ✨ Add: RuntimeState sync packet — flipflopStates synced server→client on change for real-time UI display in multiplayer 🇨🇳 新增:运行时状态同步包 — 翻转状态变化时服务端→客户端同步,多人游戏编辑区实时显示
- 🐛 Fix: Recompile state reset — GATE, T_FLIPFLOP, and LATCH current state now resets to configured default on recompile 🇨🇳 修复:重新编译状态重置 — 闸门、T触发器、锁存器重新编译后当前状态回归初始默认值
- 🐛 Fix: Edit panel live state display — GATE/T_FLIPFLOP/LATCH current state now updates in real-time during execution (shared object single-player + network sync multiplayer) 🇨🇳 修复:编辑区实时状态显示 — 闸门/T触发器/锁存器当前状态运行时实时更新(单机共享对象+多人网络同步)
- 🐛 Fix: World reload state persistence — Program Computer and Blueprint Computer now correctly restore flipflopStates and pulseTimers across world reloads 🇨🇳 修复:世界重载状态持久化 — 编程计算机和蓝图计算机世界重载后正确恢复时序节点运行状态
- 🐛 Fix: RuntimeState load consistency — All 6 block entities audited; Blueprint now loads full runtime state; SpeedProxy clears pidState on graph change 🇨🇳 修复:运行时状态加载一致性 — 全部6个方块实体审查;蓝图计算机现在加载完整运行时状态;SpeedProxy 图变化时清理 pidState
- 🔧 NBT compatibility: v1→v2 migration — Old LATCH saves (params.length=0) auto-upgraded to new format 🇨🇳 NBT 兼容层:v1→v2 迁移 — 旧版锁存器存档(params.length=0)自动升级为新格式
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:mhedkDz3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1bUvJALH:mhedkDz3"
}

