CombatLogger

How it works in play

• Tagging: damage from a player or a mob tags both sides for 15 seconds. Arrows, tridents and thrown potions tag the player who fired them.
• Countdown: a boss bar shows the seconds left, and a message tells the player when they're out of combat.
• Blocked commands: /tp, /tpa, /home, /spawn, /warp, /fly, /gamemode, /rtp, /back, /sethome, /trade and /shop are denied while tagged, aliases included (blocking /rtp also blocks /wild). You can edit the list.
• No hiding in spawn: a player tagged by another player can't walk into a safe zone. Near the border they see a red glass wall (only they see it, nothing is placed), and the server pushes them back if they try to cross, so a hacked client that hides the glass gets nowhere. Ender pearls into the zone are refused. Anyone who still gets in is killed at the last spot they stood outside, where their opponent can take the loot. Safe zones are WorldGuard regions with PvP denied and DominionForge's spawn.
• The body: a player who disconnects while tagged leaves an NPC with their skin, armour and held items for 30 seconds. Anyone can kill it, and the server announces who did.
• Coming back: if the body was killed, the player is killed on login (their items drop there) or has their inventory cleared, whichever you choose. If they reconnect while the body is still standing, they take its health and stay tagged.

For staff

• Alerts: staff with combatlogger.notify are told when someone logs out in combat, with their total count.
• History: each player's combat-log count is saved and survives restarts. /combatlog top lists the worst offenders.
• Safe zones: with WorldGuard, players aren't tagged inside regions where PvP is denied.
• Commands: /combatlog status <player>, /combatlog clear <player> for a stuck tag, and /combatlog reload.

How to use it

• Install: drop the jar into /plugins, restart once and it's ready. Install Citizens too if you want the body left behind. English is the default; set language: es for Spanish.
• Set the rules in config.yml: tag length, whether mobs tag (PvE), the blocked commands, how long the body stays and the penalty (kill or clear).
• Style the HUD: boss bar colour, style and text, and the out-of-combat message. Set combat-hud.enabled: false to hide it.
• Apply changes with /combatlog reload.

Commands and permissions

• Operators (combatlogger.admin): /combatlog status|clear|reload|top.
• combatlogger.notify receives the combat-log alerts (operators by default).
• combatlogger.bypass is never tagged; combatlogger.bypass.commands can use blocked commands while tagged; combatlogger.bypass.safezone can enter safe zones while tagged.

Placeholders

With PlaceholderAPI installed: %combatlogger_in_combat% and %combatlogger_time_left%.

FAQ

Do the items drop when the body is killed?No, they drop when the player logs back in and is killed (with the kill penalty). That way the inventory can't drop twice.

Can players get stuck in combat at spawn?Not in WorldGuard regions with PvP denied, where no one is tagged. Staff can also clear a tag with /combatlog clear.

What if I don't want the wall, or the kill?Set safe-zone.enabled: false to turn it off, or breach-penalty: teleport-back to send a player who slips in back outside instead of killing them. A mob hit never locks spawn: only a tag from another player counts.

Can mob damage be left out?Yes. Set pve-enabled: false and only players tag each other.

Can I translate the messages?Yes. English and Spanish are included in lang/, in MiniMessage, and missing keys fall back to English.

Does it work with TradeForge?

Yes. A tagged player carries the in-combat marker TradeForge checks, so trades are refused mid-fight without any setup.

Commands

Full command and permission reference in the docs ↗