1.0.2
Compatibility
Changes
š Fixed
Fixed an issue where players were combat-tagged even when no damage was actually dealt
This resolves false combat tags when:
PvP is disabled (e.g. BetterTeams friendly fire off)
Players are protected while typing /login
Damage is cancelled by regions or protection plugins
Combat is now only triggered when real damage is applied
ā Improved
Combat now ends immediately after killing a player
Prevents players from being stuck in combat after winning a fight
ā Technical
Improved damage validation using:
Cancelled event checks
Final damage checks
Updated internal logic for better plugin compatibility
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:Jjd1ZbrZ:ePN9KLle"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Jjd1ZbrZ:ePN9KLle"
}

