1.1.8-beta
Compatibility
Changes
简体中文
RTS Building 1.1.8-beta
适用于 Minecraft 1.21.1 / NeoForge 与 Minecraft 1.20.1 / Forge。本次 Beta 重点统一双版本的后台建造、配置、工作流、存储分页与蓝图预览行为。
玩家可见变化
- 后台建造任务现在使用提交时确定的合格材料来源;玩家之后打开背包、箱子或合成终端,不会再改变已提交任务是否能从主背包取料。
- 工作流不再只显示笼统的“已挂起”:列表会区分缺少材料、缺少工具、等待区块、手动暂停、配置关闭、权限不足、队列已满和执行错误,并可打开详情查看完整原因与下一步。
- 修正工作流容量与过期任务清理,尤其补齐 Forge 1.20.1 的替换、保护和终态行为,避免失效任务占满槽位。
- 设置页明确拆分本地个人设置与世界/服务器设置。服务端规则由服务器校验、保存并同步;无权限玩家只读,保存冲突或失败时保留草稿。
- 范围挖掘与范围破坏统一使用“体积上限 + X/Y/Z 轴上限”。新配置默认体积
46656、三个轴各64,旧配置会自动迁移;游戏内说明现在直接显示有效上限262144。 - 大型蓝图库改为异步读取,材料分析、预览几何和幽灵网格按内容变化缓存;固定或未变化的蓝图不再每帧重复重建整栋建筑。
- 大型存储页面使用服务端分页窗口与请求代际,减少固定页长、旧响应覆盖新页面和尾页显示异常。
- 大范围形状与破坏请求统一容量检查和分片传输;超限操作会在执行前拒绝,不再开始不完整的部分操作。
技术与兼容性改进
- 新增低噪声结构化诊断,把客户端请求、服务端操作、工作流和持久任务串到同一条追踪链,只在状态变化与终态记录关键原因。
- NeoForge 1.21.1 与 Forge 1.20.1 对齐配置协议、工作流原因、后台取料、分页、蓝图缓存、放置凭据、撤销历史和瞬时回收语义;loader 差异保留在适配层。
- 内置中英文教程的技术信息附录已同步本次配置、取料、工作流、诊断和存储绑定规则。
- 发布候选通过 NeoForge
1054/1054与 Forge955/955项普通测试,两端性能债门禁各3/3;隔离服务端 GameTest 分别通过 NeoForge90/90、Forge76/76,未启动游戏客户端。
English
RTS Building 1.1.8-beta
For Minecraft 1.21.1 / NeoForge and Minecraft 1.20.1 / Forge. This beta aligns background construction, configuration, workflows, storage paging, and blueprint previews across both supported versions.
Player-visible changes
- Submitted background construction tasks now keep using their eligible material sources. Opening an inventory, chest, or crafting terminal later no longer changes whether an existing task can draw from the player inventory.
- Workflows no longer collapse every wait into a generic “Suspended” state. Rows distinguish missing materials, missing tools, chunk loading, manual pause, disabled configuration, denied access, full queues, and execution errors, with a detail panel for the full reason and next step.
- Fixed workflow-capacity and stale-task cleanup, including Forge 1.20.1 parity for replacement, protection, and terminal states, so obsolete tasks do not keep valid work from starting.
- The settings screen now separates local personal preferences from world/server rules. Server settings are validated, persisted, and synchronized by the server; read-only users stay read-only, and failed or conflicting saves preserve the draft.
- Range mining and range destruction now share volume plus X/Y/Z axis limits. Fresh configurations default to volume
46656and64per axis, existing settings migrate automatically, and the in-game descriptions show the effective262144ceiling. - Large blueprint libraries load asynchronously. Material analysis, preview geometry, and ghost meshes are cached by content, so unchanged or pinned blueprints no longer rebuild an entire structure every frame.
- Large storage views now use server-owned page windows and request generations, avoiding fixed client page assumptions, stale-response overwrites, and incorrect last pages.
- Large shape and destruction requests share capacity admission and fragmented transfer. Oversized operations are rejected before execution instead of starting an incomplete partial action.
Technical and compatibility changes
- Added low-noise structured diagnostics that correlate client requests, server operations, workflows, and durable tasks, recording meaningful transitions and terminal reasons instead of per-tick spam.
- NeoForge 1.21.1 and Forge 1.20.1 now align configuration protocol, workflow reasons, background sourcing, paging, blueprint caches, placement credentials, undo history, and instant recovery behavior while keeping loader differences in adapters.
- The bundled English and Simplified Chinese technical appendices now match the released configuration, sourcing, workflow, diagnostics, and storage-binding behavior.
- The release candidates pass
1054/1054ordinary tests on NeoForge and955/955on Forge, plus3/3performance-debt gates on each line. Isolated server GameTests pass90/90on NeoForge and76/76on Forge; no game client was launched.
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:dVipmL0p"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5PkY7RJI:dVipmL0p"
}

