1.12.2
Compatibility
Changes
Kyra 1.12.2 — Paper 26.3 API compatibility fixes Replaced removed Registry.ENCHANTMENT.getKeys() usage with registry streaming. Removed duplicate local player declarations in crate and inventory event handlers. Replaced legacy biome enum lookup with Registry.BIOME lookup. Avoided deprecated-for-removal mob-spawn reason and game-rule constants. Replaced deprecated OldEnum name() calls with toString() where used for enum-like Bukkit API identifiers. No OP self-trade/test mode is included.
there are some known bugs. Working on it, expect an update tomorrow.
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:gVvsAMh6:mOFxcTFF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gVvsAMh6:mOFxcTFF"
}
