Links
Tags
Creators
Details
2.1.4-beta2
Compatibility
Required content
Changes
AE2 Lightning Tech 2.1.4-beta2
Minecraft 1.21.1 · NeoForge · Beta
对比版本:2.1.4-beta
中文
- 修复与 AppliedFlux 等附属共用供应器界面时,重复注册
upgrades面板可能导致打开界面失败并断开连接的问题。修复覆盖闪电科技超载供应器,以及复用共享接口的封包供应器。 - 合并升级面板中的实际槽位和兼容升级提示,重复槽位只显示一次;兼容同一菜单的重复工具箱面板。其他界面、其他控件 ID 继续使用 AE2 原有的重复检查。
- 修正中英文指南中天枢、矩阵、苍穹织雷和电磁轨道炮的重复物品索引,保留正文内容与页面链接。
- 新增针对 AE2 19.2.18、AppliedFlux 2.1.7 的兼容验证配置,并补充升级栏合并、可选模组缺失和五种供应器界面的回归场景。
依赖:Thunderbolt Core 2.0.3。使用封包供应器时,建议同步更新到 1.2.4-beta2。
验证范围:已通过有/无 AppliedFlux 两组自动测试和构建;实际整合包中的游戏内界面复现与回归尚未完成。本次为 Beta 修复版本。
English
- Fixed provider screens failing to open and disconnecting the client when AppliedFlux or another addon registers the shared
upgradespanel again. The compatibility handling covers AE2LT overloaded providers and packaged providers using the shared host API. - Merge actual upgrade slots and compatible-upgrade tooltips without displaying the same slot twice. Repeated toolbox panels for the same menu are also handled. AE2's duplicate-ID checks remain in place for other screens and widgets.
- Removed conflicting item indexes from the English and Chinese Tianshu, matrix, Celestweave and railgun guide pages while keeping their contents and links.
- Added compatibility profiles for AE2 19.2.18 and AppliedFlux 2.1.7, with regression coverage for panel merging, the optional mod's absence, and five provider screen variants.
Requires Thunderbolt Core 2.0.3. Update Packaged Pattern Provider to 1.2.4-beta2 when using that addon.
Validation: builds and automated tests passed with and without AppliedFlux. In-game reproduction and screen regression in the reported modpack have not yet been completed. This is a beta fix release.
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:ArHeh5Fz:oN9VNjwH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ArHeh5Fz:oN9VNjwH"
}

