AntiLog
Tired of players leaving the server while in combat? Then this plugin is for you!
Introduction
When a player is hit by another (or a mob, customisable), he gets tagged for 10 seconds (customisable). While tagged players can't use commands and if they leave the server they'll die. This plugin is really simple and lightweight.
Features
- Stop players from combat logging
- Prevent players from using commands while tagged
- Configurable allowed commands
- Configurable tag time
- Optional configured message when someone logs
- All messages can be customised
- Optionally disable tagging in some worlds
- Exempt permission (antilog.exempt)
- Customise if you want players to be tagged my mobs, players or both
- Untags player on death
- Optional setting to bypass other plugins pvp cancelling if player being hit is tagged
- Simple and lightweight
Installation
Simply drag and drop the plugin jar in your plugins folder and restart/reload and you're good to go! The plugin comes with a config if you then want to customise everything.
Configuration
Please check this page for configuration help.
Feature requests
Suggest features you would like to see added in the comments!
To-do list
Make tag time configurableOption to tag mobsConfigurable optional message to broadcast when someone logsTag exempt permission node
See the plugin in action
If you want to see how the plugin works you can login to my network (IP: play.nostrumcraft.com) and get on the pvp or the survival server (they both have it).
@LilOu1227
It shouldn't conflict at all, since the other plugin doesn't access antilog's config file nor does antilog access the other plugin's. Please create a support ticked with the errors you're getting.
There is a way to change <player>? as a <victim> or something? I have another plugin that uses <player> and throw errors to the console :/
@PCM_Tazmaik
Simply set blockCommands to true and allowedCommands: [] to make it so no commands are allowed at all
@PhilipsNostrum
Yes ! And only the "allowedCmds" is possible !
@PCM_Tazmaik
So basically block all commands while tagged? So they can only chat?
It's possible to change how blockCommands work ? Because I want to allow my player to speak but only speak so just desactivate the "/" !
Thanks :)
@PhilipsNostrum
GG ! :p
New file (AntiLog v1.6.1) uploaded. Changelog:
@PCM_Tazmaik
@PCM_Tazmaik
Snap :/ uploading new file now.
Problem with config, in your plugin, Line 29 of Settings.java:
You said "boradcast"
thank you for your speed
New file (AntiLog v1.6) uploaded. Changelog:
@Tintin159
World support is added in this version
@Tintin159
Hi. The first suggestion is already possible. Simply set "blockCommands" to true in your config and don't add anything to "allowedCmds" (leave it "allowedCmds: []"). I'll work on world support soon. Thanks for the suggestions and for using my plugin ;)
Hello
would it be possible to add two options
1- Disabled all commands during Combat.
2- List the worlds you want disabled under Worlds.
thank you
New file uploaded. Changelog:
Thanks to @jrd3044 and @TheExceed for reporting the allowed commands bug. This version works for 1.7.5 to 1.7.10
New file uploaded. Changelog:
New file uploaded. Fixes startup bug. Thanks to @LegendayAdmin for reporting it
@LegendaryAdmin
Can you please make a ticket (http://dev.bukkit.org/bukkit-plugins/antilog/tickets/)? Thanks
I would like to try this out, but it is giving me this error:
http://pastie.org/9117123
Thoughts?
@HddnNinja
New upate, waiting for approval. sorry for the delay, my computer was broken.
Changelog: