Combat Log Detector helps administrators see when someone leaves during PvP. It watches player combat interactions, identifies a disconnect during the combat window, and sends the event to Discord for review. Its purpose is to provide information for moderation, without automatically killing or punishing the player.
- Installed on
- The server
- Combat window
- 10 seconds
- Notifications
- Discord webhook
- Project status
- Archived
From a PvP hit to a disconnect event.
The documented combat window is ten seconds after a player hits another player or is hit in PvP. If they leave during combat, the plugin identifies that disconnect as an event administrators can review.
A PvP interaction is detected.
A player hits another player or receives a PvP hit.
The player is marked in combat.
The documented combat tag lasts ten seconds after the interaction.
Leaving becomes a report.
A disconnect during combat is recorded and can trigger a Discord notification.
Keep event context in Discord.
A Discord-compatible webhook delivers notifications about combat logging. The published feature description includes the player name, world name, and X, Y, Z coordinates in the notification, so staff have context when reviewing what happened.
The webhook URL is configured in the plugin's generated config.yml. The project is a server plugin; ordinary players do not need to install a client mod to produce these reports.
| Detail | Why it is included |
|---|---|
| Player name | Identifies the player who disconnected. |
| World name | Shows which world the event occurred in. |
| Coordinates | Provides the location associated with the event. |
Detection without automatic punishment.
Combat Log Detector does not kill a player or apply a punishment for disconnecting. It supplies a report so administrators can decide how to handle an event under their own server rules.
That distinction is part of the project's published behavior. The plugin detects the disconnect and its context; it does not claim to know why a connection ended.
Set up the server notification path.
Place the matching plugin JAR in your server's plugins folder, start the server to generate config.yml, enter your Discord webhook URL, and restart the server to apply the configuration.
Part of our plugin archive.
The project is archived on Modrinth. Its published files, description, and source remain useful references, but this page does not imply current development or support for newer Minecraft versions.
Read the original documentation and check individual files for release-specific requirements.
Modrinth documentation & releases
