AutoKick
AutoKick
AutoKick 1.7.2 Now Available
AutoKick is a plugin that allows you to effectively shut down your server to all users except OPs and those with "autokick.nokick" permission. If you have to bring your server down for any reason (e.g. editing the map or testing plugins), you can enable AutoKick and it will kick ALL players except OPs and those with "autokick.nokick". It also blocks the kicked users from logging back into the server but allows everyone else to join and leave freely
How to use:
- Type /autokick list [page] - to see all messages with ID's
- Type /autokick enable <ID> - <ID> is the message id seen on the autokick list.
- If timer is greater than 0 AutoKick will run after that time
- All users will be notified.
- Only OP's and those with 'autokick.nokick' will be allowed to log into the server.
- To disable, type /autokick disable
- To change the current message type /autokick change <ID>
- AutoKick is persistent across reloads, meaning that if AutoKick is enabled before a reload it will be enabled after the reload
- Add new messages within the game using /ak add "message" without quotes
- Delete messages in game by using /ak remove msgid
- Set a new time for the countdown using /ak time (time in seconds) without the brackets
- Force enable AutoKick during a countdown using /ak force
Features:
- bPermissions and PermissionsBukkit Support (Others may work but have not been tested)
- Kicks players whilst server is running. No need for restart for it to take effect (like whitelists)
- Customisable kick messages
- Timer
- In game and server commands
- Persistent across reloads
Settings
Config.yml:
You can change this but the plugin uses this for persistence
- enabled=false Message in use when the plugin/server was last reloaded
- lastUsed=0
- timer=30 - Timer is in seconds
- messages:
- - Server undergoing maintenance
- - Map cleanup in progress
- branding: true Choose whether or not to display "AutoKick" before kick messages
You can have as many messages as you like.
Permissions
- autokick.nokick - Gives player immunity from AutoKick
- autokick.list - Allows user to view available AutoKick Messages
- autokick.enable - Allows user to enable AutoKick
- autokick.disable - Allows user to disable AutoKick
- autokick.change - Allows user to change the current AutoKick message
- autokick.status - Displays the current status of AutoKick
- autokick.set.add - Add a message
- autokick.set.remove - Remove a message
- autokick.time - Set a new time
- autokick.force - Force enable AutoKick
- autokick.* - Gives player access to all of the above
Download (1.7.2)
How to use external scripts
Can you please update this to the recent build of Bukkit (1.7.2)?
@Marium0505
update it to what? 1.7.5?
@AryamanSee
download it
How do i get mc 1.7.2?
Can you update this plugin, please? :)
Is it possible to fix MOTD message? =) http://dev.bukkit.org/bukkit-plugins/autokick/?page=2#c22
@Roytjuh99
its working on 1.5.1-R0.1 so...
Could you please update this plugin? I use it many times and it doesn't work for CB 1.5.1-R0.2 :(
would it be possible for you to set it to autokick all players without the permission after a set amount of time, so for example every six hours it would run without needing to use the command?
@Gyldenglad I'll look into this for the next version.
@Roytjuh99 That appears to be a problem with the java version you're using. I build against Java 7. Are you using an older version?
@Outlaw11A That has been added to the next version which will be available soon.
@thekris1234
Can you please disable the "[AutoKick]: is disabled" message in chat when a player is joining? Maybe make an option in config?
Wenn I start my server with Autokick, it wil give an error. My server is a 1.4.7-R0.1. It gave the same error in 1.4.6-R0.1. What can be the problem?
Error code:
2013-01-21 18:08:15 [SEVERE] Could not load 'plugins\AutoKick.jar' in folder 'plugins'
org.bukkit.plugin.InvalidPluginException: java.lang.UnsupportedClassVersionError: net/kdmdesign/autokick/AutoKick : Unsupported major.minor version 51.0
at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:184)
at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:305)
at org.bukkit.plugin.SimplePluginManager.loadPlugins(SimplePluginManager.java:230)
at org.bukkit.craftbukkit.v1_4_5.CraftServer.loadPlugins(CraftServer.java:229)
at org.bukkit.craftbukkit.v1_4_5.CraftServer.reload(CraftServer.java:579)
at org.bukkit.Bukkit.reload(Bukkit.java:184)
at org.bukkit.command.defaults.ReloadCommand.execute(ReloadCommand.java:23)
at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:186)
at org.bukkit.craftbukkit.v1_4_5.CraftServer.dispatchCommand(CraftServer.java:504)
at org.bukkit.craftbukkit.v1_4_5.CraftServer.dispatchServerCommand(CraftServer.java:496)
at net.minecraft.server.v1_4_5.DedicatedServer.al(DedicatedServer.java:258)
at net.minecraft.server.v1_4_5.DedicatedServer.r(DedicatedServer.java:223)
at net.minecraft.server.v1_4_5.MinecraftServer.q(MinecraftServer.java:493)
at net.minecraft.server.v1_4_5.MinecraftServer.run(MinecraftServer.java:426)
at net.minecraft.server.v1_4_5.ThreadServerApplication.run(SourceFile:856)
Caused by: java.lang.UnsupportedClassVersionError: net/kdmdesign/autokick/AutoKick : Unsupported major.minor version 51.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(Unknown Source)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$000(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at org.bukkit.plugin.java.PluginClassLoader.findClass0(PluginClassLoader.java:80)
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:53)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:173)
... 14 more
PS. Excuse me for my bad English.
I'm investigating chunk leakage on my server.
It's 80 slot and usually full, its got 16k chunks loaded usually, however lately theres been about 30k chunks even in maintenance mode (autokick mode) - when someone tries to join and then get kicked, every unique player that it kicks it adds about 400-600 chunks, I can only assume that it's because the server registers the player then loads the chunks before it kicks them, however it doesn't happen with whitelist.
I hope this will get fixed, it's nice to have a customized maintenance message.
@x22Cheats
Tested everything with 1.4.6-R0.3, no errors found. If you're getting errors please post a ticket.
Please update the plugin for 1.4.6 it is very important for me ;)
@thekris1234
No. The problem is this message "[AutoKick]: is disabled" in chat on every player chatscreen when the player join's the server (like MOTD, welcome message). And we don't want to see this notification = it should be disableable in config.
screenshot of notification on beginning of chat, first row: http://img3.fotos-hochladen.net/uploads/20121212011emq1u4x897.png
@Kartus
By default the plugin shouldn't show "x has joined the game" or "x has left the game", is that the message you're getting?
Can you please add a config toggle like "status-login-notification: false" for "AutoKick is disabled" notification on login in chat?
Cause it's spammy/disturbing our server ;)
@Kartus
Dam, thanks for that.
Thank you for update. Small Issue: on /autokick status when an autokick timer is on, in the chat output message, it needs 1 space between the time counter and a word. you will see what i mean ;)