
CombatLog999
CombatLog999 is a Bukkit plugin that prevents players from logging out or teleporting during combat, ensuring fair play in PvP scenarios by implementing a robust combat system with configurable timers, penalties for combat violations, and player exemption
Tags
Creators
Details
1.1.0
Compatibility
Changes
Added
- Placeholder support for combat status, remaining time, profile type, and lifetime offense stats.
- Offline staff tools for profile lookup, profile resets, and ranked leaderboards.
- Configurable combat restrictions for pearls, rockets, elytra activation, invisibility, milk, and flight toggles.
- Database-backed storage with SQLite by default, optional MySQL support, and periodic autosaves for combat data.
Fixed
- Combat timers now survive reloads and restarts reliably instead of being lost before players return.
- Delayed combat tagging now clears correctly on death, world changes, and other combat cleanup paths.
- Profile tracking now fully respects global and per-world disable settings.
- Profile classification thresholds now follow configured values instead of fixed values.
- Default timer and boss bar settings now apply correctly when world overrides are not provided.
- World inheritance now resolves correctly regardless of configuration order.
- Reloading now refreshes runtime message display state correctly.
- Join protection timing now stays accurate across fast rejoins and correctly shows remaining time.
- Escape attempts are no longer counted for actions already cancelled elsewhere.
- Forced inventory drops no longer strip kept levels as a side effect.
- Re-enabling combat displays now restores active timers immediately.
- Combat displays now appear populated immediately instead of starting blank.
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:unaoPU3I:TFwv2omT"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:unaoPU3I:TFwv2omT"
}
