All versions
1.7.0
Release
AE2:Utility 1.7.05 months ago 409
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
- Removed the built-in recipe tree feature.
- Added single and batch pattern encode/upload support to the EMI interface.
- Added ECO crafting subsystem upload compatibility for crafting, smithing table, and stonecutting patterns.
- Improved pattern upload behavior:
- EAEP toggle off: all automatic behavior (unique-match upload / provider reuse) stops, returning to fully manual selection.
- EAEP toggle on + AE2U reuse on: unique matches upload automatically; multiple matches reuse the previous same-name provider choice.
- EAEP toggle on + AE2U reuse off: only unique matches upload automatically; multiple matches require manual selection every time.
- When batch reuse is enabled and the batch remembers a same-name provider, but that provider is no longer in the current list (for example, it is full), the provider selection screen opens again and upload resumes only after a new choice, avoiding uploads to mismatched providers.
- Changed encode/upload input priority to: bookmarks > existing network patterns (craftable) > undamaged > highest stock > specific variant > first entry.
- Fixed a bug where JEI crafting recipes could be encoded as processing patterns.
- Fixed a bug where batch upload forced processing patterns into the matrix and showed “assembly matrix full, upload aborted”.
- Improved performance for multi-tag and multi-alternative recipe screens.
- 移除配方树功能。
- EMI 界面新增单个/批量样板编码/上传功能。
- 上传样板兼容自动上传合成、锻造台、切石机样板至 ECO 合成子系统。
- 优化上传样板逻辑:
- EAEP 开关关:任何自动行为(唯一匹配 / 复用)全部停止,回到全手动。
- EAEP 开关开 + AE2U 复用开:唯一时自动,多个时复用上次同名选择。
- EAEP 开关开 + AE2U 复用关:只有唯一匹配才自动,多个时每次手动选。
- 当开启批次复用、本批次已记住同名选择、但该同名供应器不在当前列表(如原供应器已满)时,再次弹出供应器选择界面进行选择后才再次上传,避免上传至不匹配的供应器。
- 更改编码/上传样板优先级:书签 > 网络已有样板(可合成) > 未损坏 > 库存最多 > 特异性变体 > 首项。
- 修复 JEI 编码合成配方时可能被编码成处理样板的 bug。
- 修复批量上传时处理样板被硬塞矩阵,提示“装配矩阵已满、已中止上传”的 bug。
- 优化多标签/多候选配方界面卡顿。
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:kJXRtOkZ:E0dgy1Ch"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kJXRtOkZ:E0dgy1Ch"
}

