Combat Tag

Combat Tag Logo

The essential PvP plugin that prevents hit-n-quit players. No longer will the fun of killing other players be ruined!

Combat tag is a plugin that can prevent your players from pvp logging, period.
Reason why we developed this:
When your players are in the heat of battle, sometimes someone gets cold feet, and logs out while in combat!
This means that the player can no longer be harmed, because they are offline.
This can be EXTREMELY irritating to other players, because the person they were attacking, is now safe and keeps all of their items.

How it works:
Combat tag makes it impossible to pvp log!
When a player is struck by another player, combat tag logs it in its log.
If one of the players logs off within 10 seconds (time can be changed) of being struck, combat tag comes to play.
Combat tag makes it so that if the player logs off within the ten second field, he spawns an NPC with the same inventory/health as him.
The player that was attacking then can attack the NPC, and the same is done to the logged off player.
If the player kills the NPC, the player that logged off in combat is also killed, and drops everything in their inventory.
If the player causes damage to the NPC, the player that is logged off also takes the damage (including armor).

Video Demonstration:

Video tutorial español:

Video Tutorial italiano:


  • Tracks players in combat
  • Custom tag time
  • Supports disabling in specified worlds
  • Supports disabling commands while in combat
  • Use /ct or /combattag to keep track of how long until combat is over

How to install:
Everything that is needed for an install should be located here:

Explanation of the config file options:

There are five commands:
All "ct" can be replaced with "combattag"

/ct = Check your remaining tag time
/ct reload = Reload Combat Tag's configuration file
/ct wipe = Wipes all npcs on the map
/ct command add /<command> = Adds command to blocked commands list
/ct command remove /<command> = Removes command from blocked commands list

There are currently four permission nodes:
Note: Ops automatically get permissions

combattag.ignore = Player does not get tagged and doesn't spawn npcs
combattag.ignore.pvplog = Player does get tagged, but doesn't spawn npcs
combattag.reload = Allow player to reload the Combat Tag configuration file
combattag.wipe = Allow player to wipe all npcs on the map
combattag.command = Allow player to modify disabled commands from in game
combattag.alert = Alert people with this permission of a person logging out while in pvp


If you have any bugs or feature requests, go here!:

If you wish to use the Combat Tag API:

About Incompatibilities:
As with any plugin where fake players exist, there will be places where other plugins do not take into account the possibility of fake players and may have unexpected results. I can't change how other plugins handle these NPCs, so probably a good bet if you're getting random PvPLogger files is to change the npc name to "player." That way the player and the NPC will share the same files.

Known Incompatibilities:

  • Heroes in both instakill and NPC mode - No duplication of items, but players will respawn in their old location with the health they logged out at
  • ModifyWorld - Npcs will not take damage

Please put all bugs and feature requests here:

You must login to post a comment. Don't have an account? Register to get one!

  • Avatar of Techcable Techcable Apr 17, 2015 at 18:10 UTC - 0 likes

    Combat Tag now has an irc channel: #techcable on spigot irc network. Combat Tag source has moved to here in preparation for the rewrite.


  • Avatar of Techcable Techcable Apr 15, 2015 at 20:54 UTC - 0 likes

    @Outfenced has approved a rewrite.
    Get ready for a ton of new features.

  • Avatar of danielfr789 danielfr789 Apr 08, 2015 at 23:03 UTC - 0 likes

    You should add an option in the config that extends the npc despawn time when they are hit.

  • Avatar of Techcable Techcable Mar 31, 2015 at 14:41 UTC - 0 likes

    @hobovirginity: Go

    Please file an issue at the issue tracker. It makes my life a lot easier.

  • Avatar of hobovirginity hobovirginity Mar 30, 2015 at 22:17 UTC - 0 likes

    @Techcable: Go

    so negating the permissions works for my owners thanks so much :), actually it all works except when I enable mobTag to true, hitting a mob or getting hit by one wont tag you.

  • Avatar of hobovirginity hobovirginity Mar 30, 2015 at 15:20 UTC - 0 likes

    @Techcable: Go

    Thanks for being so quick in responding and helping me as this plugin perfectly fits my servers pvp needs. I'm at work now but when I get home I'll update my permissions and groups and let you know how it all works.

  • Avatar of Techcable Techcable Mar 30, 2015 at 15:18 UTC - 0 likes

    @hobovirginity: Go

    Yes you should

  • Avatar of hobovirginity hobovirginity Mar 30, 2015 at 15:15 UTC - 0 likes

    @Techcable: Go

    Ok Ill de op everyone and just make my staff members in the owners group as well. But shouldn't negating the combat tag permissions come before the * permission as pex reads from top to bottom?

    Last edited Mar 30, 2015 by hobovirginity
  • Avatar of Techcable Techcable Mar 30, 2015 at 00:23 UTC - 0 likes

    @hobovirginity: Go

    Op shouldn't be used with permission plugins. Permission plugins allow very fine grained control over the permissions you give your staff. Groups are a far better alternative. See my permissionsex config. Specifically the bottom part near the owner.

  • Avatar of hobovirginity hobovirginity Mar 29, 2015 at 13:22 UTC - 0 likes

    @Techcable: Go

    And then negate the permissions for each individual op account as well? Also I negate by typing

    - -combattag.ignore

    - -combattag.ignore.pvplog

    In my pex permissions file correct?

    Last edited Mar 29, 2015 by hobovirginity


Date created
Sep 25, 2011
Last update
Mar 24, 2015
Development stage
  • enUS
Curse link
Combat Tag
Recent files