1.0.5
Compatibility
Changes
Forge 1.20.1 1.0.5
For Minecraft 1.20.1 / Forge.
This update syncs the Forge 1.20.1 branch with the latest 1.21.1 mainline fixes where applicable, including smoother RTS camera behavior, large-build stability, progression UI fixes, JEI overlay fixes, and safer container overlay behavior.
-
Changed the release artifact naming format.
- New file name:
rtsbuilding-forge-1.20.1-1.0.5.jar - Version metadata is now unified as
1.0.5.
- New file name:
-
Added and enabled Smooth RTS Camera by default.
- Ported the render-frame RTS camera prediction from the 1.21.1 mainline.
- Keeps the same server-authoritative tick/network split.
- The setting remains user-toggleable.
-
Improved large quick-build / shape placement performance.
- Added batched non-fluid shape placement.
- Server processes large placement jobs gradually instead of firing one packet/action per block.
- Reduces lag spikes during large RTS builds.
-
Fixed RTS render-buffer stability.
- Boundary, ghost preview, hovered target, and chunk guide rendering now use private buffers.
- Avoids conflicts with Minecraft’s shared render buffer lifecycle.
-
Fixed progression / skill tree material display mismatch.
- The UI now follows the server-synced cost table.
- Fixes cases where the detail panel showed enough materials but unlock still failed.
-
Improved progression node details UI.
- Added a higher-layer details modal for materials and prerequisites.
- Shows all required materials and unfinished prerequisites.
- Allows unlocking from the modal.
-
Fixed JEI overlay blank / invisible clickable area behavior.
- JEI now uses the actual RTS overlay layout instead of old hard-coded bounds.
-
Improved container RTS overlay behavior.
- Bottom import preview row reduced from five
+slots to two. - Added
Shift Intoggle. - Shift import is disabled by default so normal container Shift-transfer works unless the player opts in.
- Bottom import preview row reduced from five
-
Improved linked-storage tool mining.
- Remote tools are matched by full stack prototype instead of item id only.
- Mutated tool stacks are refunded after mining or aborting.
- Helps protect modded electric/NBT tools.
-
Fixed Mod Menu / config save crash.
- Progression and survival settings are saved through a single batched config write.
- Save failures are handled with a message instead of a crash.
-
Synced more RTS UI and control fixes.
- Configurable pan-drag X/Y inversion settings.
- High UI-scale layout fixes.
- Camera-centered 3x3 chunk guide display with player-height Y.
- Overlay and storage workflow cleanup.
Validation:
- Forge 1.20.1
jartask passed. - Output verified:
rtsbuilding-forge-1.20.1-1.0.5.jar.
Forge 1.20.1 1.0.5
适用于 Minecraft 1.20.1 / Forge。
本次更新将 Forge 1.20.1 分支进一步同步到 1.21.1 主线,重点包含平滑 RTS 镜头、大规模建造稳定性、技能树 UI 修复、JEI overlay 修复,以及更安全的容器 overlay 操作。
-
调整发布文件命名格式。
- 新文件名:
rtsbuilding-forge-1.20.1-1.0.5.jar - 模组版本号统一为
1.0.5。
- 新文件名:
-
新增并默认开启 Smooth RTS Camera。
- 从 1.21.1 主线同步渲染帧级别的 RTS 镜头预测。
- 保留服务端权威的 tick / 网络逻辑。
- 玩家仍可在 RTS 设置中关闭。
-
优化大规模快速建造 / 形状建造性能。
- 普通非流体形状建造改为批量放置。
- 服务端逐 tick 处理大型建造任务。
- 降低大面积 RTS 建造时的卡顿。
-
修复 RTS 渲染 buffer 稳定性。
- 边界、幽灵预览、悬停目标、区块显示改用私有 buffer。
- 避免和 Minecraft 主渲染 buffer 生命周期冲突。
-
修复技能树材料显示和实际解锁不一致。
- UI 现在使用服务端同步的消耗表。
- 修复详情里显示材料足够但无法解锁的问题。
-
改进技能节点详情界面。
- 新增更高图层的材料/前置详情弹窗。
- 显示全部材料和未完成前置。
- 可以从弹窗直接解锁。
-
修复 JEI overlay 空白/隐形可点击区域。
- JEI 现在使用真实 RTS overlay 布局,不再使用旧硬编码范围。
-
改进容器 RTS overlay。
- 底部导入预览从五个
+缩减为两个。 - 新增
Shift 存入开关。 - 默认关闭 Shift 导入,让普通容器 Shift 转移正常工作。
- 底部导入预览从五个
-
改进绑定储存中的工具挖掘。
- 远程工具按完整 ItemStack 原型匹配,不再只看物品 id。
- 挖掘完成或中断后返还变化后的工具。
- 降低模组电动工具 / NBT 工具异常丢失风险。
-
修复 Mod Menu / config 保存崩溃。
- 生存平衡和技能消耗设置改为一次批量保存。
- 保存失败会显示提示,不再直接崩溃。
-
同步更多 RTS UI 和操作修复。
- 拖屏 X/Y 方向反转设置。
- 高 UI 缩放布局修复。
- 区块显示以摄像机 X/Z 为中心,Y 高度跟随玩家。
- overlay 和储存流程细节清理。
验证:
- Forge 1.20.1
jar任务通过。 - 已确认产物:
rtsbuilding-forge-1.20.1-1.0.5.jar。
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:P0Rp0Dei"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5PkY7RJI:P0Rp0Dei"
}

