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.
@r0306
Lol, i saw that. I just edited the URL and got an early copy :) Awesome update, thanks man.
Also, im told that /f home is affected by this- its instant, despite my config, and can be used in combat. If you could add that, thatd be awesome. Oh, and unblock /tpahere, since thats not fleeing, right?
Differentiates between client crash and intentional logout. Players don't get banned when they crash!
I think there is a problem here. When a player close Minecraft via clicking the X button, isn't that counted as client crash? I think the only case that can be defined as crash here is when the server suddenly crash.
@Mick6666
Lol. I did upload it. I'm just waiting for a moderator to approve it so that it will show up. As for the command, I will see what I can do about that. If you have any other ideas, feel free to post them as well.
Suggestion- add a config option for allowed commands? Like tpaccept.
Also: can you upload the jar already? Im sitting here refreshing..
@Toxic__Waste
I think I fixed the bugs in the newest 1.2 release so check it out. Be sure to erase your old config file before loading. In this new update, I also added compatibility with Factions and safe-zones.
Thanks bro But I got my own custom one developed :(
i had to remove the plug in yes using 1.1 it would happen when a plyer would pvp alot or get hit alot if it was one battle i had no problems but for the active back and forth pvpers they were getting pissed at me they couldnt get back to the fight even after they log out and in actually had to restart the server so they could tp but like i said when it was one battle and some won died the winner was able to tp out after the 7 seconds i left it at default then tried other times never sent errors either I also checked it i would have some won hit me and hit them and i wait i was able to tp out after the time
so I guess real active pvpers who who get hit alot
also i use the towny system where pvp is not legal in towns or allowed by perms and it would not let no one tp out even on a fake hit meaning they hit but no damage so I had them following each other fake hitting so the other player couldnt leave since they lose there stuff upon log out no one was able top log out they were scared they lose all there stuff looool
@Toxic__Waste
Have you updated the plugin to 1.1? If not, then you should update it here: http://dev.bukkit.org/server-mods/anti-relog/files/4-anti-relog-v1-1/. Otherwise, can you provide some more detail about the frequency that this happens? I have just tried it on my server for 10 seconds and it works. Maybe the server reloaded all of a sudden or a plugin conflict occurred. If you are still having this problem, send me a message.
i set the tp out for 10 seconds and they cant tp even after a minute plz help this plug in is great
@Mick6666
That's strange, I tested it and it seemed to work out fine. Maybe I was using an older version of WorldGuard. I'll look into this as well.
In a WG zone with the no-pvp flag on, the plugin still acts as if its in real combat.
Confirmed with the latest version.
@erdrickk
Thanks for reporting this issue, I will look into it as soon as possible.
@nhoclesnar
No, as of now, it does not. However, I can add that feature in in later updates.
Little issue: If you are using Citizens and you hit an npc, it flags you as PVP. Is there a way to not include NPC's ?
Does this plugin work when you are fighting with mobs?
@rasnyderiii
If you go into the config.yml folder in AntiRelog, you will see a section labeled StunDuration. The default is set to 7 seconds whenever a player hits another player. You can change that to whatever you want. As for notifying players when they are/aren't in combat, that would cause huge spam and server lag on larger servers and it's not very accurate either as you could be hit anytime. If you want to let your players know how long it is that you are/are not in combat, simply broadcast it or post the duration you set on a sign so they are aware of this. Otherwise, the only known compatibility issue right now is with Factions and I'm trying to find a way to fix it.
Can anyone give solid feedback on this plugin for a large server? Works good overall with just the few problems mentioned below?
How long is someone marked in combat until it resets as no longer in combat? How do you know when you are "no longer in combat"?
Safe Zone "smacking" other players then that player logs out kills them? That is a deal breaker right there...
Any compatibility problems with towny noted yet?
The alternative to this already uses NPCs and it is horribly glitchy...
Okay, just ignore my ban message rambling :)
I swear we were having issues at spawn with this. No factions, just WG. Ill try an update.
@Mick6666
As of now, the only plugin I'm worrying about is Factions as I've tested WorldGuard and nothing goes wrong. I don't know what you're talking about for the ban message. I already added the ability to display a custom ban message when the player is banned for logging.
@r0306
A much bigger priority is the safe zone/no pvp WG regions. Its the only and biggest downside so far.
Oh, and for the customizable ban message, no idea how it bans, but maybe put text after the player? Assuming it bans in a format like: ban (player) (message). Where player is the combat logger and message is the field in the config.
Im no coder, but it shouldnt conflict.