Links
Tags
Creators
Details
Licensed GPL-3.0-only
Published 8 months ago
Updated 3 days ago
All versions
20.4.0
Release
Neo ECO AE Extension v20.4.02 months ago 789
Uploaded by
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
中文
新增
- 新增合成网络交换机、计算网络交换机及其高能型号,用于将 ECO 合成/计算子系统组织为可切换的逻辑集群。
- 网络交换机接入 AE2 电网,并加入频率设定、GuideMe 说明及相关配方和本地化内容,降低不同网络误串的风险。
- 新增快速任务规划路径,并接入实际 AE 合成任务;支持循环配方、NBT/动态/替换样板,以及可复用催化剂。
- 新增样板迁移、矩阵样板浏览、规划路径日志、最大合成效率提示和快速任务规划提示。
- FastPath 新增对 AAE CPU 批量样板推送、外部 CPU 路由、锻造台配方、切石机配方的支持。
- 无限存储迁移至
SavedData引擎,新增幂等迁移、WAL 持久化、故障隔离、恢复诊断和迁移状态展示。 - 新增 4 GiB ECO Omni 存储单元、Omni 联动存储盘
改进
- 优化快速任务规划的循环处理、网络增长量计算和样板搜索流程,改善复杂自动合成请求的响应速度。
- 优化 FastPath 的批量调度、控制器缓存共享和元数据惰性构建,减少重复解析样板的开销。
- 将快速规划开关调整为网络级总开关,并加入交换主机间的公平派发,减少主机抢占任务的情况。
- 优化无限存储的数据持久化、迁移记录、恢复边界和统计显示;容量统计改用二进制字节单位。
- 增强 FE 存储元件,调整量子 Omni 单元配方、量子组件回收和旧配方。
修复
- 修复崩溃或重进存档后合成 CPU 恢复异常导致的产物丢失、卡合成问题。
- 修复超大 CPU 存储量在界面显示时可能引发的崩溃。
- 修复材料不足时错误报告“没有可用 CPU”、长链配方栈溢出、自增长循环异常及双样板计算卡死问题。
- 修复超大快速计划、外部 CPU 输出、虚拟合成资格和任务归属处理异常。
- 修复可复用输入在大量样板变体下的状态容量丢失,以及 FastPath 在 ECO 主机、AAE CPU 上的兼容问题。
- 修复无限存储迁移后的校验、缺失物品转移、恢复材料验证和特殊库存数值误进入合成规划的问题。
English
Added
- Added Crafting Network Switches, Computation Network Switches, and their high-energy variants for organizing ECO Crafting and Computation subsystems into switchable logical clusters.
- Connected Network Switches to the AE2 power grid and added frequency settings, GuideMe documentation, related recipes, and localization to reduce accidental cross-network connections.
- Added a Fast Task Planning path integrated with real AE crafting tasks, supporting cyclic recipes, NBT/dynamic/replacement patterns, and reusable catalysts.
- Added Pattern Migration, Matrix Pattern Browser, planning-path logs, maximum crafting-efficiency hints, and Fast Task Planning hints.
- Extended FastPath with AAE CPU batch pattern pushing, external CPU routing, Smithing Table recipes, and Stonecutter recipes.
- Migrated Infinite Storage to the
SavedDataengine and added idempotent migration, WAL persistence, fault isolation, recovery diagnostics, and migration-status feedback. - Added 4 GiB ECO Omni Cells and Omni integration storage cells.
Improved
- Improved cyclic handling, net-growth calculation, and pattern-search flow in Fast Task Planning for more responsive complex autocrafting requests.
- Improved FastPath batch scheduling, shared controller caches, and lazy metadata construction to reduce repeated pattern parsing.
- Made Fast Planning a network-wide master switch and added fair dispatching between Exchange Hosts to reduce task monopolization.
- Improved Infinite Storage persistence, migration records, recovery boundaries, and statistics display; capacity statistics now use binary byte units.
- Enhanced FE Storage Cells and adjusted Quantum Omni Cell recipes, Quantum Component recovery, and legacy recipes.
Fixed
- Fixed Crafting CPU recovery after crashes or world reloads causing lost outputs or stalled crafting jobs.
- Fixed a crash that could occur when the UI displayed oversized Crafting CPU storage values.
- Fixed insufficient materials incorrectly reporting no available CPU, long crafting chains overflowing the stack, self-growing cycle issues, and duplicate-pattern planning deadlocks.
- Fixed oversized Fast Plans, external CPU outputs, virtual crafting eligibility, and task-ownership handling.
- Fixed reusable-input state capacity loss with many pattern variants, along with FastPath compatibility issues on ECO Hosts and AAE CPUs.
- Fixed Infinite Storage post-migration validation, missing-item transfers, restore-material validation, and sentinel inventory values leaking into crafting planning.
Full Changelog: https://github.com/DancingSnow0517/NeoECOAEExtension/compare/20.3.0...20.4.0
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| neoecoae-20.4.0-sources.jar | Unknown | 753.42 KiB |
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:udZtKfzP:ueacEcfO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:udZtKfzP:ueacEcfO"
}

