CombatGuard
Nothing frustrates a PvP server community more than a player who disconnects the moment they start losing a fight. Combat logging ruins the experience for everyone, turning intense battles into cheap escapes. CombatGuard is the definitive solution for Minecraft server owners who want to enforce fair play without complex configurations. This lightweight plugin automatically tags players in combat and delivers instant justice to anyone who tries to log out to avoid defeat.
What is CombatGuard for Minecraft?
CombatGuard is a streamlined plugin designed specifically for Paper servers running modern Minecraft versions. Unlike bloated anti-cheat suites that consume resources, CombatGuard focuses on one critical task: punishing players who disconnect during PvP combat. When you install CombatGuard, you give your community a clear message that combat logging will not be tolerated. The plugin operates silently in the background, tagging players the moment they engage in a fight and removing the tag only when the danger has passed.
How CombatGuard Works
The logic behind CombatGuard is elegantly simple. When Player A strikes Player B, both are immediately tagged as "in combat." A 15-second timer begins counting down. If either player disconnects from the server during those 15 seconds, CombatGuard automatically slays them, and a broadcast message announces the combat log to the entire server. This public shaming acts as a powerful deterrent. If no further combat occurs between the tagged players for the full 15 seconds, the tag is removed and they are free to log out safely. The system ensures that only those who actively try to escape a fight face consequences.
Real-Time Combat Tagging
CombatGuard does not rely on guesswork. The moment a player deals or receives damage from another player, the plugin instantly applies the combat tag. This immediate response leaves no window for a quick disconnect. The tag persists for exactly 15 seconds, a duration carefully chosen to be long enough to prevent escape but short enough not to inconvenience players after a legitimate fight ends.
Clear Server-Wide Notifications
Transparency is key to maintaining trust. CombatGuard sends a warning message to players as soon as they enter combat, reminding them not to log out. If someone ignores that warning and disconnects, the plugin broadcasts a death message to the entire server, naming the player who combat logged. This feature not only punishes the offender but also reassures honest players that the server takes fair play seriously.
Key Features of CombatGuard
- Automatic combat tagging when players hit each other.
- Fixed 15-second combat timer that resets on each new hit.
- Instant death for any player who disconnects while tagged.
- Broadcast message announcing the combat log to the whole server.
- Personal warning message so players know they are in combat.
- Zero configuration required — works right out of the box.
- Extremely lightweight, with no impact on server performance.
Compatibility and Requirements
CombatGuard is built exclusively for Paper servers, taking advantage of Paper’s modern API to deliver reliable performance. The plugin requires Paper 1.21.2 or any newer build, ensuring compatibility with the latest Minecraft features. On the software side, your server must run Java 21 or higher. Because CombatGuard avoids unnecessary hooks and listeners, it remains fully compatible with other popular plugins like anti-cheats, economy systems, and minigame frameworks. Whether you run a survival world, a factions server, or a dedicated PvP arena, CombatGuard integrates seamlessly.
If you use the foxygame.net launcher to manage your Minecraft servers, adding CombatGuard is even easier. The launcher’s built-in add-on catalog lets you install CombatGuard with a single click, automatically matching the correct version to your server’s Paper build and keeping the plugin updated without manual file replacements.
How to Install CombatGuard
Getting started with CombatGuard takes less than a minute. First, ensure your server is running Paper 1.21.2 or newer and Java 21+. Then, download CombatGuard from its official page. You will receive a .jar file. Place this file into your server’s plugins folder. Restart the server or run the plugman load CombatGuard command if you have a plugin manager. That is it — CombatGuard begins working immediately with no configuration files to edit. To verify the installation, simply have two players hit each other and check for the combat warning message. If you ever need to remove the plugin, just delete the .jar file and restart.
Why Every PvP Server Needs CombatGuard
Combat logging is not just an annoyance; it undermines the entire PvP ecosystem. When players know they can escape death by disconnecting, they take risks they would otherwise avoid, and honest players feel cheated. CombatGuard restores balance by making the cost of combat logging exactly what it should be: death. The plugin’s lightweight design means you can add this layer of protection without sacrificing server performance. Its simplicity also means no learning curve for staff or players — everyone understands the rules instantly.
For server owners who want to maintain a competitive and fair environment, CombatGuard for Minecraft is an essential tool. The automatic slay mechanic and public broadcast create a strong social contract. Players quickly learn that disconnecting is not an option, and the quality of PvP encounters improves dramatically. Combined with the ease of installation and zero maintenance, CombatGuard is the smart choice for any PvP-focused server.
Conclusion
CombatGuard delivers exactly what it promises: a lightweight, no-nonsense solution to combat logging. With its automatic tagging, 15-second timer, and instant punishment for disconnectors, it keeps your server’s PvP fair and enjoyable. The plugin’s compatibility with modern Paper builds and Java 21 ensures it will run smoothly on your setup. If you are ready to stop combat loggers and give your players the fair fights they deserve, download CombatGuard today and let the plugin handle the rest.
===ARTICLE===