1.1.5-patch4
Compatibility
Changes
简体中文
RTS Building 1.1.5-patch4
适用于 Minecraft 1.21.1 / NeoForge 与 Minecraft 1.20.1 / Forge。
本次补丁集中修复 RTS 放置方块回收、生存解锁、交互提示、掉落物处理和精妙背包兼容问题。
玩家可见变化
- 修复“回收 RTS 放置方块”开启时,挖掘等级或工具不满足原方块要求会直接吞掉方块的问题。
- 由 RTS 放置并仍被追踪的方块,现在回收时会绕过挖掘等级、工具和精准采集要求;能通过 RTS 放置,就能通过 RTS 回收。
- 领地保护、事件取消和其他服务端保护规则仍会生效。
- 修复生存平衡开启时若干功能被错误锁定的问题。
- 范围挖掘不再错误依赖连锁挖掘插件。
- 快速建造的不同形状会按各自插件权限解锁,服务端拒绝放置时也会给出明确提示。
- RTS 镜头未解锁时,提示现在会明确说明需要安装“RTS 相机”插件,或者在模组配置中关闭“生存平衡”。
- 修复固定 RTS UI 缩放下,屏幕下半部的普通交互目标框可能消失的问题。
- 修复快速建造中“实心 / 空心”按钮看似切换成功、实际仍按旧模式生成的问题。
- 修复大量同类掉落物可能被合并成非法超大 ItemStack 并导致崩溃的问题(#123)。
- 改进 Sophisticated Backpacks / 精妙背包兼容。
- 同一个 UUID 背包无论放在世界中还是背在玩家身上,都可以继续使用同一条 RTS 储存绑定。
- RTS 模式下右键物品栏中的精妙背包只会尝试放置;放置失败时不再回退打开背包界面,避免卡住。
- 新生成的客户端配置会默认关闭放置方块的半透明虚影预览。已有玩家的手动设置不会被覆盖;线框预览和放置/破坏动画不受影响。
技术与兼容性改进
- RTS 放置方块回收现在先经过服务端保护事件,再使用追踪记录中的原始方块物品进行无掉落破坏和精确归还,避免工具判定造成物品丢失或重复掉落。
- NeoForge 1.21.1 的挖掘掉落缓存现在按物品合法堆叠上限合并和拆分,并按真实入库进度判断超时回退,减少大型挖掘任务中的卡顿与物品异常。
- 生存平衡配置变化后会重新同步插件状态,避免客户端继续显示旧的解锁结果。
- 精妙背包绑定会优先解析饰品、Curios 和 Accessories 槽位中的真实背包物品,再使用 UUID 虚拟处理器回退;Forge 1.20.1 同步支持其旧版能力接口。
- 两条维护线均补充了对应的契约与回归测试。本次构建中,NeoForge 1.21.1 全量测试通过;Forge 1.20.1 常规测试通过,仍保留两项已知性能债作为后续优化目标。
English
RTS Building 1.1.5-patch4
For Minecraft 1.21.1 / NeoForge and Minecraft 1.20.1 / Forge.
This patch focuses on safe recovery of RTS-placed blocks, survival unlocks, clearer interaction feedback, safer mining-drop handling, and Sophisticated Backpacks compatibility.
Player-visible changes
- Fixed tracked RTS-placed blocks being lost when “Recover RTS-placed blocks” was enabled but the player lacked the normal mining level or tool.
- Blocks that were placed through RTS and are still tracked now bypass mining-level, tool, and Silk Touch requirements during RTS recovery: if RTS can place it, RTS can recover it.
- Claims, cancelled break events, and other server protection rules are still respected.
- Fixed several features being incorrectly locked while Survival Balance was enabled.
- Area mining no longer incorrectly depends on the chain-mining plugin.
- Quick Build shapes now follow their own plugin unlocks, and rejected placement attempts provide clear feedback.
- When the RTS camera is locked, the message now explicitly tells players to install the “RTS Camera” plugin or turn off Survival Balance in the mod config.
- Fixed the normal interaction target outline disappearing in the lower half of the screen when using a fixed RTS UI scale.
- Fixed Quick Build solid/hollow buttons appearing to change while generation still used the previous mode.
- Fixed large groups of identical drops being merged into an illegal oversized ItemStack and potentially crashing the game (#123).
- Improved Sophisticated Backpacks compatibility.
- The same UUID-backed backpack keeps one RTS storage link whether it is placed in the world or worn by the player.
- Right-clicking a Sophisticated Backpack from the inventory in RTS mode now only attempts placement. If placement fails, it no longer falls back to opening the backpack UI and getting stuck.
- Newly generated client configs now disable translucent placement block ghosts by default. Existing player choices are preserved; wireframe previews and placement/destruction animations are unchanged.
Technical and compatibility changes
- Tracked-block recovery now passes through server protection events, then performs a no-drop break and returns the exact recorded block item, preventing tool checks from losing items or creating duplicate drops.
- On NeoForge 1.21.1, the mining-drop buffer now merges and splits items using each item’s legal stack size and bases fallback timing on real storage progress, reducing stalls and invalid stacks during large mining jobs.
- Plugin state is resynchronized after Survival Balance configuration changes so clients do not keep stale unlock results.
- Sophisticated Backpack links now resolve real stacks from accessory, Curios, and Accessories slots before falling back to the UUID-backed virtual handler. Forge 1.20.1 also supports the older capability API.
- Regression and contract coverage was added on both maintenance lines. The NeoForge 1.21.1 suite passed in full; the Forge 1.20.1 regular suite passed, with two previously tracked performance-debt checks remaining for later optimization.
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:jNSFd4UW"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5PkY7RJI:jNSFd4UW"
}

