CombatLog
CombatLog punishes players who log out in an attempt to escape combat
CombatLog has been updated to v2.3.0! Supports versions 1.7.10+
How effective is CombatLog? Take a look at this graph: http://bit.ly/CL-Graph
Sample config page: https://dev.bukkit.org/bukkit-plugins/combatlog/pages/configuration/
New API usage: https://dev.bukkit.org/bukkit-plugins/combatlog/pages/api/
Features:
- Easy-to-understand configuration file.
- Able to customize messages and disable unwanted features.
- Use /tag or /ct to check tag time.
- Remove players' Combat tags if they disconnect because of lag or if they were kicked.
- Block commands (using a blacklist/whitelist), teleportation, and enderpearls.
- Remove invisibility potions, disguises, or fly mode, upon entering Combat.
- Display CombatTags on an ActionBar.
Permissions:
- combatlog.bypass - Ability to bypass all of CombatLog's log prevention methods. (Default NONE)
- combatlog.reload - Ability to reload combatlog.yml. (Default OP)
- combatlog.update - Ability to see UpdateChecks upon logging in. (Default OP)
Consider donating to support development: http://bit.ly/CL-Donate
I've run into an issue on my server, when players PVP log when they rejoin they are dead, but when they hit respawn they end up in the same location instead of their designated spawn, this typically is an issue with people dying before logout, would it be possible to make it to where users die after logging back in?
http://pastebin.com/kh3bMPtQ
13:24:19 [INFO] This server is running CraftBukkit version git-Bukkit-1.4.6-R0.3-b2586jnks (MC: 1.4.6) (Implementing API version 1.4.6-R0.3)
13:24:41 [INFO] Plugins (33): AntiInvisible, WorldEdit, NoCheatPlus, SimpleFly, Buycraft, ShowHeal, SaveItems, Vault, PermissionsEx, Multiverse-Core, WorldGuard, CasinoSlots, AuthMe, Announcer, WhatIsIt, ClearLag, ProtocolLib, StealthLogin, Dispensator, Essentials, KillsPay, floAuction, AntiCommandTab, EssentialsProtect, ServerSigns, EssentialsSpawn, VanishNoPacket, PluginsBaker, EssentialsAntiBuild, iGates, EssentialsChat, Factions, CombatLog
@ravand
But that's completely giving the the fight to the other player. If a player runs into a SAFEzone, regardless of whether it's a pussy move, s/he should still be protected. Not protecting them would be a double standard.
I nice feature would be for players, who decide to attack others, to ignore pvp spawn protection
Example scenarios:
First case: Player1 and Player2 are in the wilderniss fighting each other->Player1 is a coward and runs towards spawn for pvp protection->Player2 will still be able to hit Player1 and Player1 can also hit Player2.
Second case: Player1 is outside spawn protection and waits for Player2 to come out. Player1 hits Player2 and Player2 decides to run back to spawn for protection->Player1 can still attack Player2 because both of them have been tagged as pvp.
Would be awesome to see this :)
Thanks in advance ravand
@tarahere81
Hm, this has happened before when one my sponsors was using it. I haven't completely been able to get to the bottom of why it's doing this when I implement it the way I did, but I do know a fix and will upload a bug fix version soon.
0.9.7
2013-01-11 15:00:27 [INFO] Strakattack: yes 2013-01-11 15:00:28 [SEVERE] Could not pass event EntityDamageByEntityEvent to CombatLog v0.9.7 org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:427) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462) at org.bukkit.craftbukkit.v1_4_6.event.CraftEventFactory.callEvent(CraftEventFactory.java:81) at org.bukkit.craftbukkit.v1_4_6.event.CraftEventFactory.callEntityDamageEvent(CraftEventFactory.java:369) at org.bukkit.craftbukkit.v1_4_6.event.CraftEventFactory.handleEntityDamageEvent(CraftEventFactory.java:391) at net.minecraft.server.v1_4_6.EntityLiving.damageEntity(EntityLiving.java:686) at net.minecraft.server.v1_4_6.EntityMonster.damageEntity(EntityMonster.java:39) at net.minecraft.server.v1_4_6.EntitySmallFireball.a(EntitySmallFireball.java:28) at net.minecraft.server.v1_4_6.EntityFireball.j_(EntityFireball.java:132) at net.minecraft.server.v1_4_6.World.entityJoinedWorld(World.java:1334) at net.minecraft.server.v1_4_6.WorldServer.entityJoinedWorld(WorldServer.java:548) at net.minecraft.server.v1_4_6.World.playerJoinedWorld(World.java:1315) at net.minecraft.server.v1_4_6.World.tickEntities(World.java:1193) at net.minecraft.server.v1_4_6.WorldServer.tickEntities(WorldServer.java:445) at net.minecraft.server.v1_4_6.MinecraftServer.r(MinecraftServer.java:580) at net.minecraft.server.v1_4_6.DedicatedServer.r(DedicatedServer.java:224) at net.minecraft.server.v1_4_6.MinecraftServer.q(MinecraftServer.java:494) at net.minecraft.server.v1_4_6.MinecraftServer.run(MinecraftServer.java:427) at net.minecraft.server.v1_4_6.ThreadServerApplication.run(SourceFile:849) Caused by: java.lang.NullPointerException at com.jackproehl.combatlog.listeners.EntityDamageByEntityListener.onEntityDamageByEntity(EntityDamageByEntityListener.java:87) at sun.reflect.GeneratedMethodAccessor1787.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:425) ... 20 more
@TheFarmerNL
Godmode was the one thing I wasn't able to fit into 1.9.7. I just had some damning issues with it. I'm going to give it another go in the next update, which may very well be the first final release of CombatLog.
It'll feature CombatTag duration saving on disabling of the plugin, server crash and lag disconnect disconnection, removal of godmode and vanish. On top of it all, I've already made the neatest, best config.yml and messages.properties of all the anti-PVPLogger plugins. I am absolutely in love with how it turned out. And actually, this update will come much quicker than this one.
@BlueberryII
Yes, you can set them to die using the Kill punishment and Drop punishment. Simple set them as "Enabled: true."
I can't wait for the update, I've been waiting for it for 2 endless days :P It looks VERY promising and amazing when I look at the config! You have nearly everything in it (potions, fly, commands etc.). Much better then our current anti combat log plugin and you don't have to spent (or waste) time on NPC's!
Only thing I thought of lately is godmode (essentials). Could you disable that one too?
Really good job you guys did here!
The plugin looks very nice, but I've got two questions: Number 1: Can the player be set to death for logging out in combat and drop the inventory?
Number 2: Does this plugin work with Tekkit Classic without (extreme) laggs?
BlueberryII
@Exagerate
Ah, that is tricky! I would've never thought of /back. Yah, I'm going to add a disable all commands option in that section.
AHA! It's /back that they're using, you should consider making this one of the default blocked commands, it's the most overused way of cheating in combat.
Kind regards,
I'm not sure that the disabled commands works properly, is this a known bug?
@CapBlackShot
No problemo. New update coming soon.
Very thanks for plugin! :)
@xATon2x
Sorry man, it will come, I promise. Just caught up in life and I don't want to rush the plugin. I've also been busy doing some other programming.
@pulsehh
That's because you have to type the teleport command in the disabled list...
Where's the new update?
The disabled commands part of this plugin doesn't work. Allows teleportation while in combat etc.