Links
Tags
Creators
Details
1.0-Release
Compatibility
Changes
⚔️ CombatGuard
A lightweight and configurable combat tag plugin for Minecraft SMP servers. Prevent combat logging and track player stats with a clean and simple system.
✨ Features
⚔️ Combat Tag System
When two players fight, both are tagged for a configurable duration. A progress bar displayed on the action bar shows the remaining combat time in real time.
🚪 Combat Logout Punishment
If a tagged player disconnects, they are automatically punished. Choose between an instant kill, a temporary ban, or both — all configurable.
📊 Stats Tracking
Every kill, death and combat logout is tracked per player and saved in individual JSON files. Stats are persistent across restarts.
🗂️ Tab List Stats
Optionally display each player's kills and deaths directly in the tab list — toggleable in the config.
⚙️ Full Config Support
Customize the prefix, combat duration, punishment type, ban duration, and tab stats display. Reload without restarting with /combatguard reload.
📋 Commands
| Command | Description |
|---|---|
/stats <player> |
Display a player's combat stats |
/combatguard reload |
Reload the config |
🔐 Permissions
| Permission | Description |
|---|---|
combatguard.admin |
Access to /combatguard reload |
⚙️ Config
# Plugin prefix
prefix: "CombatGuard "
# Combat tag duration in seconds
combat-duration: 15
# Punishment on combat logout: kill | ban | both
punishment: kill
# Ban duration in seconds (only if punishment is "ban" or "both")
ban-duration: 300
# Show kills/deaths in the tab list
tab-stats: true
📦 Installation
Drop the .jar into your plugins/ folder and restart your server. No dependencies required.
🔧 Compatibility
- ✅ Spigot / Paper
- ✅ Minecraft 1.21.x
Made with ❤️ by Gregwll
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:sP3BxQ96:CNc82jTy"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sP3BxQ96:CNc82jTy"
}

