Set up CombatLogX on your Minecraft server

CombatLogX tags players when they fight and punishes them if they log out during combat. Extra features such as a boss bar, a force field and a newbie helper come as separate expansion jars. It is a plugin for Paper or Purpur, and its install is different from most: it comes as a zip of several files.

Checked against CombatLogX 11.6.0.0.1286, the latest release on its SpigotMC page (July 2025), October 2026. The project's source is on its 11.7 development line, and its README lists Spigot, Paper or Folia 1.8.8 to 26.1.2. The 11.6 release dates from July 2025, and the versions its author recommends (listed under What you need) stop at 1.21.7, so Minecraft 26.x is not among them.

What you need

• A Paper or Purpur server. Vanilla servers have no Plugins tab; switch software in JAR Manager first (see Change your Minecraft version or mod loader).
• Minecraft 1.20.5 or newer. The classes in the 11.6 jar are built for Java 21, and our panel starts using Java 21 at 1.20.5. The SpigotMC page names 1.19.4, 1.20.6 and 1.21.7 as the versions the author tests, and says others may work but are not tested.
• BlueSlimeCore, which CombatLogX requires. It is inside the download, so you do not need to fetch it separately.

Install it

The Plugins tab has no SpigotMC source, and the download is a zip with a fixed layout, so install it from File Manager.

1. Download CombatLogX.zip from the plugin's SpigotMC page.
2. Open File Manager and go into the plugins folder.
3. Click Upload files and choose the zip.
4. Click Extract here on the zip. It unpacks into the folder you are in.
5. Check that plugins now holds CombatLogX.jar, BlueSlimeCore.jar and a CombatLogX folder with an expansions folder inside. Delete the zip.
6. Use Restart on the Console tab.

Once it is running, clx version in the Console prints the version.

First run

CombatLogX writes config.yml, commands.yml, punish.yml and language.yml into plugins/CombatLogX. Each expansion has its own settings under plugins/CombatLogX/expansions. After any edit, run clx reload.

Defaults worth knowing:

• In config.yml, timer.type is GLOBAL and timer.default-timer is 10 seconds. The PERMISSION type uses combatlogx.timer.<seconds> instead.
• bypass-permission is combatlogx.bypass. Operators do not have it by default.
• minimum-tps is 15.0, the lowest TPS at which tagging still happens.
• disabled-world-list is empty. List world names there to switch tagging off, or set disabled-world-list-inverted to true to treat the list as the only worlds where it runs.
• In punish.yml, on-disconnect is true, on-kick is false, and kill-time is QUIT, so the player dies the moment they log out. It also accepts JOIN and NEVER.
• Commands that run on tag, untag or punishment go in commands.yml.

Expansions

The zip includes expansions such as Action Bar, Boss Bar, Cheat Prevention, Force Field, Mob Tagger and Newbie Helper, plus compatibility expansions for plugins like WorldGuard, Towny and EssentialsX. They all load from plugins/CombatLogX/expansions. To remove one, delete its jar from that folder and restart. Force Field also needs the ProtocolLib plugin.

Commands

• /combatlogx, shortened to /clx, has subcommands including help, about, version, reload, tag, untag and toggle. Those default to operators. There is also a forgive set (request, accept, reject and toggle), where forgive-request-cooldown and forgive-request-expire in config.yml default to 30 and 10 seconds.
• /combat-timer [player] shows time left in combat, and everyone can use it by default.
• /togglepvp comes from the Newbie Helper expansion, so it only works while that expansion jar is in plugins/CombatLogX/expansions. Without it the command only replies that the expansion is unknown. Everyone can use on and off by default. check <player> and admin on/off <player> are for operators unless you grant combatlogx.command.togglepvp.check and combatlogx.command.togglepvp.admin.

Common problems

• CombatLogX is disabled at start. Read the Console. A missing BlueSlimeCore is the first thing to rule out, because the plugin requires it.
• Players are not tagged. Check disabled-world-list, minimum-tps and whether the player has the bypass permission.
• An expansion does nothing. Confirm its jar sits in plugins/CombatLogX/expansions, then restart.