1.1.5-patch2
Compatibility
Changes
Forge 1.20.1 — 1.1.5-patch2
适用于 Minecraft 1.20.1 / Forge。
这是一次小型补丁更新,重点修复退出 RTS 后的隐藏区块恢复,并改进服务端稳定性、挖掘性能与本地化。
- 修复退出 RTS 后方块仍然隐藏的问题。
- 关闭 RTS 模式时会刷新范围隐藏功能影响过的区块。
- 减少必须手动重载区块后方块才重新显示的情况。
- 改进专用服务器稳定性。
- RTSBuilding 不再在服务器启动或延迟索引期间重建创造模式物品栏。
- 避免在服务端意外触发第三方模组的客户端事件与网络逻辑。
- 优化大型连锁挖掘与区域挖掘。
- 过滤重叠扫描范围内重复发现的掉落实体。
- 相同掉落会合并后再写入连接的储存。
- 未成功吸收的物品会准确写回原掉落实体。
- 补齐工作流与 GUI 绑定本地化。
- 工作流名称、暂停/等待状态、恢复放置面板、保护提示和 GUI 绑定错误现在会跟随玩家语言。
- 绑定的线缆与机器名称改为在客户端解析。
- 覆盖英文、简体中文、繁体中文(台湾)和繁体中文(香港)。
Forge 1.20.1 — 1.1.5-patch2
For Minecraft 1.20.1 / Forge.
This small patch focuses on restoring hidden chunks after leaving RTS mode, dedicated-server stability, mining performance, and localization.
- Fixed hidden chunks after leaving RTS mode.
- Blocks hidden by the RTS range-culling feature are refreshed when RTS mode closes.
- This reduces cases where blocks remain invisible until chunks are manually reloaded.
- Improved dedicated-server stability.
- RTSBuilding no longer rebuilds creative-tab contents during server startup or lazy indexing.
- This avoids triggering client-oriented events and networking behavior from third-party mods on the server.
- Optimized large chain-mining and area-mining jobs.
- Duplicate item entities from overlapping scan areas are filtered out.
- Identical drops are grouped before insertion into linked storage.
- Unabsorbed items are accurately returned to their original entities.
- Completed workflow and GUI-binding localization.
- Workflow names, paused/suspended states, resume-placement panels, protection messages, and GUI-binding errors now follow the player’s language.
- Bound cables and machines now resolve their names on the client.
- English, Simplified Chinese, Traditional Chinese (Taiwan), and Traditional Chinese (Hong Kong) are covered.
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:5PkY7RJI:hWmXXI2n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5PkY7RJI:hWmXXI2n"
}

