Links
Tags
Creators
Details
2.1.4-forge.1.20.1
Compatibility
Required content
Changes
AE2 Lightning Tech 2.1.4 (Forge 1.20.1)
对比版本 / Compared with: 1.20.1-2.1.3
中文
- 新增矩阵 T3 样板仓:单仓 288 槽、50 仓共 14,400 槽,支持使用致密拓扑晶格从 T2 原位升级并保留样板;各仓独立发布样板与接收合成请求,端口按仓浏览和同步。
- 特斯拉线圈与普通水晶催化器支持 AE2 红石卡,可选择忽略红石、有信号工作、无信号工作;暂停时保留加工进度。
- 安装 Apotheosis 并注册漂浮药水时,可用浮游物质将粗制药水酿造为漂浮药水,兼容普通、喷溅和滞留药水。
- 完善 Applied Mekanistics 气体、灌注、颜料和浆液输入,以及过载接口子网存储能力;修复 Mekanism 流体和化学品自动回收误取输入储罐的问题。
- 修复供应器共享升级面板、天枢上传界面和动态目标名称匹配,改善样板管理交互。
- 修复矩阵与天枢核心特效在控制器移出视野、跨渲染区段或关闭自定义着色器时消失,以及跨区块拆除后外观残留的问题。
- 兼容异步 AE 节点序列化,完善过载合金通用材料标签及相关配方。
依赖 Thunderbolt Core 2.0.5(Forge 1.20.1)。封包供应器建议配套 1.2.2-beta3。
English
- Added T3 matrix pattern warehouses with 288 slots each and up to 14,400 slots across 50 warehouses. Upgrade T2 warehouses in place with dense topological lattices while preserving patterns. Warehouses advertise and accept their own crafting requests; the port browses and synchronizes one warehouse at a time.
- Added AE2 redstone card control to Tesla coils and regular crystal catalyzers, with ignore/high/low signal modes that preserve paused processing progress.
- Added floating-matter brewing for Apotheosis levitation potions when that potion is registered, including regular, splash and lingering variants.
- Improved Applied Mekanistics chemical input support and overloaded-interface subnet storage access. Prevent automatic Mekanism fluid and chemical returns from draining input tanks.
- Fixed shared provider upgrade panels, Tianshu upload screens and dynamically styled upload target matching; improved pattern management interactions.
- Fixed matrix and Tianshu core effects disappearing across render sections, outside the controller view, or with custom shaders disabled. Fixed stale formed appearances after cross-chunk dismantling.
- Added compatibility with asynchronous AE node serialization and improved common overload-alloy tags and recipes.
Requires Thunderbolt Core 2.0.5 for Forge 1.20.1. Use Packaged Pattern Provider 1.2.2-beta3 when installed.
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:RoG4v66B"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ArHeh5Fz:RoG4v66B"
}

