1.0.2-beta
Compatibility
Changes
English Changelog
RTS Building: Build From Above 1.0.2-beta
For Minecraft 1.21.1 / NeoForge mainline.
This update focuses on storage-scan performance, inventory-open lag in large modpacks, clearer scan feedback, and smoother ultimine behavior.
- Added a manual refresh button: the main RTS storage bar and the compact inventory overlay now include an
Rbutton to force a linked-storage rescan. - Reduced inventory/creative-inventory open lag: the overlay no longer triggers a full linked-storage scan every time a container or creative inventory screen opens.
- Improved large-modpack item classification performance: creative-tab membership is warmed and cached instead of being rebuilt repeatedly.
- Added storage scan feedback: refresh, search, sort, and paging requests now show a lightweight scan indicator while waiting for the server response.
- Improved Ultimine pacing: chained blocks are now processed in small batches across server ticks instead of finishing the entire chain, drop absorption, and storage refresh in one tick.
- Fixed and expanded overlay localization: English, Simplified Chinese, Traditional Chinese Taiwan, and Traditional Chinese Hong Kong resources now cover return/import labels, help text, and scan status.
- Manual actions still request fresh data: search, sort, paging, and the new refresh button continue to update linked storage explicitly.
RTS Building: Build From Above 1.0.2-beta
适用于 Minecraft 1.21.1 / NeoForge 主项目。
本次更新主要改善大型整合包中的存储扫描性能、库存界面打开卡顿、扫描反馈和连锁挖掘体验。
- 新增手动刷新按钮:RTS 底部存储栏和库存内小型 RTS 覆盖层现在都有
R刷新按钮,可手动强制重新扫描已绑定存储。 - 降低打开背包/创造物品栏时的卡顿:覆盖层不再每次打开容器或创造物品栏都自动触发完整存储扫描。
- 优化大型整合包物品分类性能:创造模式标签分类会提前预热并缓存,减少大量物品环境下的重复重建。
- 新增存储扫描反馈:触发刷新、搜索、排序、翻页等存储请求时,会显示轻量扫描提示,避免看起来像 UI 没反应。
- 优化 Ultimine 连锁挖掘:后续方块现在分批跨 tick 处理,不再把整条连锁、掉落吸收和存储刷新挤在同一个服务器 tick 中完成。
- 修复和补全覆盖层本地化:补充英文、简体中文、繁体中文台湾、繁体中文香港翻译,包括返回/导入标签、帮助文本和扫描状态。
- 保留显式刷新逻辑:自动扫描减少了,但搜索、排序、翻页和手动刷新仍会请求最新存储数据。
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:2ziWo3sl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5PkY7RJI:2ziWo3sl"
}

