C
PLUGIN DOCUMENTATION

Combat Log

Players who hit each other are put in combat for as long as you set in the config. Logging out in combat kills them. While they’re in combat you decide which commands, teleports, items, potion effects and areas are off limits, and every kill is counted.

Paper / Folia 26.1+Java 25PlaceholderAPI optionalWorldGuard optional

What it does

⚔

Combat tag

Hitting a player puts you both in combat. The time left counts down above the hotbar, with a tick sound at the end.

✕

Logging out kills

Leaving in combat kills the player like a normal death and gives the kill to the last player who hit them.

▣

Safe zone wall

Players in combat see a glowing wall at the edge of safe zones and can’t get in, not even with pearls or on a horse.

⏱

Item cooldowns

Give any item a cooldown in combat or block it completely. Elytra gliding can be turned off.

⚗

Blocked potions

Effects like invisibility are taken away in combat and given back when it ends.

☠

Kills and streaks

Kills, deaths, K/D and kill streaks, saved in SQLite, MySQL, MariaDB, PostgreSQL or MongoDB.

✉

Kill messages

Your own kill and death messages, with the weapon shown on hover. Every message can have a sound.

/

Command blocking

Block the commands you list, or allow only those. Teleports from commands and plugins are blocked too.

%

Placeholders

The combat timer, kills, deaths, K/D and kill streaks for scoreboards and tab.

Quick start

  1. Place the Combat Log JAR in plugins and start the server once.
  2. Set license-key in plugins/CombatLog/config.yml.
  3. Restart and check the console for License verified.
  4. Hit another player in survival. You both see the combat timer above the hotbar.

Explore the docs