
A simple and lightweight CombatTimer plugin!
CombatTimer is a lightweight and configurable Minecraft plugin that stops players from escaping combat by logging out.
It is built for survival, SMP, factions, and PvP servers that want fair fights without constantly needing staff to punish combat loggers manually.
CombatTimer can simply kill or ban combat loggers, or it can replace them with a lootable logout villager so the fight continues even after they disconnect.
CombatTimer tags players when they enter combat.
You decide what should trigger combat:
MOB
PLAYER
BOTH
This allows you to use CombatTimer for:
The combat duration is fully configurable.
Players can clearly see when they are still in combat.
Available display modes:
| Mode | Description |
|---|---|
ACTIONBAR |
Shows the timer above the hotbar |
BOSSBAR |
Shows the timer as a bossbar |
BOTH |
Shows both actionbar and bossbar |
NONE |
Hides the timer display |
Bossbar color is configurable.
One of CombatTimer’s main features is the optional logout villager system.
When a player logs out during combat, they can be replaced by a villager at their logout location.
That villager represents the logged-out player.
Other players can:
If the combat logger rejoins while their villager still exists:
Logout villagers are saved in the database and restored after server restarts, so combat loggers cannot escape by waiting for a reboot.
If logout villagers are disabled, CombatTimer can still punish combat loggers directly.
Supported punishment options:
Temporary bans support flexible durations:
30m
1h
1h 30m
2d
1w
If logout villagers are enabled, the configured punishment can still be applied when the villager is killed.
CombatTimer uses its own SQLite-backed ban system instead of relying on Minecraft’s default ban list.
This allows cleaner ban screens and better control over combat-log punishments.
Bans are stored locally in:
plugins/CombatTimer/combattimer.db
Staff can view and remove CombatTimer bans with plugin commands.
CombatTimer uses simple JSON configuration.
Example config:
{
"trigger_when": "BOTH",
"timer_seconds": 30,
"timer_display": "ACTIONBAR",
"bossbar_color": "GREEN",
"kill_on_logout": true,
"ban_on_logout": false,
"ban_type": "PERMANENT",
"tempban_duration": "1d",
"logout_villagers_enabled": true
}
All plugin messages can be edited.
You can customize:
File structure:
plugins/CombatTimer/
config.json
combattimer.db
translations/
messages.json
Trusted players or staff groups can bypass combat tagging.
combattimer.bypass
Reload config and translation files without restarting the server.
/combattimer reload
Missing files are recreated automatically.
| Command | Description |
|---|---|
/combattimer help |
Displays plugin commands |
/combattimer reload |
Reloads config and messages |
/combattimer unban <player> |
Removes a CombatTimer ban |
/combattimer banlist [page] |
Lists active CombatTimer bans |
Alias:
/ctimer
| Permission | Description | Default |
|---|---|---|
combattimer.help |
Allows /combattimer help |
true |
combattimer.reload |
Allows /combattimer reload |
op |
combattimer.unban |
Allows unbanning players | op |
combattimer.banlist |
Allows viewing CombatTimer bans | op |
combattimer.bypass |
Bypasses combat timer tagging | false |
combattimer.update.notify |
Allows receiving update notifications | op |
Combat logging can ruin fights.
Common problems include:
CombatTimer solves this by keeping combat fair, visible, and configurable.
Use a simple timer, punish combat loggers directly, or enable logout villagers for a more interactive and loot-friendly system.
PvP servers
SMP servers
Survival servers
Faction servers
Hardcore servers
Event servers
Lifesteal-style servers
CombatTimer is designed to be:
You decide when combat starts, how long it lasts, and what happens when someone logs out.
If you encounter issues or have feature requests, feel free to open a ticket in the Discord server.
Keep combat fair, stop logout abuse, and make every fight count.