1.1.6
Compatibility
Changes
简体中文
RTS Building 1.1.6
适用于 Minecraft 1.21.1 / NeoForge 与 Minecraft 1.20.1 / Forge。
这是 1.1.6 的替换发布,保留原版本的界面、建造、旋转、崩溃修复和整合包兼容改进,并补上 Task Engine 的工作流上限修复。
玩家可见变化
- 修复工作流面板为空时,批量建造仍反复提示“建造任务已到上限”的问题。
- 新工作流会自动淘汰最旧的未钉住旧工作流。
- 只有所有相关旧工作流都已钉住时,新任务才会因容量上限被拒绝。
- 修复旧持久任务成为隐藏工作流并长期占用任务名额的问题。
- 没有合法可见投影的旧任务会被终止和清理。
- 旧任务恢复时不能反向挤掉玩家刚创建的新工作流。
- 保留此前 1.1.6 的玩家改进,包括水平旋转箭头的屏幕方向语义、Forge 1.20.1 进入世界和旋转箱子的崩溃修复,以及快速建造、蓝图、挖掘、储存和 AI 帮助更新。
技术与兼容性改进
- 将放置、破坏和挖掘的持久任务容量策略统一收口到 Task Engine,并按当前维度与相关任务族处理淘汰,避免无关维度或无关任务互相阻塞。
- 内部漏斗和恢复辅助任务仍可隐藏运行,但不占用玩家工作流槽位。
- NeoForge 1.21.1 完整构建通过 683 项常规测试与 3 项性能债检查;Forge 1.20.1 完整构建通过 713 项常规测试与 3 项性能债检查。
English
RTS Building 1.1.6
For Minecraft 1.21.1 / NeoForge and Minecraft 1.20.1 / Forge.
This replacement release keeps the UI, building, rotation, crash, and modpack-compatibility improvements from the original 1.1.6 while adding the missing Task Engine workflow-capacity fix.
Player-visible changes
- Fixed repeated “building task limit reached” messages while the workflow panel appeared empty.
- A new workflow now evicts the oldest unpinned older workflow automatically.
- Capacity rejects a new task only when every relevant older workflow is pinned.
- Fixed old durable tasks remaining as hidden workflows that permanently consumed task capacity.
- Old tasks without a valid visible projection are cancelled and cleaned up.
- Restoring an old task cannot evict a workflow the player just created.
- Retains the earlier 1.1.6 improvements, including screen-direction semantics for horizontal rotation arrows, Forge 1.20.1 startup and placed-chest rotation crash fixes, and the Quick Build, blueprint, mining, storage, and AI help updates.
Technical and compatibility changes
- Unified durable placement, destruction, and mining capacity policy in the Task Engine, with eviction scoped to the current dimension and relevant task family so unrelated work cannot block admission.
- Internal funnel and recovery helper tasks may remain hidden but do not consume player workflow slots.
- Full builds passed 683 ordinary tests plus 3 performance-debt checks on NeoForge 1.21.1, and 713 ordinary tests plus 3 performance-debt checks on Forge 1.20.1.
Optional dependencies
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:bOUc0KlZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5PkY7RJI:bOUc0KlZ"
}


