Combatlog
Combatlog lets server owners stop players from logging out during combat by starting a configurable countdown after a player hits another player or a mob.
What it does
When a player damages another player or a mob, a countdown starts and runs for a set length of time. A player who leaves before the countdown ends has their items dropped on the ground and can be punished, which makes logging out mid-fight pointless. The timer length, the events that trigger combat, and the messages shown to players are all configurable.
Movement and actions can be limited while the timer runs. Elytra flight, ender pearls and a blacklist of commands such as home or combat-related teleports can be blocked, and a kill can be set to run a command against a player who logs out. The mod only needs to run on the server, so players join without installing anything, and Fabric API is required.
Combatlog is published for Fabric, Forge and NeoForge across 26 release versions, 1.16.5 – 26.3, and the code is open source under the MIT License.
Key features
Customizable combat timer
Server owners set how long a player stays in combat after a hit, separately for player and mob damage.
Damage source control
The combat trigger can be limited to chosen sources, so only selected kinds of damage start the countdown.
Restricted movement items
Elytra flight and ender pearl use can be disabled while a player is in combat.
Command blacklist
Specific commands, such as home or combat teleports, are blocked while the timer is running.
Disconnect punishment
A player who logs out during combat can be penalized, and a command can run when a kill happens during the countdown.
Compatibility
Latest build for each game version and loader.
26.x5 of 5 versions with builds
1.21.x11 of 11 versions with builds
1.20.x5 of 5 versions with builds
1.19.x3 of 3 versions with builds
1.18.x1 of 1 version with builds
1.16.x1 of 1 version with builds
Only full game releases are shown. This mod publishes no snapshot builds.
Requirements
Dependencies declared by the latest file for each loader.
Required 1
Use cases
Survival and PvP servers
Server owners running player-versus-player worlds can keep fights from ending with a quick logout.
Who it’s for: Server owners who want to discourage combat logging. The mod needs no client install, and players who play single-player on a LAN host only need it if the server is hurt by logouts.
How it compares
CombatLock is server-side only and open source under the GNU General Public License v3.0 only, but it is published only for Fabric and version 1.21. Player Death Kick is server-side only, published for Fabric, Forge, NeoForge and Quilt across 1.16.5 – 26.3, and is not open source, under All rights reserved.
| Mod | Loaders | Game versions | Environment | Updated |
|---|---|---|---|---|
| Combatlog | Fabric, Forge and NeoForge | 1.16.5 – 26.3 | Server-side only | 2026-09-25 |
| CombatLock | Fabric | 1.21 | Server-side only | 2024-08-07 |
| Player Death Kick | Fabric, Forge, NeoForge and Quilt | 1.16.5 – 26.3 | Server-side only | 2026-10-12 |
Questions
Does Combatlog need Fabric API?
Do players need to install Combatlog?
Which loaders have Combatlog files?
In the catalog
Combatlog is one of 36,990 Utility mods on ModsFinder, and one of 25,772 Utility mods for Fabric. 8,071 mods support Minecraft 26.3.
Similar mods
What the author says
This mod tries to prevent people from combat logging on a server. After a player is hit by another player, both of them have a configurable countdown assigned to them. If either of them leaves before that countdown is over, they are killed and all of their items are dropped on the ground. All settings are configured…
Official listing
- Modrinth page
- modrinth.com/mod/combatlog
- Owner
- WildToastyMop
- Published
- 2022-09-01
- Updated on Modrinth
- 2026-09-25
- Facts verified
- 2026-10-15