0.0.4
Compatibility
Changes
奖池之间可以自动转化钥匙,示例: 开B箱时没有钥匙,就自动转化A箱的10把钥匙转化为B箱钥匙使用
key-conversion:
auto-convert: true
rules:
- from: "CrateA"
to: "CrateB"
ratio: 10
message: "&a[PitySystem] &f你没有 &bCrateB &f钥匙,已自动消耗 &e10 &f把 &bCrateA &f钥匙进行兑换!"
现可以通过PlaceholderAPI变量查看玩家的保底信息:
%pitysystem_count_<crate>% - 玩家当前的保底计数。
%pitysystem_max_<crate>% - 该奖池设定的最大保底次数。
%pitysystem_left_<crate>% - 距离下一次保底还剩多少次(计算方式:max - count)。
%pitysystem_groupcount_<CommonPool>% - 如果使用了共享保底,获取该组的共享计数
示例: 如果你的奖池名为 ExampleCrate,则可以使用 %pitysystem_count_ExampleCrate%
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:XI9NABWW:N2hiaXtU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XI9NABWW:N2hiaXtU"
}

