Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 5 months ago
Updated 11 hours ago
All versions
1.2.4-beta
Beta
AE2LT Packaged Pattern Provider 1.2.4-beta (neoforge 1.21.1)15 hours ago 52
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Any compatible version
Changes
AE2LT Packaged Pattern Provider 1.2.4-beta
Minecraft 1.21.1 / NeoForge · Beta
中文
相对正式版 1.2.4 的更新:
- 修复 Re-Avaritia、Extended Crafting 虚拟工作台及终焉锻造台在配方重载后继续使用旧绑定的问题;删除、替换或新增配方后重新校验,正、负绑定缓存同步刷新。
- 拒绝已经删除或被同 ID 新配方替换的旧配方句柄,避免继续按过期配方加工。
- 修复工作台多份输入计数相加溢出的问题;数量溢出时拒绝投料,保留输入归属。
- 完善原生工作台、锻台和真实 KubeJS 资源重载的回归覆盖,并补充脚本兼容文档。
- 旧版 Re-Avaritia 的 KubeJS 锻台 schema 问题仍属于上游限制;该情形可使用原始数据包 JSON,本次不宣称修复其 event.custom() 创建失败。
- 配套依赖 AE2 Lightning Tech 2.1.4-beta 和 Thunderbolt Core 2.0.3。
English
Changes since the stable 1.2.4 release:
- Fixed stale virtual crafting bindings after recipe reloads for Re-Avaritia and Extended Crafting tables, including extreme smithing. Added, replaced and removed recipes now refresh both successful and failed binding caches.
- Reject deleted recipes and stale recipe handles replaced under the same ID instead of processing outdated recipes.
- Reject overflowing combined input counts without transferring input ownership.
- Expanded native table, smithing and real KubeJS resource reload regression coverage and documented script compatibility.
- The legacy Re-Avaritia KubeJS smithing schema limitation remains an upstream issue. Raw datapack JSON is a workaround; this release does not fix recipe creation through the affected event.custom() path.
- Requires AE2 Lightning Tech 2.1.4-beta and Thunderbolt Core 2.0.3.
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:8Q5CInYx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QrbJwOfn:8Q5CInYx"
}

