Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 years ago
Updated 5 days ago
All versions
1.15.3.0
Release
1.15.3.05 days ago 545
Compatibility
Minecraft: Java Edition
26.3
26.2
26.1.x
1.21.x
1.20.x
Platforms
Folia
Paper
Purpur
Spigot
Changes
更新内容 | Update Contents
- 移除配置项
use_experimental_recipe_ingredients,新增配置项ingredient_match_mode,用于选择配方材料的匹配方式:first(默认,使用第一个识别到的物品 id 匹配)或all(收集物品所有可能的物品 id 后逐个尝试匹配,性能开销更高) | Removed theuse_experimental_recipe_ingredientsoption and added theingredient_match_modeoption to choose how recipe ingredients are matched:first(default, matches using the first recognized item id) orall(collects all possible item ids of an item and tries them one by one, which costs more performance). not_convert_listener_classes支持以*结尾的条目按类名前缀匹配 |not_convert_listener_classesnow supports entries ending with*for class-name prefix matching.- 连续发起的插件重载请求现在会进入队列依次执行,不再被直接丢弃 | Consecutive plugin reload requests are now queued and executed in order instead of being dropped.
- 优化插件启动加载流程 | Optimized the plugin's startup loading flow.
- 优化26.3版本下禁用较多酿造配方时,重载过程占用较多网络带宽的问题 | Reduced excessive network bandwidth usage during reload on 26.3 when a large number of brewing recipes are disabled.
- 其他插件监听器转换成功的日志级别由
verbose调整为info| The log level for successfully converted third-party listeners has been changed fromverbosetoinfo. - 修复通过
/craftorithm restore恢复的配方无法出现在命令补全列表中的问题 | Fixed recipes restored via/craftorithm restorenot showing up in command tab completion. - 修复
ingredient_restriction_rules中的物品 id 无法解析时导致整份限制规则重载中断的问题 | Fixed an issue where an unparseable item id iningredient_restriction_rulesaborted reloading of the entire rule list. - 修复迁移整型配置项时输出无意义警告的问题 | Fixed meaningless warnings when migrating integer config options.
Optional dependencies
Any compatible version
Any compatible version
Unavailable version
Unavailable version
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:mttZgFDu:wjxlC2Q5"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mttZgFDu:wjxlC2Q5"
}

