No Pvp Log — anti-combat-log protection for fair Minecraft PvP

No Pvp Log is a Minecraft plugin that blocks teleportation and logout during combat, punishing combat loggers with death or ban. Essential anti-log protection for fair PvP servers.

Download NoPvpLog for Minecraft 1.6.2

Original name: NoPvpLog

Minecraft: 1.6.2

FileVersionLoaderSize
NoPvpLog.jar1.6.25 КБDownload

No Pvp Log: Prevent Combat Logging on Your Minecraft Server

Every Minecraft server administrator knows the frustration: a heated PvP duel is underway, both players are trading blows, and suddenly one of them vanishes into thin air. A quick teleport command, a forced disconnect, or a sneaky client-side mod — all of these tactics shatter fair combat and leave the remaining player feeling cheated. This is the classic problem of combat logging, and it has plagued multiplayer servers since the earliest days of the game. Fortunately, there is a straightforward and effective solution designed specifically to address this issue: the No Pvp Log: Prevent Combat Logging on Your Minecraft Server plugin.

This plugin is a lightweight administrative tool that forces players to see their battles through to the end. It was the first project released by its developer on their current account, yet it quickly gained traction within the community. Within just a few months of its initial release, the plugin surpassed one thousand downloads, and by November 2013, that number had grown to 2.5 thousand. While it was originally built for Minecraft version 1.7.2, the core logic remains relevant even today. Many modern server administrators adapt similar mechanics for their contemporary builds, proving that the concept behind this tool is timeless.

Understanding the Core Combat Mechanic

The heart of the plugin is a distinct "Combat" state that both players enter after they exchange their first blow. The moment one character attacks another, a configurable timer is activated. For a specified number of seconds, defined in the configuration file, both participants are officially considered to be in combat. During this state, the plugin can block the use of any commands — for example, /spawn, /home, or /tpa — which are the go-to tools for dishonest PvP loggers who want to escape a losing fight. If a player attempts to log out while in this state, they face a punishment determined by the server administrator.

This approach eliminates the most common methods of dodging a fight. No more instant teleportation to a safe zone, and no more emergency disconnects to the lobby. The plugin ensures that if you start a fight, you are committed to finishing it. For players who appreciate fair battles and want to quickly find servers that enforce these rules, a convenient solution is to use a launcher that provides curated modpacks. Such a launcher allows you to browse and select ready-made server configurations directly from its menu, saving you the hassle of manual installation. You simply choose your preferred version and connect to a server where the PvP mechanics are already properly configured.

Punishments for Leaving Combat

When a player exits the server while in the "Combat" state, one or more actions are triggered based on the configuration file. The developer intentionally kept the configuration simple, avoiding unnecessary parameters. The following options are available to administrators:

  • Kill_On_Pvp_Log — When a player logs out during combat, their character instantly dies, and their items drop on the ground. This is a classic and highly effective deterrent that discourages cheating.
  • Ban_On_Pvp_Log — The player receives a temporary or permanent ban. This is a harsh but fair consequence for repeat offenders.
  • Announce_On_PvP_Log — A message is broadcast to the server chat, naming the player who fled from a fair fight. This public shaming lets everyone know who the "hero" is that ran away.
  • Disable_Commands_In_PVP — This blocks the use of any commands during combat. It closes the loophole of teleportation before the player even has a chance to log out.

All of these parameters accept boolean values (true/false), and the duration of the combat state is set in seconds using the Time_In_Combat key. This minimalist design allows you to configure the plugin in under a minute after installing it on your server. The simplicity is a major selling point; you do not need to wade through pages of documentation to get the plugin working exactly the way you want.

Installation and Compatibility Details

Installing the plugin is a straightforward process. It is distributed as a standard JAR file that you place into the plugins folder of your server directory. After a restart, the plugin immediately begins working with its default settings. The version discussed here was tested on Minecraft 1.7.2, but the source code is open, and with a bit of effort, it can be adapted for newer builds. The source is available on GitHub, which allows the community to fork and enhance the functionality over time.

For players who want to join a server running this plugin, no additional client-side actions are required — everything operates server-side. However, if you prefer to play with mods or frequently switch between different game versions, a dedicated launcher can be an excellent companion. It will automatically select compatible mods and spare you the hassle of manually managing files. This is particularly useful for players who want to experience the anti-combat-logging mechanic without the technical overhead.

To get started, you can easily download No Pvp Log: Prevent Combat Logging on Your Minecraft Server from the official distribution platforms. The plugin file is small, so the download is quick, and the installation process is identical to any other Bukkit or Spigot plugin. If you are unsure about the steps, a quick search for "how to install" will yield numerous guides that walk you through the process of placing the JAR in the correct directory and restarting the server. The plugin is designed to be as frictionless as possible for administrators of all skill levels.

Planned Features and Future Development

The developer has left a public TODO list that outlines the future direction of the plugin. Among the ideas are:

  • Expanded punishments — This includes loss of in-game currency, temporary bans, or stripping faction power as additional penalties for combat loggers.
  • Flexible command filtering — A more granular configuration that allows administrators to specify exactly which commands are allowed or forbidden during combat.
  • Ender pearl blocking — Preventing the use of ender pearls while in combat, which would eliminate yet another popular escape method used by players.

While these features are not yet implemented, the plugin in its current state already does an excellent job of fulfilling its primary purpose. Bug reports are accepted through tickets or comments, and the developer remains open to feedback from the community. This commitment to ongoing improvement is a good sign for administrators who rely on the plugin for their day-to-day server management.

Why This Plugin Remains Relevant Today

Even though the plugin is several years old, its core concept lives on in hundreds of modern alternatives. The idea is simple: force players to take responsibility for their actions in PvP and deny them easy escape routes. Servers with active PvP modes still use similar mechanics today, because fair fights are the foundation of interest in survival and mini-game modes. The plugin’s transparent logic and minimal configuration requirements make it a true classic among server administration tools.

If you administer a server and are tired of complaints about PvP loggers, installing No Pvp Log: Prevent Combat Logging on Your Minecraft Server for Minecraft will solve the problem in no time. The plugin is particularly effective on factions servers, survival servers, and any other game mode where PvP is a central element. Its presence alone often deters players from attempting to log out mid-fight, as they know the consequences are immediate and severe.

For players who are searching for servers with proper PvP rules, it is worth looking into curated modpacks available through popular launchers. These packs often include projects where such plugins are already integrated into the base package of mods. This means you can join a server and immediately enjoy a fair PvP environment without worrying about someone vanishing mid-duel. The combination of a reliable anti-combat-logging plugin and a well-maintained server creates the ideal conditions for competitive and enjoyable gameplay.

In conclusion, No Pvp Log: Prevent Combat Logging on Your Minecraft Server is an essential tool for any server administrator who values fair play. Its simple setup, clear configuration options, and effective punishment system make it a must-have addition to your server’s plugin collection. Whether you are running a small private server with friends or a large public community, this plugin ensures that every PvP encounter ends with a definitive winner — not with a cowardly escape.