1.7
Compatibility
Changes
Update v1.7 — Stability & Safety Hardening • VIP Sword Fix: players can no longer keep both normal and VIP swords — inventory state is always correct. • Anti-Duplication Hardening: full protection against item duplication via containers, hoppers, creative mode, crafting stations, armor stands, and pickups. • Reload Stability: /lobby4pvp reload is now fully safe — no ghost PvP states, no stuck BossBars, no orphaned tasks. • Timer & State Reliability: activation, deactivation, and cooldown logic refined for maximum consistency under heavy event spam. • Compatibility Expansion: improved coexistence with major protection and PvP plugins across large and small lobby servers. • 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:f3eGVpEU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aNnHsvOU:f3eGVpEU"
}

