AntiLog — Smart Combat Log Protection for Minecraft Servers

Understanding the Combat Logging Problem

Every Minecraft server administrator knows the frustration of combat logging. A player engages in a heated PvP battle, realizes they are about to lose, and quickly disconnects from the server to avoid death. This not only ruins the experience for honest players but also undermines the competitive integrity of any survival or factions server. The AntiLog plugin steps in to solve this issue in a clean, lightweight way that doesn't bog down your server's performance.

How AntiLog Tags and Punishes Quitters

AntiLog introduces a straightforward tagging system. Whenever a player is hit by another player or a mob (fully customizable), they receive a combat tag that lasts for a configurable number of seconds—10 seconds by default. While tagged, the player cannot use any commands, preventing them from teleporting away, accessing kits, or executing other tricks to escape. If they decide to disconnect from the server during the tag period, the plugin instantly kills their character, ensuring that combat logging carries a real consequence.

The beauty of AntiLog lies in its simplicity. It doesn't overcomplicate the mechanic with unnecessary features or heavy database queries. Once installed, it just works, keeping your server fair and fun for everyone. Server owners who also want a smooth client-side experience often turn to the foxygame.net launcher, a convenient and modern Minecraft launcher where you can download mods right from the menu, making it easy to manage your entire game setup while AntiLog handles the server-side rules.

Key Features That Make AntiLog Stand Out

AntiLog packs a surprising number of customization options into a tiny plugin file. Here’s what you can expect when you add it to your server:

• Combat logging prevention: Automatically kills players who disconnect while tagged.
• Command blocking: Stops tagged players from using any commands, with an option to configure a whitelist of allowed commands.
• Adjustable tag duration: Set the tag time to anything from a few seconds to several minutes.
• Custom messages: Every notification—from the tag warning to the death broadcast—can be personalized to match your server’s style.
• World-specific toggles: Disable tagging entirely in specific worlds, such as creative plots or minigame lobbies.
• Exempt permission node: Grant the antilog.exempt permission to staff or VIPs who should never be tagged.
• Damage source control: Choose whether players get tagged from player attacks, mob attacks, or both.
• Death untagging: A tagged player who dies legitimately is automatically untagged, preventing double penalties.
• Bypass compatibility: An optional setting allows the plugin to override other plugins that might cancel PvP damage on a tagged player, keeping the tag system consistent.

Installation: A Drag-and-Drop Affair

Setting up AntiLog is as simple as it gets. Download the plugin jar file from your trusted source, then drag and drop it into your server’s plugins folder. Restart the server or run a reload command, and AntiLog will generate its default configuration file. From there, you can tweak every aspect to your liking without ever touching the code.

No complicated dependencies, no database setups. The plugin is designed to be lightweight, so even servers running on modest hardware will see no noticeable performance impact.

Diving Into the Configuration

Once the config file appears in the AntiLog folder, you can open it with any text editor and start customizing. Here are the most important settings you’ll want to adjust:

• tag-time: The number of seconds a player remains in combat after being hit.
• allowed-commands: A list of commands that tagged players can still use (for example, /msg or /help).
• log-message: The message broadcast to the entire server when someone combat logs and dies.
• disabled-worlds: Worlds where the tagging system should not activate.
• tag-by-mobs: Set to true if you want mob attacks to apply a combat tag.
• tag-by-players: Set to true for player-inflicted tags.
• bypass-other-plugins: When enabled, AntiLog will force-tag a player even if another plugin tries to cancel the damage event.

For a complete breakdown of every configuration option, refer to the plugin’s official documentation page. The defaults are sensible, but taking a few minutes to tailor the messages and timings will make the plugin feel like a native part of your server.

See AntiLog in Action

If you want to experience how the plugin behaves before installing it, you can join the NostrumCraft network at play.nostrumcraft.com. Both their PvP and survival servers run AntiLog, giving you a firsthand look at the tag system, the death-on-logout mechanic, and the custom messages in a live environment. It’s a great way to test whether the plugin fits your community’s needs.

Why AntiLog Deserves a Spot on Your Server

Combat logging is one of those issues that can quietly drive players away. When a fair fight ends with a disappearing opponent, it leaves a sour taste. AntiLog eliminates that loophole with minimal overhead and maximum configurability. The permission-based exemption keeps your staff happy, the world toggles prevent interference in non-PvP areas, and the customizable messages let you inject personality into every punishment.

Whether you run a hardcore factions server, a casual survival world, or a competitive PvP arena, AntiLog gives you the tools to enforce combat integrity. Its lightweight nature means you can add it to an existing server without worrying about lag, and the simple config makes ongoing maintenance effortless. For server owners who value fairness and want to keep their players engaged, this plugin is an essential addition.