1.2.2-beta3-forge.1.20.1
Compatibility
Required content
Changes
AE2LT Packaged Pattern Provider 1.2.2-beta3 (Forge 1.20.1)
对比版本 / Compared with: 1.20.1-1.2.2-beta2
中文
- 核心制作与安装接入 AE2 原生终端确认页和合成状态页,支持首核自动安装、批量备用核心及单枚原位升级;服务端校验前置核心、数量和供应器忙碌状态。
- 共振输入新增默认 32 格的可配置距离限制,校验维度和坐标并兼容旧输出布局;拆除前按实际回执优先将缓冲资源退回 ME。
- 完善实体批量投料与虚拟产物逐笔交付回执,保留部分插入余量,修复后续通道异常、重载恢复和旧 Alpha 存档迁移时的材料归属与回收边界。
- 完善 Botania 花药台组件与容量匹配、EC 实时配方检查、MekMM 原生配方重载选择,并共享多个可选机器联动的现有访问实现。
- 修复 Forge/Netty 协议切换后多人登录可能等待约 30 秒超时的问题;修复长标题越界和确认页初始空目标状态。
依赖 AE2 Lightning Tech 2.1.4 和 Thunderbolt Core 2.0.5,均为 Forge 1.20.1 版本。
English
- Integrated core crafting and installation with the native AE2 terminal confirmation and crafting status screens, including first-core installation, spare-core batches and single-core in-place upgrades with server-side validation.
- Added a configurable 32-block resonant input range with dimension and coordinate checks while preserving legacy output layouts. Return buffered resources to ME before removal according to actual receipts.
- Improved physical input batching and per-delivery virtual-output receipts, preserving partial insertion remainders and material ownership across later-lane failures, reloads and legacy Alpha save migration.
- Improved Botania petal recipe component/capacity matching, live Extended Crafting recipe checks and MekMM native recipe overload resolution; shared existing access logic across optional machine integrations.
- Fixed a Forge/Netty protocol-switch race that could stall multiplayer login until the approximately 30-second timeout, long title overflow and empty initial confirmation destinations.
Requires AE2 Lightning Tech 2.1.4 and Thunderbolt Core 2.0.5, both for Forge 1.20.1.
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:QrbJwOfn:gGEBWmRX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QrbJwOfn:gGEBWmRX"
}

