
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.0.5
Compatibility
Changes
New Features
World-Specific Combat Rules
- Each world can now have its own combat settings
- Worlds can inherit settings from other world configurations using the
inheritoption - Per-world configurable options:
- Enable or disable combat logging in specific worlds
- Set different combat timer durations per world
- Define world-specific blocked commands
- Customize boss bar colors per world
- Option to clear combat status when entering a world
- Enable or disable combat profiles per world
- Enable or disable punishment scaling per world
Combat Profiles System
- Players are automatically categorized based on their combat behavior
- Four profile types: Aggressive, Defensive, Escape-Prone, and Neutral
- Profiles track player statistics including:
- Total attacks made
- Damage dealt
- Damage taken
- Number of combat logs
- Escape attempts (blocked commands used during combat)
- Staff can view any player's combat profile with
/combatlog profile <player> - Player profiles persist across server restarts
Punishment Scaling
- Punishments can now be scaled based on player combat profile
- Escape-prone players receive harsher penalties (1.5x multiplier by default)
- Defensive players receive lighter penalties (0.8x multiplier by default)
- Use
%multiplier%placeholder in punishment commands to apply scaling - Punishment scaling can be enabled or disabled per world
Safe World Protection
- Players cannot teleport to worlds with combat disabled while in combat
- Attempting to teleport to a safe world during combat is blocked and logged as an escape attempt
Combat Clearing on World Change
- Worlds can be configured to clear combat status when players enter them
- Useful for spawn areas or safe zones
Improvements
- Combat violations are now logged with additional profile information
- Profiles are saved and loaded automatically on server start/stop
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:OPWdBrQQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:unaoPU3I:OPWdBrQQ"
}
