Tags
Creators
Details
0.0.2-beta
Compatibility
Changes
Changelog / 更新日志
-
Released
0.0.2-betawith centralized favorite-slot protection across Fabric, Forge, and NeoForge. 发布0.0.2-beta,统一 Fabric、Forge、NeoForge 的收藏槽位保护逻辑。 -
Added server-side favorite handling, interaction guards, and Instant Swap Engine compatibility. 新增服务端收藏处理、交互保护和 Instant Swap Engine 兼容支持。
-
Fixed item duplication issues involving Reliquary Void Tear and Wrench Finder on NeoForge. 修复 NeoForge 下 Reliquary Void Tear 和 Wrench Finder 的物品复制问题。
-
Fixed the locked main-hand guard incorrectly affecting
FakePlayer. 修复锁定主手保护对FakePlayer的误判。 -
Added tests for favorite management, interaction guards, Instant Swap, and mod compatibility. 补充收藏管理、交互保护、Instant Swap 和兼容性测试。
-
Updated GitHub Actions, JUnit configuration, build artifact naming, and project documentation. 更新 GitHub Actions、JUnit 配置、构建产物命名和项目文档。
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:7hKKPXQq:VKSZK1hq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7hKKPXQq:VKSZK1hq"
}

