Anti-Relog

Now 1.5.2 fully functional! Download version 2.5 here!
Special thanks for Swifteh for keeping the plugin updated when I wasn't here!
New Features of Version 2.x.x
- Cleaner code.
- NPCs with option for aggressive combat mode. (or assign permission nodes for individual use see below)
- NPCs are compatible with Modifyworld
- Configuration messages now support colors.
- Customized option to drop items, armor, and experience (each handled separately).
- Commands can be run from the console when a combat logger is unbanned and logs back on.
- Fixed issue with MobCatcher.
- Automatic update notifications to the console.
What is Anti-Relog?
Anti-Relog is a lightweight and easy-to-use PVP plugin that prevents players from using commands during combat to escape from the opponent. With this plugin, players will not be able to simply warp to safety but will instead be forced to fight to the death. In the case of a player logging off to escape death, they will be killed instantly* before log-off and their items will drop as usual. If NPCs are enabled, an NPC will spawn in place of the combat logger. They will automatically be banned for a preset time to prevent them from logging on immediately. I made this plugin in response to a plugin request.
What Are This Plugin's Features?
This plugin is designed to be as flexible as possible with the server owner in mind. Below are the current list of features:
- Easy to install. Just drag and drop.
- Keeps players fighting and on the alert. No more escaping from battles.
- Players who log off before the battle ends are logged into a text file with time and date.
- Detects cause of player logoff so they are not banned if their client crashes in the midst of battle.
- Customizable messages and settings.
- Functions are togglable. This means that you can turn the settings off whenever you don't need them!
- PermissionsEx support.
- NPCs compatible with Modifyworld.
How to Install
- Download the latest build of Anti-Relog here.
- Download the latest CraftBukkit recommended build.
- Drag Anti-Relog.jar into the CraftBukkit plugins folder and start up the server.
- Configure the config.yml inside the generated Anti-Relog folder to your preferences and save.
- Reload the server.
Commands
Alias for /antirelog is /ar.
- /antirelog - Shows the plugin version.
- /antirelog t (or /antirelog time) - Shows the time left before player can use commands.
- /antirelog unban <player> - Unbans the selected player if they were banned through PVP logging.
Permissions
Nodes:
- antirelog.pvpbypass - Allows user to be exempt from all PVP restrictions. Allows use of commands in PVP and allows logging off without consequence.
- antirelog.unban - Allows user to unban players who were banned by PVP logging.
- antirelog.aggressivenpc - User will spawn a NPC which will fight the attacker in place of the player when the player combat logs.
NPCs
NPCs are designed to help prevent combat loggers from ruining the fun of PvP by continuing the fight after they log off. Regular NPCs (default ones) do not fight back but instead stay they and get killed. If you really want a challenge, turn the Aggressive Mode on in the config or give players who you want to spawn aggressive NPCs the 'antirelog.aggressivenpc' permission node. NPCs will drop all the player's items when killed and the player will lose all their items upon logging back on. If an aggressive NPC manages to kill the attacker, the combat logger will maintain their inventory and the NPC will despawn.
Configuration
Although there is already information about each config node embedded in the configuration file, below are links to more information regarding the config file:
Change Log:
Version 1.0:
- Release.
Version 1.1:
- Major bug fixes.
- Added more flexible options to toggle different functions.
- EXP and equipped armor will now drop if player logs off during PVP.
- Added custom ban messages that will be shown to the player.
- If server reloads when the player is still banned, instead of leaving the player as banned, the server will unban the player.
Version 1.2:
- Fixed compatibility issues with Factions, WorldGuard, Towny, and any Safe-Zones.
- Players will not be tagged if fighting against NPCs.
- Differentiates between client crash and intentional logout. Players don't get banned when they crash!
- Minor bug fixes and performance improvements.
Version 1.3
- Emergency Release.
- Completely changed the code around using a new method of tracking PVP which is 99% glitch free.
- No more glitching during PVP.
- Fixed permissions issues.
- Allows players to see the remaining combat duration using /ar t or /ar time.
- Fixed major issues regarding Citizens and Factions.
Version 1.4
- Added fix for some cases where players are able to PVP log without penalty.
- Added support for Heroes plugin.
- Added support for banning on servers in offline mode.
- Added command for unbanning players who were banned by PVP logging (regular unbans do not work!).
- Added option for PVP logging against Mobs (agressive/passive).
- Added option to toggle the killing of the player if they PVP log.
- Added ability for server owners to choose which commands they want to disable during PVP (allowing use of spells/PVP commands).
- Added ability to toggle the disabling of commands during PVP.
- Added ability to toggle all commands off during PVP.
- Plugin will now write the reason for the player's unban in the PVP log file.
Version 1.5
- Critical bug fix with /f home.
- Fixed error messages regarding mob logger as well as implementing full functionality for passive mob logger.
- Sends a customizable message notifying players when they are/are not in combat.
- Added alias /arl for plugin conflicts.
- Fixed exploit of directly closing the client window to bypass PVP logging.
- Use <player> in config field: TempBanMessage to signify which player PVP logged.
- Fixed command issue with /unban for servers in offline mode.
Version 1.6
- Removed spam due to forgotten debug lines.
Version 2.0
- Completely recoded plugin from the ground up.
- Cleaner and more efficient code to prevent memory leaks and leave more resources for other plugins to run on.
- Added NPCs that spawn when a player combat logs.
- NPCs have basic combat AI in aggressive mode (which can be toggled in the config or be allowed through a permission node see above).
- NPCs are compatiable with Modifyworld.
- Cleaner and organized configuration format for ease of use.
- Custom messages now support color.
- Added option to run commands from the console when a combat logger logs back on once they are unbanned.
- Added option to choose whether to drop the player's inventory, armor, or exp.
- Fixed issue with items not dropping.
- Automatic update notifications to the console when a new version is available.
- Fixed issue with MobCatcher.
Version 2.1
- 1.4.5 Update. by swifteh @ www.mc-index.com
Version 2.2
- 1.4.6 Update by swifteh.
Version 2.3
- 1.4.7 Update by swifteh.
Version 2.4
- Updated for 1.5.1.
- NPCs are now fully functional.
- Kicked players will no longer be penalized for logging out.
- Fixed a minor bug with the disallow-all function.
Version 2.5
- Updated for 1.5.2.
- Added a command whitelist.
- Players cannot escape from PVP by flying.
- Fixed bug with NPC spawning.
- Fixed bug with mob logger.
To Do List
Add option to have certain allowed commands while in PVP (customizable via config.yml).- Add commands to change config in-game.
- Add options to specify worlds to enable in.
Add support for other permission plugins.Make an optional option to warp banned players to a certain location after they are unbanned.Clean up code.- Make a video tutorial.
Test the plugin and try to find plugin conflicts.Resolve conflict with Citizens and Factions.Add economy support.- Add region support.
- If player logs off in PVP, make the plugin wait a certain time before banning them.
Option to allow an NPC to spawn instead of death.

-
View User Profile
-
Send Message
Posted Jul 12, 2012Since the latest release this seems to be spamming my console with numbers and stuff
-
View User Profile
-
Send Message
Posted Jul 3, 2012so this won't go to well with heroes will it? That with typing /spell [spellname] to cast a spell and getting banned... right?
-
View User Profile
-
Send Message
Posted Jul 3, 2012@Tobseb
Same thing here, guess he forgot to delete a debug line or something?
-
View User Profile
-
Send Message
Posted Jul 3, 2012How do i fix the snowball problem? It doesn't do damage anymore, as in hitting the target with a knockback, it just hits em and does nothing...
Thanks!
-
View User Profile
-
Send Message
Posted Jul 2, 2012I am the Owner of a big PvP-Server and we also use this plugin ... but with the last update this plugin is spamming my whole console and logs ...
I think if any player damages another it counts every stroke...
This is kind of annoying! Please fix! :) ..
Or is it my mistake? xD
-
View User Profile
-
Send Message
Posted Jul 1, 2012I can't find a ticket page so I'll just post this here about how to fix my conflict issue :)
"His source was on github and I found the problem.
Tell him on line 51 of his damageListener class, he's cancelling all EntityDamageEvents that have damage less than or equal to 0. This would include any eggs that are thrown, because they don't do damage.
event.getDamage() <= 0 && event.getCause() != DamageCause.CUSTOM
I'm not sure what the purpose of this if statement is, since cancelling damage events that don't do damage is completely pointless. But regardless, this is what he needs to fix."
-Malikk65 (Dev of Mobcatcher plugin)
-
View User Profile
-
Send Message
Posted Jun 30, 2012Hi I love this plugin, and it works 100%, but I believe it conflicts with the Mobcatcher plugin unfortunately which is also used on my server. D:
What conflicts is that when I throw an egg at a mob to capture it, the egg goes directly through the mob/animal and doesn't even hurt it at all, nor capturing it. I do not know how to reproduce this bug but once I deleted Anti-Relog to test if that mobcatcher feature works, it worked. Once I put it back, it stopped working. I still use both of these plugins and would appreciate it if you can get a fix out eventually. Thanks!
(Here's a link to the other plugin http://dev.bukkit.org/server-mods/mobcatcher/)
-
View User Profile
-
Send Message
Posted Jun 25, 2012worka 100% :D
-
View User Profile
-
Send Message
Posted Jun 24, 2012@DrDewman
What did you type as the arguments? Something like /antirelog unban <player>?
-
View User Profile
-
Send Message
Posted Jun 24, 2012@levisn1
@nhoclesnar
@Curtis4321
@Jordan0510
@Tr0n1x
@Sapd
Ok guys. Sorry about the delay but I managed to release version 1.5. Had to retrieve files from github because of some technical difficulties but all is good now. File is still pending approval so you can go here to get a early copy. http://dev.bukkit.org/server-mods/anti-relog/files/11-anti-relog-v1-5/ This release, of course, includes the critical /f home fix.
-
View User Profile
-
Send Message
Posted Jun 22, 2012Hey there, i did everything as you said, but it simply doesn't works... Nothing happens when someone log out, the plugin is installed but nothing happens at all. Help please?
-
View User Profile
-
Send Message
Posted Jun 22, 2012Hello.
Whenever I use /antirelog or /antirelog unban I get the following error:
2012-06-22 21:49:20 [SEVERE] null org.bukkit.command.CommandException: Unhandled exception executing command 'antirelog' in plugin AntiRelog v1.4.0 at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42) at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:166) at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:479) at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:821) at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:781) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:764) at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:106) at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:34) at net.minecraft.server.NetworkManager.b(NetworkManager.java:229) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:113) at org.getspout.spout.SpoutNetServerHandler.a(SpoutNetServerHandler.java:172) at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:78) at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:567) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:459) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492) Caused by: java.lang.ArrayIndexOutOfBoundsException: 1 at com.github.r0306.antirelog.Executor.onCommand(Executor.java:124) at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40) ... 14 more
-
View User Profile
-
Send Message
Posted Jun 19, 2012FWIW, CombatTag does a job similar to this.
-
View User Profile
-
Send Message
Posted Jun 19, 2012@nhoclesnar
yea you right..i quote nhoclenar..
-
View User Profile
-
Send Message
Posted Jun 19, 2012when ready new version? i have lost a lot of user couse many people use /f home bug<sub> :(</sub>
-
View User Profile
-
Send Message
Posted Jun 17, 2012@r0306
Thanks. One more request tho. I prefer a configurable message to be shown right when a player enter combat. This message should be telling them something like 'You have entered combat, run away and you will get banned.' and it's even better if there is another message shown when combat is over, so that they know they can log off. This other message should be something like 'The battle is over, you can now relax your muscle.'
This is a problem on my server because when two players are fighting, after one player kills other player, he thinks he is safe and therefore logs off right after. The plugin 'thinks' he is PVP logging and tries to ban him. He ends up being very mad losing his items and banned for 5 minutes. I hope you will take my suggestions. Good work making this plugin :)
-
View User Profile
-
Send Message
Posted Jun 17, 2012I was thinking, instead of the antireload t command, how about notifying the player when they are in combat, This way they will know when they can and cannot do commands
-
View User Profile
-
Send Message
Posted Jun 16, 2012It's very important bug report! Players are able to PVP log without penalty with simple closing the launcher's window (by Alt+F4 or close button at top right corner of window). Anti-Relog v1.4, CB 1.2.5-R2.0
-
View User Profile
-
Send Message
Posted Jun 14, 2012@nhoclesnar
Sure. I'll do <player>.
-
View User Profile
-
Send Message
Posted Jun 14, 2012@r0306
That's great. Can you add a variable for the config file? I want to use %player to tell who is punished for pvp logging.