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
-
View User Profile
-
Send Message
Posted Aug 6, 2012I've gotten enough updated for a release for the 1.3.1 dev. If you want it, there will still be all the old bugs plus probably some new ones. Also, if you like npcs showing the skin of the player by setting their name only to player, I've had to do a workaround that disables that and will change the format of people's names. In any case, enjoy Combat Tag v4.8.5 when it is shown in the files you can download. If you find any major bugs besides the ones currently posted in tickets, please make a ticket for them.
I can't stress enough: I will not be taking bugs, errors, or features from the comments.
-
View User Profile
-
Send Message
Posted Aug 5, 2012i agree, we love and miss you :(
But you didn't have to cut me off Make out like it never happened
-
View User Profile
-
Send Message
Posted Aug 4, 2012Please Update! All your work is appreciated! Keep it going :)
-
View User Profile
-
Send Message
Posted Aug 4, 2012@Sk8Sanctified
Hm that's odd...
I'm still getting severe spikes of lag and extremely low tickrate.. 7 - 15 seconds of lag, and 2 TPS... (I try every new dev bukkit that comes out, and Spigot.)
It has a progressiveness to it, gets worse with more player+time... I hope they can fix this soon.
-
View User Profile
-
Send Message
Posted Aug 4, 2012Dont working in 1.3.1 =(
-
View User Profile
-
Send Message
Posted Aug 3, 2012@lazertester
That would be quite helpful. I've modified it mostly, but I must've missed something because npcs I spawn don't show to a player until the player relogs.
-
View User Profile
-
Send Message
Posted Aug 3, 2012@cheddar262
I've updated TopCat's NPC Library to work with 1.3 for our Antilogger plugin we use, I will post my fork on git soon, I figure that would help you along :)
https://github.com/eatmybiglazer/NPCLib if you want to grab it.
-
View User Profile
-
Send Message
Posted Aug 3, 2012@joannou1
It's was actually a bukkit bug with any version below 2279. The entity tick processing was a little buggy so any plugin that relied on it heavily, like Towny does to remove mobs in towns. Your server would lag. In bukkit version 2279 Mike has a fix for this.
-
View User Profile
-
Send Message
Posted Aug 3, 2012@cheddar262
Are you struggling with the PrivateKey on the NetworkManager constructor? That's what I cannot figure out for the life of me!
-
View User Profile
-
Send Message
Posted Aug 3, 2012Hey, Awesome plugin and i hope the updating is going well. I will keep checking back for updates on the plugin and cant wait to use it on my server when its updated for 1.3.1 Great job man! Thanks CackleFish
-
View User Profile
-
Send Message
Posted Aug 3, 2012@Sk8Sanctified
It's really Towny? I have it and I'm getting severe spikes (10 seconds sometimes). I talked to ElgarL on the IRC, and he said the plugin didn't need any updates really.
-
View User Profile
-
Send Message
Posted Aug 3, 2012@cheddar262
I apologize I was a dick :/ because I was kinda. Thanks for letting us now whats going on, I started to feel your pain too, after searching through my plugins trying to figure out which one was causing lagspikes, I found it was towny, but the later on realized it was a confliction with the entity tick processing of dev bukkit and towny.
Anyways, keep up the good work! Your plugin eliminated whining children that experienced a combat logger, as well as eliminating the whining combat loggers explaining why they shouldn't be banned. Da Best!
-
View User Profile
-
Send Message
Posted Aug 3, 2012@cheddar262
I can send you the source code I have if you want? (Im not familiar with git)
It includes a hacky fix or two, but everything works as it should :)
Edit: I'll send you a link to the source, hopefully it helps you out in some way.
-
View User Profile
-
Send Message
Posted Aug 2, 2012@cheddar262
Hm, I'm not a part of this conversation, but I understand what you have to deal with. Luckily I only use the Insta kill part of the plugin! So a basic dev build that has that function would be awesome.
Thanks!
-
View User Profile
-
Send Message
Posted Aug 2, 2012@Sk8Sanctified
What you don't realize is Combat Tag breaks in at least 5 different ways every minecraft update. This causes the plugin to be rendered unusable. It has happened especially in this update. So far, I have worked 8 hours scouring through the bukkit source code for everything I need for the update.
The version on the files for Combat Tag do not say for 1.3.1. Do they? That means the version of Combat Tag you are using will not work most likely. Every update to Minecraft, expect Combat Tag to break. This happens because the obfuscation for minecraft and also the classes and methods that Bukkit uses change drastically. I have to find what replaced what, what does not work anymore, and what to do if something is no longer is in the code.
As things are right now, I could put out a build for Combat Tag. The only problem is you could only do instakill mode. I have npcs able to spawn at this point, but they do not show up until you relog. I'm fairly sure nobody wants that.
-
View User Profile
-
Send Message
Posted Aug 2, 2012@cheddar262
I think the issue is that we ARE relying on the versions in the files and they no longer work with 1.3.
People like to update a.s.a.p even if there using bukkit dev. It's always good to keep an updated dev version for download, those that like to update quickly really appreciate it. :D
-
View User Profile
-
Send Message
Posted Aug 2, 2012To all those who are saying this isn't working with 1.3: I would prefer if you relied on the versions that are on the files.
ShakyTom: If you want, you could make a commit to the github at https://github.com/trc202/Combat-Tag
You can distribute it if you want (as says the License), but I would prefer the commit instead. Also, if there are any bugs with the version ShakyTom has, I am not responsible.
-
View User Profile
-
Send Message
Posted Aug 2, 2012This needs an update, getting tons of errors with it.
-
View User Profile
-
Send Message
Posted Aug 2, 2012I have an (unofficial) build ready that works on 1.3.1 if anyone would like it?
With authors permission of course!
-
View User Profile
-
Send Message
Posted Aug 2, 2012current version is conflicting with authme, users dont have to type /login etc (only on 1.3.1)