Screenshot 1 of 1. MinecraftHub-generated cover art for Simple Combat Log: a floating desert block island with server racks and a stone tower, under a night sky
What Simple Combat Log works with.
| Platform | Java Edition |
|---|---|
| Loaders | Paper, Purpur |
| Minecraft versions | 1.19, 1.19.4, 1.20.6, 1.21.11, 26.1.2, 26.2, 26.3 |
Simple Combat Log is a combat log plugin for Paper and Purpur servers, with older Bukkit and Spigot builds that have stopped. It starts a timer when a player deals or takes damage, then shuts the exits that PvP players abuse. It is server-side only, so players join with nothing extra installed.
Server software and versions
- Paper: Minecraft 1.19 to 26.3. The newest build needs no dependencies, optionally WorldGuard and PlaceholderAPI.
- Purpur: Minecraft 1.21 to 26.3. The newest build needs no dependencies, optionally WorldGuard and PlaceholderAPI.
- Bukkit and Spigot: Minecraft 1.19 to 1.21.4, builds stopped after December 2024. The newest build needs no dependencies.
Combat timer and restrictions
The timer shows on an ActionBar or a BossBar, and its length is fully configurable. A player who leaves mid-fight triggers a broadcast message. While the timer runs, each of these can be switched off independently:
- Elytra use, including the boost
- Teleporting
- Mending
- Riptide
- End Crystal and Respawn Anchor explosion abuse
Every restriction is optional. The feature set is narrow by design, aimed at competitive servers that want strict and predictable combat rules rather than a broad PvP suite.
What tags a player
Tagging is not limited to sword fights. Player damage, projectiles (arrows, tridents, wither skulls), explosions and Ender Pearl landings all count. An optional combat zone with radius detection is also available.
An anti kill abuse system stops the same victim from being farmed repeatedly. You set a kill limit and a time window, and custom punish commands run automatically when a player passes it.
WorldGuard region blocking
With WorldGuard present, the plugin registers a custom flag named allow-combat-entry. Set it on a region and players in combat cannot enter it. The integration is optional and nothing breaks without it.
Installation
Place the plugin file in the plugins folder of your Paper or Purpur server and restart. If you have not done this before, the guide on installing plugins on a server covers each step. Players do not install anything.
Questions about Simple Combat Log.
4 questions
Why does Simple Combat Log seem to do nothing when I test it?
Operators get the combatlog.bypass permission by default and are never tagged, so the timer never starts for them. Test with a normal non-OP player, or remove the permission from your operator group, and the combat timer and restrictions will appear as configured.
Does Simple Combat Log need WorldGuard?
No. WorldGuard is an optional integration with no hard dependency. If it is installed, the plugin registers the allow-combat-entry flag, which blocks region entry while a player is in combat. Without WorldGuard, the timer, restrictions and anti kill abuse system still work.
Do players have to install Simple Combat Log?
No. It is a server plugin, so only the server needs it. Players join with a normal setup and see the combat timer on their ActionBar or BossBar, depending on how the admin configured the display.
What actions can Simple Combat Log block during combat?
It can disable Elytra use including boost, teleporting, Mending, Riptide, and explosion abuse with End Crystals or Respawn Anchors. Each restriction is optional and configurable, so you choose which ones apply on your server.
