1.8.6
Compatibility
Changes
Update v1.8.6 — Compatibility, Stability & Hotfix Polish • Improved backward compatibility with older config files through safer auto-repair and validation. • Reduced false-positive config warnings, especially for valid sounds, particles, lore lines, and cross-version aliases. • Improved overall lobby PvP stability across joins, respawns, teleports, world changes, reloads, and external plugin interactions. • Refined managed sword, armor, and PvP-state handling to avoid stuck or inconsistent states. • Improved compatibility with both older Paper versions and the latest modern Paper API line. • Verified build compatibility across 1.18, 1.18.1, 1.18.2, 1.19.4, 1.20.6, 1.21.11, and source compatibility with Paper 26.1.x. • Focused entirely on hotfixes, polishing, compatibility, and safer release quality with no new gameplay features added.
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:aNnHsvOU:u7vY2d7t"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aNnHsvOU:u7vY2d7t"
}

