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
@LordKainzo
Ok, will check a couple of things again. Tell me if any different messages come up.
Also, if you know what someone was doing beforehand, it would be much appreciated and help me work this out faster.
@cheddar262
seeing this on latest... http://pastebin.com/CaDz2inh
@FatFreeSMP
It should be called "sendMesssageWhenTagged" If you don't see it, please report as a bug.
@deleted_8460815
This is actually how it's programmed to work right now. Does it despawn when they log back in? If so then that's a bug. Right now I'm working on despawning after a time.
@grimyre
Hey, i know there is a way in the config to disable the f home command if enemy faction players or factions are in a radius of 100 blocks
I have Combat Tag v3.8 installed using 1.1-R4 Craftbukkit.
We are using Factions, and I"m attempting to prevent people from using their faction home command while combat tagged. The two ways to use this command are 'f home' and '/f home'.
I have put into the config this:
disabledCommands=[f home,/f home]
That didn't work. I was still able to use these commands.
I then tried this:
disabledCommands=[f,/f]
That still did not work. Players were still able to use 'f home' or '/f home' to go to their faction home during the combat tag timer.
@cheddar262:
It seems that when a player logs off while tagged, the npc never disappears unless it is killed. Not sure if you were aware of this bug or not.
@Darkhand81
Yes, unless you turn on instaKill which will kill them on log out.
I haven't had a chance to test this yet... Am I correct in assuming that if the player logs back in before he dies, the NPC is removed and he can continue on his way?
Sweet, works perfect now. Great plugin and awesome work. Your plugin has made AntiPVPLogger obsolete, not that it's even updated anymore. Thanks!
Currently uploading CombatTag 3.8
Change Log: Fixed having just "player" as NPC name not working correctly.
Added sendMessageWhenTagged to the config. Sends a message to both players saying they are tagged for combat. Default is false.
Added blockEditWhileTagged to the config. Can place or break blocks while tagged. Default is true.
Seeing this - just dropping it here. http://pastie.org/3412378
@Predatron
Bukkit was the thing that actually changed. I'm working on a workaround for the problem now.
@cheddar262
Ok, I'm glad it's not just me. I know nothing about writing plugins so don't take this the wrong way, but wasn't it done that way before? What is different now? This plugin used to make the npc have the players name and skin, did something change? Overall it's a great plugin and I appreciate the work you and your team put into it. Thanks!
@JoneKone
It works for me. Let me do another test again.
Edit: Works for me...
@Predatron
I'll test this just to make sure of things, but it should still work.
Edit: You are correct. Keep your names away from just player for now. Add something before or after please. The fix will hopefully be in the next update unless it's impossible to fix in which case I'll warn people as such.
Hi, can you add the support of AuthMe? This plugin has done it too: http://forums.bukkit.org/threads/mech-antipvplogger-v-1-1-prevent-players-from-logging-out-1-1ready.48604/ Regards.
02:27:49 [INFO] [CombatTag] Player tagged another player, setting pvp timeout 02:27:51 [INFO] Connection reset 02:27:51 [INFO] JoneKone lost connection: disconnect.quitting
after that nothing... :(
It now registers all events but npc doesn't work.
@cheddar262
True enoughghgfhgh However mob vs player .. In a small server it is you vs the mobs..