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 17, 2013@BugsyH
Mobs don't log off
-
View User Profile
-
Send Message
Posted Aug 17, 2013Is it possible to configure this to work with mobs as well?
-
View User Profile
-
Send Message
Posted Aug 16, 2013@laseromich
Ok, I was just making sure. A fix was posted on another plugin and I wanted to test.
-
View User Profile
-
Send Message
Posted Aug 16, 2013@cheddar262
"Possible fix for End of Stream for null error, put into testing"
dont helping
-
View User Profile
-
Send Message
Posted Aug 15, 2013@laseromich
Please submit a ticket again. I'll look into it, I guess.
-
View User Profile
-
Send Message
Posted Aug 15, 2013@chopstick121
It shouldn't
-
View User Profile
-
Send Message
Posted Aug 15, 2013Last MCPC
[SEVERE] Reached end of stream for null
[SEVERE] Reached end of stream for null
[SEVERE] Reached end of stream for null
-
View User Profile
-
Send Message
Posted Aug 15, 2013@cheddar262
I wouldn't worry about bugs in the comments section. People who file worthy bug reports will file them in the correct locations :P Also TYVM for the update! Works Perfectly!
-
View User Profile
-
Send Message
Posted Aug 15, 2013@cheddar262
I wouldn't worry about bugs in the comments section. People who file worthy bug reports will file them in the correct locations :P
-
View User Profile
-
Send Message
Posted Aug 15, 2013if a server restarting will everyone die?
-
View User Profile
-
Send Message
Posted Aug 14, 2013not working .<sub>, </sub>
if i hit someone then he left ... his name became pvplogger 000 and number how to fix that
-
View User Profile
-
Send Message
Posted Aug 13, 2013@laseromich
If a bug is posted in the comments, I can't request more information to fix the issue. The information is kept in one area that I can reference while fixing the problem, so I don't have to search through comments every time.
-
View User Profile
-
Send Message
Posted Aug 13, 2013@cheddar262
why?
-
View User Profile
-
Send Message
Posted Aug 12, 2013@LaughNgamez
Please submit a ticket with your issue... As posted right above the comment box: "Do not post your bugs and feature requests in the comments!"
-
View User Profile
-
Send Message
Posted Aug 12, 2013blocking teleport does not work.
-
View User Profile
-
Send Message
Posted Aug 12, 2013@cheddar262
Updated to Spigot build 1073 and it's working again with 5.9.3, thank you!
-
View User Profile
-
Send Message
Posted Aug 11, 2013@cheddar262
I have never had a problem with spigot & combattag and i can confirm this for the last few hundred versions.
-
View User Profile
-
Send Message
Posted Aug 11, 2013I did some research: Spigot builds released recently (probably 2 days ago or less) should not spam the "Reached end of stream for null" error. It's recommended, if you still wish to use Combat Tag, to update to this version. However, I will be providing support for problems that I can reproduce in craftbukkit only.
-
View User Profile
-
Send Message
Posted Aug 11, 2013For those looking for v5.9.3, it's yet to be approved by bukkit dev staff, even though it was uploaded over a day ago. I will not be posting a direct link to the version because it was edited out by a moderator last time.
-
View User Profile
-
Send Message
Posted Aug 11, 2013@Maroseliss
I have been building off of the beta build #2838. No problems are found from my testing.
The change in my policy of support for Spigot and MCPC is due to a recent change in what appears to be spigot's code deviating from craftbukkit's as of 1.6.2 causing an error that spams the console. As I'm unfamiliar with Spigot, even though it's based off of craftbukkit, I can't provide support for this error.
I can provide support for errors otherwise present that involves the plugin and effects both craftbukkit and Spigot, but I have never gotten the "[SEVERE] Reached end of stream for null" as many people who use Spigot are reporting. If you are not reporting this error, I may not be able to fix your problem, but I will test for it on craftbukkit.