Combat Tag
This plugin is unsupported!!! Use CombatTagPlus instead.
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: http://www.youtube.com/watch?v=g4G5MZmHA9A
Video tutorial espaƱol: http://www.youtube.com/watch?v=EXLi4vgJ-uc
Video Tutorial italiano: https://www.youtube.com/watch?v=kVixSdjBXvw
Features:
- 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:
http://dev.bukkit.org/server-mods/combat-tag/pages/setup/
Config:
Explanation of the config file options:
http://dev.bukkit.org/server-mods/combat-tag/pages/config-file/
Commands:
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
Permissions:
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
Source:
https://github.com/TechzoneMC/CombatTagLegacy/
Problems:
If you have any bugs or feature requests, go here!:
https://github.com/TechzoneMC/CombatTagLegacy/issues
API:
If you wish to use the Combat Tag API:
http://dev.bukkit.org/server-mods/combat-tag/pages/using-the-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
https://github.com/TechzoneMC/CombatTagLegacy/wiki/Feature-ComparisonFeature Comparison
thanks :)
I've made a new extention to combat tag that creates a shield around spawn that combattag players can't go through. Unlike other plugins this one has almost no lag.
@PortGasMC
I'll look into it.
Yes my server is on offlinemode
Is it just me, or am i awesome?
This requires no dependencies.
All you have to do is download the latest build. Then set tagDisplayMode to "mobBar".
@PortGasMC
Are you on offline mode?
Help? In my server have this plugins 1.8 spigot not 1.8.3 ProtocolLib 1.8 update Citezen latest Sentries latest builds
It always spamming my console http://pastebin.com/MhzzWBiV
@Techcable
Honestly, no idea what specifically the cause was. All I know is NPCs would not take damage if the plugin was enabled.
@cheddar262
What made it incompatible with ModifyWorld last time?
EDIT 1: Made a thing that allows patching code at runtime: https://github.com/TechzoneMC/CBPatcher
To be honest, I am unsure if the new version of combat tag is incompatible. It was only incompatible with the NPCs, last time I checked with Combat Tag. @Techcable , do you know if the new NPCLib is compatible with ModifyWorld?
Incompatibly with ModifyWorld???
What?
That makes it almost worthless to me :'(
Combat Tag now has an irc channel: #techcable on spigot irc network. Combat Tag source has moved to here in preparation for the rewrite.
@Outfenced has approved a rewrite.
Get ready for a ton of new features.
You should add an option in the config that extends the npc despawn time when they are hit.
@hobovirginity
Please file an issue at the issue tracker. It makes my life a lot easier.
@Techcable
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.
@Techcable
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.
@hobovirginity
Yes you should
@Techcable
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?
@hobovirginity
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.
@Techcable
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?