1.6.7
Compatibility
Changes
π οΈ Update v1.6.7 β Stable Override & Cooldown Fixes
β’ Cooldown Fix: cooldowns no longer reset when hitting or switching slots β fully stable timers. β’ Safer BossBar: improved cross-version compatibility (1.20.6β1.21+). β’ Improved PvP Override: stronger and faster control over WorldGuard, Essentials, PvPManager, and CombatLogX. β’ Reload++: /lobby4pvp reload now refreshes all timers, BossBars, and configs instantly with no ghost tasks. β’ Conflict Detection 3.0: clearer console logs for PvP plugin conflicts. β’ Polish: smoother activation/deactivation flow, cleaner debug output, and full Java 21 optimization. β’ Full support for Java 21 and Paper/Spigot 1.20.6β1.21+.
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:Tshp2CNf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aNnHsvOU:Tshp2CNf"
}

