All versions
V1.4.2
Release
V1.4.2 for 1.20~1.20.4yesterday 4
Compatibility
Minecraft: Java Edition
1.20–1.20.4
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Auto-Refill Item Identity Fix
English
Fixed
- Auto-refill no longer hands over a different item when several custom items are built on the same vanilla base item (e.g. two artifacts that are both
minecraft:stick). - Worn tools still refill:
DamageandRepairCostare excluded from the identity comparison.
Added
nbtIdentityKeys(defaultCustomModelData): items carrying an identity key are matched by that key alone, ignoring instance UUID / remaining uses / lore. This fixes auto-refill on custom-item servers such as The Sky Blessing.nbtIgnoreKeys,nbtMatchMode,allowSameItemFallbackfor finer control.- Identity diagnostics under
debugRefillLogging.
Changed
- If no item with the same identity exists in the inventory, auto-refill now does nothing instead of picking another item with the same ID.
config/kabutack-auto-refill.propertiesis generated with inline comments (UTF-8 + BOM); new options are appended and existing values are preserved.
Notes
- Client and server should both run v1.4.2. Older clients fall back to item-ID matching.
简体中文
修复
- 修复了同一件原版底料的多个自定义道具(例如两个都是
minecraft:stick的神器)互相补错的问题。 - 耐久型工具仍可正常补给:身份比较中剔除
Damage与RepairCost。
新增
nbtIdentityKeys(默认CustomModelData):物品带有身份主键时只看主键,忽略实例 UUID / 剩余次数 / Lore。玩法服(如 The Sky Blessing)依赖这一项才能补对物品。- 新增
nbtIgnoreKeys、nbtMatchMode、allowSameItemFallback三个可调项。 debugRefillLogging下新增身份诊断日志。
调整
- 背包中没有同一身份的物品时不再补给,而不是拿一件同 ID 的其他物品顶上。
config/kabutack-auto-refill.properties改为带中文注释的格式(UTF-8 + BOM),新增项自动追加,已有取值保留。
说明
- 建议客户端与服务端同时更新到 v1.4.2;旧客户端会自动退回按物品 ID 匹配。
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:mr1owHxk:5I01U0wk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mr1owHxk:5I01U0wk"
}

