Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 6 months ago
Updated 6 months ago
All versions
1.8.0-release
Release
Wireless Redstone: RedstoneLink-makomi 1.8.0-release6 months ago 15
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Client and server
Changes
1.8.0-release
Major update from the 1.6.3-beta line.
Highlights
- Added
Link Repeater - Added
Smart Glassesto carry far/near overlays and visualize display - Added
Smart Node Containerfor portable node storage and placement Sync Linkernow supports in-game custom signal strength0-15
Improvements
- Visualized links now support incremental refresh instead of staying as a stale one-time snapshot
- Better HUD / tooltip / current-link display for nodes, aliases, and repeaters
- Repeater support has been extended across visualization, graph export, web editor, delay validation, lifecycle handling, and cross-chunk behavior
- Smart Node Container now replaces the old aggregate-shell workflow with a real chest-like handheld container
Fixes
- Fixed multiple repeater edge cases
- Fixed sync cross-tick aggregation/recompute issues
- Fixed recipe parsing issues that prevented some recipes from appearing in JEI
- Fixed client shutdown crash caused by duplicate scroll callback release
Technical cleanup
- Removed the old aggregate-related mixin path
- Synced recipes, guides, item guide pages, and mechanism docs to the new systems
1.8.0-release
相较 1.6.3-beta,这是一次较大的功能整合更新。
主要内容
- 新增
转发器 - 新增
智能眼镜,承接远近外显与连线显示 - 新增
智能节点容器,用于便携收纳与放置节点 同步遥控器支持游戏内自定义0-15信号强度
改进
- 连线可视化从一次性快照改为增量刷新,连接变化后会自动同步显示
- 优化了节点、别名、转发器相关的 HUD、tooltip 和当前连接显示
- 转发器已接入连线显示、图导出、网页图编辑、延迟验证、生命周期处理和跨区块行为
- 智能节点容器替代旧聚合壳思路,改为真正的大箱子式手持容器
修复
- 修复多个转发器边界问题
- 修复
sync跨 tick 聚合与重算问题 - 修复部分配方解析失败导致 JEI 不显示的问题
- 修复客户端退出时滚轮回调重复释放导致的崩溃
整理
- 移除了旧的聚合相关 mixin 实现路径
- 已同步相关配方、使用说明、图鉴和机制文档
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:pCtW8y8B:HlRdDYNp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pCtW8y8B:HlRdDYNp"
}

