Menu

plugin

CombatLOGMinecraft plugin

Combat logging prevention. Tags players during PvP with a boss bar, blocks configured commands, and kills anyone who disconnects while tagged. Configurable duration, projectiles, worlds and messages.

server only
Latest version
no release indexed
Minecraft
no version declared
Java
follows the game
Platforms
none declared
Licence
GPL-3.0-only
Downloads
587
Updated
12 d ago
Available on
Modrinth
Space NodeOur hosting

Host CombatLOG servers

One click and CombatLOG is installed on a Paper or Purpur server built for it.

  • One click plugin install
  • Paper and Purpur ready
  • Automatic updates
  • NVMe SSD
Deploy a serverFrom €0.90 per GB

Frequently asked

Do I need to install CombatLOG on the client or the server?

The server only. Players join with an ordinary Minecraft client and install nothing.

What licence is CombatLOG under?

GPL-3.0-only, as stated by the author on the platform we synced it from. Check the project's own page before redistributing or bundling it.

How do I install CombatLOG?

Choose the release variant for your server platform. Paper, Spigot, Purpur and Bukkit files go in the server's plugins folder; Fabric, Forge, NeoForge and Quilt files go in the mods folder. Restart after installing and check that the Minecraft version matches your server.

Where do I download CombatLOG safely?

MCReference has no release file or checksum recorded for CombatLOG. Check the publisher's Modrinth listing for current downloads and verify the publisher before installing.

Which Minecraft versions does CombatLOG work on?

The author has not declared a supported version in the metadata we sync, so there is nothing here we can state as fact. Check the project's own page before installing it, and treat an old plugin with no declared version as untested on modern Minecraft.

Details from Modrinth, where the author last updated it on 1 Oct 2026. We do not host files or republish descriptions. Available download links point to the author’s own release.

Not indexed yet. Score 53 against a threshold of 55. The page still exists and is still linked; it simply carries noindex until we hold more.

Is this information wrong or missing something? .