[ADMN] AfkBooter v1.0.3 - Boot players that idle too much [1000]

AfkBooter - Boot players who idle too much on your server:
Version: v1.0.3


This plugin is no longer being maintained by neromir. It has been taken on by morganm. Please see the BukkitDev site http://dev.bukkit.org/server-mods/afkbooter/ for the latest version, support, and questions.


Download AfkBooter v1.0.3: jar
Source Code: https://github.com/neromir/AfkBooter

Important Note: If you are upgrading from pre-1.0, take special note of the listened-events property! You must set it or the plugin will not work!

This plugin monitors the last activity time a player has on your server and will boot them if that time longer than a settable idle-allowance.

Current version was tested against CB 1000, 935 and 953. Previous versions will work with CB 860, 818, 803, 798, 766, 740, 733, 677, 670, 617, 556, 531, and 493. Version 0.7.1 and above require 612+ due to interface changes. Version 0.4 requires at least CB 432+ due to the changes with the plugin constructor.

Features:

• Prevent players from idling on your server beyond a given time limit.
• Allows you to set a list of player names who are immune to idle-kicking.
• Allows you to set a player count threshold below which nobody will be kicked.
• Allows you to set a custom kick message for both the kicked player to see and one that is broadcast to all players on the server when the player is kicked.
• Allows you to determine if player idling status should be merely announced rather than having idlers kicked. If set to true, it will be announced when players are no longer idling. The kick broadcast message is used to determine the text of the message announced when a player goes idle.
• Works with any number of people on the server (does not fail when there's only a single person on).
• Allows you to set a kick-check frequency. Rather than arbitrarily set a kick-check interval for you, it allows you to determine what is best for your server.
• Allows you to specify which events, out of a given set, should be listened to for purposes of activity checking.
• Allows you to specify if players should be counted as active while moving in a vehicle.
• Allows you to set whether idlers should be counted as "in bed" for checking if all players are in bed to move the server time forward to day.
• Allows you to set whether idlers should be blocked from picking up items.
• Integrated with Permissions 3.1.6. Should also work fine with Permissions 2.7.3.

To install
Simply put the jar file in your plugins directory for CraftBukkit. On first run it will create a file called "afkbooter.properties" in the directory "plugins/AfkBooter" and populate it with the default settings. You should then stop your server, change the settings to match what you want, and re-run it.

To upgrade

Important Note: If you are upgrading from pre-1.0, take special note of the listened-events property! You must set it or the plugin will not work!

Put the new jar in your plugins directory for CraftBukkit and start the server. Use one of the below-listed commands which changes a value, such as kickTimeout, from inside the server console. You can just reset it to the already-configured value. This will update your settings file to contain all the latest settings. Stop the server, change any of the new settings. Restart and you're good.

The properties file looks like this:

Code:

#Default auto-created config file. Version 1.0.2. Please change.
#kick-timeout is amount of time (sec) players can be idle, kick-message is the message the
#kicked player sees, kick-broadcast is the message all players see when a player is kicked (name + message), 
#timeout-check-interval is the frequency (sec) to check for players to boot, and exempt-players is the list
#of players not to kick at all. player-count-threshold is the number of players that must be present before
#players start getting kicked for idling.  Set to 0 for always. Set use-jump-ignoring to use the experimental
#code which ignores vertical movement for activity purposes. Set kick-idlers to determine whether or not idlers
#should actually be kicked or merely announced. ignore-vehicle-movement if set to true will not consider a player's 
#movement if they are in a vehicle. use-faux-sleep will count AFK players as "sleeping" for the purposes of beds
#moving the clock forward; only works if kick-idlers is false.
#Sun May 8 19:09:36 MST 2011
exempt-players=name1,name2,name3
use-jump-ignoring=false
timeout-check-interval=10
kick-message=Kicked for idling too much.
kick-timeout=30
kick-broadcast=kicked for idling too much.
player-count-threshold=0
kick-idlers=false
ignore-vehicle-movement=false
use-faux-sleep=false
block-idle-items=false
listened-events=PLAYER_MOVE,PLAYER_CHAT,INVENTORY_OPEN

Note that the server broadcast for kick-broadcast will show up as "<kickedPlayerName> <kick-broadcast>". So in this case, it'd be "neromir kicked for idling too much."

Permissions nodes:

Code:

- 'afkbooter.exempt'
- 'afkbooter.config'

Anyone that has the exempt node will not be kicked by the plugin. Anyone that has the config node will have access to all the below-listed commands. Note that the exempt node is in addition to any names listed in the exempt-players list in the settings file. Also note that ops have access to all commands as well, regardless of whether or not they have the config permission.

Commands:

Code:

Example: /afkbooter kickTimeout [number] - Changes the idle time (sec) allowed before players are kicked.
Example: /afkbooter kickMessage [message] - Changes the message a kicked player sees.
Example: /afkbooter kickBroadcast [message] - Changes the message broadcast to all players when someone is kicked.
Example: /afkbooter listExempt - List the players on the exempt list.
Example: /afkbooter addExempt [playerName] - Add a player to the exempt list.
Example: /afkbooter removeExempt [playerName] - Remove a player from the exempt list.
Example: /afkbooter playercount [number] - Set the threshold below which no players will be kicked.
Example: /afkbooter useJumpIgnore [true|false] - Set whether or not to use experimental jump ignoring code.
Example: /afkbooter kickIdlers [true|false] - Set whether or not idlers should be kicked or merely announced as idling.
Example: /afkbooter ignoreVehicles [true|false] - Set whether or not to ignore player movement while in vehicles.
Example: /afkbooter useFauxSleep [true|false] - Set whether or not to use faux sleep (afk players are considered in bed).
Example: /afkbooter blockIdleItems [true|false] - Set whether or not item pickup should be blocked for idlers.
Example: /afkbooter list - List players marked as AFK.

Also note that a player newly added to the exempt list may get kicked for idling if they are in the server when they are added. They should be exempt from tracking once they rejoin the server, however.

A player can be considered active when the plugin catches one of the following events (depending on how you set it):

• Join
• Movement (looking around past a certain threshold, I believe 30 degrees, does count as movement).
• Chat/command
• Opening the inventory (simply holding the inventory open does not trigger this-- only the actual open inventory action does).
• Block placement.
• Block break.
• Dropped item.
• Player interacting with a block.
• Player interacting with an entity.

Event names which can be listed in the listened-events property:

Code:

PLAYER_MOVE
PLAYER_CHAT
PLAYER_COMMAND_PREPROCESS (to detect commands as well as chat)
INVENTORY_OPEN (does not work currently due to Bukkit event issues with inventory)
PLAYER_DROP_ITEM
BLOCK_PLACE
BLOCK_BREAK
PLAYER_INTERACT
PLAYER_ENTITY_INTERACT

Changelog (open) Changelog (close)

Changelog:
Version 1.0.3

• Fixed an exception that was thrown if the "/afkbooter list" command was used while nobody was AFK.

Version 1.0.2

• Added ability to listen to PLAYER_INTERACT and PLAYER_ENTITY_INTERACT events.
• Added /afkbooter list command which will list idle players if kickIdlers=false

Version 1.0.1

• Added a bad formatting check, should catch exceptions when you screw up the listened-events property.

Version 1.0

• Fixed bug which required a restart of the AfkBooter when you changed the kickTimeout. It will now properly detect it when changed while the server is running.
• Added ability to block pick up of items for players which are idling. Note that this only functions when kickIdlers is false.
• Added ability to listen to players' commands in addition to their chat for determining activity status.
• Completely revamped the way that events are listened to for determining activity status in order to allow for easier adding of additional events. You now must list the event names in the listened-events property. Events should be comma separated. For events that can be listened to, please see the list above.

Version 0.9

• Added option to ignore player movement while in a vehicle. Set the ignore-vehicle-movement property to true for this.
• Added ability to set AFK players as "asleep" according to the new Bukkit feature in CB 677. This only works if you have kick-idlers set to false. If use-faux-sleep is set to true, then players who are AFK will be marked as "in bed" for checking if all players are in bed to move the server clock to day.

Version 0.8.1

• Fixed possible NPE through the Permissions plugin. Looks like he's not checking if the Player object passed in to his PermissionHandler.has() method is null or not.

Version 0.8

• Added ability to simply make an announcement of idling status. This is controlled through the kick-idlers property of the properties file to false. Defaults to kick idlers (true).
• Added a check for player online-ness before trying to kick them. Should hopefully help prevent some of the NPEs, since the previous check for player presence was apparently insufficient.
• Changed kick announcement color to yellow.

Version 0.7.1

• Simple changes to method signatures to match the changes in CB 612? (Not sure exactly which version they were introduced). Makes plugin fully compatible with CB 617.

Version 0.7

• Added the ability to determine whether certain events should be listened to. The events which can be listened to currently are:
  Player move
  Open inventory
  Player chat
  Block place
  Block break
  Player drop item.
  
  These are modified by setting one of the "listen-*" settings in the properties file.
  

Version 0.6.1

• Corrected a NullPointerException that was occurring if you were not running the Permissions plugin.

Version 0.6

• Added support for Permissions plugin.
• Added synchronization for the playersToKick list. Seemed like we were getting some log messages that indicated there was some concurrent access happening. This should prevent it while simultaneously not slowing bukkit down much.
• Added some nicer cleanup in onDisable() so it wipes some stuff out for potential subsequent startup better.
• Added a setting for the experimental jump ignoring code so I no longer have to maintain multiple versions of the plugin. It's "use-jump-ignoring" in the properties file. Also added the command "useJumpIgnore [true|false]" to the plugin's command description and commands it is capable of handling.

Version 0.5.1

• Added some experimental jump-ignoring code.

Version 0.5

• Added a player count threshold making it so if the number of players on the server is below this threshold then nobody will be kicked. Set to 0 to always kick idlers.
• Made the system a bit more robust so if there's a problem with the players to be kicked task not happening we're not totally hosed until server restart. You should get a log message after 60 seconds saying that kicking players failed and then the system should be ready to go.

Version 0.4

• Fixed the TSLPC error.
• Corrected a problem in which the player command event was being listened for but not caught instead of listening for the player chat event which was attempted to be caught.

Version 0.3

• Added commands that allow you to hot-swap config values while the server is running.
• Added config-file saving which happens every time you change a value with a command. See commands above.

Version 0.2

• Removed setting re-saving on shutdown until settings hot-swapping is enabled while the server is running.

Version 0.1

• Releasing the AfkBooter.

Features for the future:

• Look into allowing multi-line kick messages. (low priority, haven't been able to figure it out yet).

Old Versions:
v1.0.2: jar
v1.0.1: jar
v1.0: jar
v0.9: jar
v0.8.1: jar
v0.8: jar
v0.7.1: jar
v0.7: jar
v0.6.1: jar
v0.6: jar
v0.5.1 (experimental, see change log): jar
v0.5: jar
v0.4: jar
v0.3: jar
v0.2: jar
v0.1: jar

 

Good to hear that.

 

I have tested it with no code changes and it is working fine on RB 818. Please note the update procedure in the first post and make sure you have done everything. If you still have problems after that, reply with a pastebin of your afkbooter.properties file.

Edit: Added a couple minor things for 1.0.2 which had been previously requested. Please see the changelog.

 

I must have missed something. I'll check that asap, sorry for the inconveniance.

 

Hi, I have a problem. Ever since updating to the latest RB of Bukkit (#860), AfkBooter doesn't listen too all of the events that the user specifies in the config file. I have AfkBooter set up to listen to player movement, player chat, and opening of inventory, however it does not seem to listen to player chat while it listens to the other two just fine. Players will get kicked after 5min of straight talking.

Here's my config file.

Code:

#Default auto-created config file. Version 1.0.1. Please change.
#kick-timeout is amount of time (sec) players can be idle, kick-message is the message the
#kicked player sees, kick-broadcast is the message all players see when a player is kicked (name + message),
#timeout-check-interval is the frequency (sec) to check for players to boot, and exempt-players is the list
#of players not to kick at all. player-count-threshold is the number of players that must be present before
#players start getting kicked for idling. Set to 0 for always. Set use-jump-ignoring to use the experimental
#code which ignores vertical movement for activity purposes. Set kick-idlers to determine whether or not idlers
#should actually be kicked or merely announced. ignore-vehicle-movement if set to true will not consider a player's
#movement if they are in a vehicle. use-faux-sleep will count AFK players as "sleeping" for the purposes of beds
#moving the clock forward; only works if kick-idlers is false. block-idle-items will prevent idlers from picking up
#items; only works if kick-idlers is false.
#Wed May 18 19:45:46 EDT 2011
kick-message=You have been AFK for too long!
block-idle-items=false
timeout-check-interval=300
exempt-players=dmansinful
kick-broadcast=was kicked for being AFK!
use-faux-sleep=false
use-jump-ignoring=false
ignore-vehicle-movement=false
listened-events=PLAYER_MOVE,PLAYER_CHAT,INVENTORY_OPEN
player-count-threshold=10
kick-idlers=true
kick-timeout=30

 

First off, you have no idea how nice it is to not have to ask for your config file in this reply. Thank you for including it!

Secondly, I have not had a chance to test it on 860 yet, but I'll do that when I get home from work tonight and see if I can track down the problem.

In the mean time, I notice that you have your timeout-check-interval set to longer than the kick-timeout. You'll probably want to reverse those two values. The timeout-check-interval tells the plugin how often it should check for players to kick, in this case, every 5 minutes. The kick-timeout tells the plugin how long a player can be idle without being kicked, in this case, 30 seconds. If you reverse them, you'll have it so a player can be idle for 5 minutes, but the plugin will check every 30 seconds to see if someone has been idle for that long.

All right, I tested it and it seems to be working fine for me. However, the inventory open seems to not be working properly, which jives with some other stuff I've seen. The Bukkit inventory events don't work properly yet and I didn't know that at the time that I added the INVENTORY_OPEN listening capability.

At any rate, I suspect the problem is likely related to your reversal of the timeout-check-interval and kick-timeout values. Let me know if you still have the issue after switching those and I'll look into it a bit deeper. Otherwise, I'll wait to hear from you.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Ahh, alright thank you very much for your reply. Didn't notice I had them reversed till now. I just switched the values like you said so hopefully that will settle it. I'll let you know if I still have problems.

 

I've had players report to me that they're able to get by the AFK kicking mechanism by standing in moving water. Is this a known issue yet?

 

Hi, is this working with permissions 3 ? thanks

 

If the water is moving them, yes. If the water has pushed them to a standstill and they are still being reported as moving, then no, it was not known but there is nothing I can do about that; it'd be a bukkit problem.

I have not tested it with Permissions 3. Unless they made a lot of API changes, I would imagine it still works.

 

Just about everything works with Permissions 3x inc this provided you steer clear of global permissions right now.

The only Issues with this I have had that users report is that it kicks them after 1 min regadless if they are doing somthing that I set in the Events config area or not.

Like I choose to Ignore movement and entity events as that opens doors to large amounts of ways to avoid the kick.
Id prefer only Chat and interact those kinds to be watched for flagging as not afk.

This was with bukkit 887 about to test now with 935 "latest reco" also I'm a little confused with the way this kicks.

It has two time settings now I don't know if I caused the issue as a result of telling it to check every 60s for afk players and kick ones afk for 5min what the goe was with it but I noticed that ppl chatting still got booted.


Here is my new config hope it works better will test this out overnight.

PHP:

#Default auto-created config file. Version 1.0.1. Please change.
#kick-timeout is amount of time (sec) players can be idle, kick-message is the message the
#kicked player sees, kick-broadcast is the message all players see when a player is kicked (name + message),
#timeout-check-interval is the frequency (sec) to check for players to boot, and exempt-players is the list
#of players not to kick at all. player-count-threshold is the number of players that must be present before
#players start getting kicked for idling. Set to 0 for always. Set use-jump-ignoring to use the experimental
#code which ignores vertical movement for activity purposes. Set kick-idlers to determine whether or not idlers
#should actually be kicked or merely announced. ignore-vehicle-movement if set to true will not consider a player's
#movement if they are in a vehicle. use-faux-sleep will count AFK players as "sleeping" for the purposes of beds
#moving the clock forward; only works if kick-idlers is false. block-idle-items will prevent idlers from picking up
#items; only works if kick-idlers is false.
#Tue Jun 28 23:23:52 EST 2011
kick-message=You were AFK too long and have been kicked!.
block-idle-items=false
timeout-check-interval=300
exempt-players=name1,name2,name3
kick-broadcast=Kicked for being AFK too long!!.
use-faux-sleep=true
use-jump-ignoring=true
ignore-vehicle-movement=true
listened-events=PLAYER_CHAT,INVENTORY_OPEN,BLOCK_PLACE,BLOCK_BREAK,PLAYER_INTERACT,PLAYER_DROP_ITEM,PLAYER_COMMAND_PREPROCESS
player-count-threshold=5
kick-idlers=true
kick-timeout=540


 

With this setting on the timeout-check-interval and the kick-timeout you'll get it only checking if someone has been afk long enough to kick every 5 minutes, with the kickability time set to 9 minutes. With it set this way, there'll likely be at least a 1 minute delay that someone has been AFK past your selected 9 minutes before they're kicked. (Meaning people will actually be allowed to be AFK for 10 minutes before getting kicked). That'll vary a bit depending on when they go AFK relative to the checker.

Do you get any errors in the console at all? Do people get kicked if they're placing/breaking blocks and/or interacting with blocks, or only when just chatting?

 

I got no error during this time at all but suddenly 3 - 6 ppl would DC
at the same time, this was on a earlier verison tho I have not used it for about 3 weeks.

But when I tested it before on 860 yes it seemed to ingnore what I told it to check and it would kick people due to the fact the time out passed and they were afk just prior to the time out. I'm really not sure why it happend but people were kicked regadless of doing what I set most of the time.

I had it much harsher I had it at 30s interval check with kicktime of 3min. I did not count chat or anything.
Only command usage and interact and Inventory open. But I see u imporved it a whole LOT now. so far it appears to work fine on 935 have not had to kick anyone but I just need this really bad.

Being a small server with lik 11 ppl on a most half the time and running from home until I can afford colocation I needed this regadless due to fact I now Run that Timed Ranking system and I did not want people afking over night exploiting it so they could get more ingame hours logged to get to member rank.

Edit:

So what your saying my current settings are decent ?
and around 10min before being seen as AFK ?

 

All right, let me know if there are further issues.

 

I think you guys are likely already aware of this, but afkbooter shuts your server down instead of kicking players on 935. I've removed it until the dev can update and fix things.

 

Well now it makes sense...

 

in regards to people not being kicked in moving water, it IS a bug (prolly bukkit).... I have people with mob traps that simply stand in the running water, in a corner, and they dont get kicked... they are standing in moving water block so bukkit reads it as they are moving with the flow, however, it is the last water flow block, so they are not pushed further. If you put blocks near you, so that this 'end flow' block is in a corner, you never get 'out' of the flow, but are not actually moving >.>

And since i had this mod to keep people from mob farming, its sorta useless now >.>

 

Can you give me more information? "Shuts your server down" is not very descriptive. Is it a crash, is it like the server received a stop command, or something else?

There are other events you can listen to besides PLAYER_MOVE to determine if a player is actually doing things. I've detailed them in the first post.

I'm planning on testing and upgrading this for both RB 935 and 953 either today or tomorrow (depends on time available today). I'll make sure to get compatibility for 935 as it sounds like 953 has some issues.

 

yeah, i know. But there are some people on the server, who literally do nothing but walk across the server for about 9-10 minutes while they try to get to their bases And they were getting kicked when i had player_move off

I'm not saying the plugin sucks because of this, i'm just saying after weighing my causes for actually using the plugin, it wasn't a top priority at this time (not to mention, i'm trying to shorten my plugin list :/ )

 

i hate to ask this, but is this actually updated an confirmed working by you neromir? cause it still says 860 in the topic title?

 

@neromir

My players go AFK and tape the mouse button down behind a mob spawner to get EXP for my RPG plugin. What settings would make them not be able to hold down 'W' and Left Click and still be kicked...?

 

No, it is not. The last version it was tested with and working by users was 928, although I have not tested it with that version myself. I'm currently working on testing/fixing it for RB 935 and RB 953. There should be an update out within a few hours.

Probably BLOCK_PLACE and BLOCK_BREAK are going to be your best bets, perhaps in addition to PLAYER_CHAT and PLAYER_COMMAND_PREPROCESS. Keep in mind that anybody who is legitimately moving around but is not actually placing/breaking blocks and/or chatting/using commands would be kicked as well with these settings.

Edit: @dkeulen This is tested and working with RB 935 using Permissions 2.7.3. Am beginning testing with Permissions 3 now.

Edit 2: Now tested and working on RB 935 using Permissions 3.1.6, with one minor problem that has been fixed and will be pushed out later (using command /afkbooter list results in an NPE if nobody is afk). Moving on to test with RB 953.

Edit 3: This is tested and verified to be working with both RB 935 and 953. Small bugfix added for the previously mentioned problem (edit 2). This version was tested with Permissions 3.1.6, but should also work fine with 2.7.3 as there were no code changes related to Permissions. If you still have problems with this plugin after downloading the latest version, please post a full bug report.

 

love this plugin but lately my console is spamming errors after some time running and blocking all players trying to join the server.

error:

Code:

[SEVERE] [AfkBooter] Failed to kick idle players. Passed timeout (60 sec) after found idlers.

 

Can you give me any more information such as what CB version are you running, how long does it run for before this happens, are there any other errors that show up in the log, what is in your afkbooter.properties file? My server has been running for 8 hours between auto-restarts regularly without this issue, so any info you could provide would help.

 

bukkit 953
afkbooter 1.0.3
config:

Code:

kick-message=Kicked for idle.
block-idle-items=false
timeout-check-interval=30
exempt-players=
kick-broadcast=kicked for idle
use-faux-sleep=true
use-jump-ignoring=false
ignore-vehicle-movement=false
listened-events=PLAYER_MOVE,PLAYER_CHAT
player-count-threshold=0
kick-idlers=true
kick-timeout=300

my server auto restarts every day and it can bug after a hour or after 10 hours.. very different

 

Hmm, nothing sticks out to me there as needing fixing. When did this start happening (with what version)? Also, what other plugins are you running? One of them could be interfering in a way that is causing the AfkBooter to freak out. If you are able and/or have a test server, I would recommend starting with just the AfkBooter enabled and see if the problem occurs. If it does not, then it is likely a conflict.

The best way to find a conflict is one of the following:

a) turn on AfkBooter by itself and add plugins one at a time until the problem begins occurring.

b) leave the AfkBooter enabled and do a binary search through the rest of your plugins: disable half of your plugins. If the problem does not occur, disable that half and enable the other half. If the problem does occur, disable half of those that were running and see if it happens. If not, disable that half and re-enable the other half. Repeat this process until you've narrowed it down to the offender. If you have a larger number of plugins, this method will be faster than a).

Or lastly, if you know of a particular plugin or group of plugins that you installed at around the same time this issue began, you have a smaller group to start with.

 

We have people getting kicked even though they are chatting.

We use HeroChat and have PLAYER_CHAT in the event monitor of course.

 

It is possible/probable that HeroChat is canceling the PLAYER_CHAT event prior to it arriving at the AfkBooter, in which case it will not get counted for activity. I'll see if I can look into it; it may have to be made into a special case that would ignore whether or not the even is canceled. That would also potentially cause other problems, however.

 

Running CB Version 1003, version 1.0.3 of this, my players are kicked every 15 minutes with the kick-timeout set to 900. All of my players are being active and are being kicked while breaking blocks and chatting.

Is this a known bug with 1000+ or do you know how to fix this?

 

Nope. Paste here or Pastebin your afkbooter.properties file and I'll take a look.

On a side note, I only support recommended builds. So if it doesn't happen on that one and it isn't something misconfigured with your properties file, my recommendation will be to change to RB 1000. Note that I still need to test with RB 1000 myself.

 

Unfortunately with my serverhost (GSVerse) they have an automatic update feature that grabs the latest bukkit build. If it were up to me, I'd still be on 953 myself, but apparently I've been on 964 for a while, so I tried to grab 1000 when it was out, but apparently was too late and got 1000 instead. So I don't know how to get them to downgrade it. I have FTP access, but it doesn't use the .exe's in there.

Anyways, I'll hit up their staff and see if I can downgrade, but until then, here's my afkbooter.properties file:

Code:

#Default auto-created config file. Version 1.0.3. Please change.
#kick-timeout is amount of time (sec) players can be idle, kick-message is the message the
#kicked player sees, kick-broadcast is the message all players see when a player is kicked (name + message), 
#timeout-check-interval is the frequency (sec) to check for players to boot, and exempt-players is the list
#of players not to kick at all. player-count-threshold is the number of players that must be present before
#players start getting kicked for idling. Set to 0 for always. Set use-jump-ignoring to use the experimental
#code which ignores vertical movement for activity purposes. Set kick-idlers to determine whether or not idlers
#should actually be kicked or merely announced. ignore-vehicle-movement if set to true will not consider a player's
#movement if they are in a vehicle. use-faux-sleep will count AFK players as "sleeping" for the purposes of beds
#moving the clock forward; only works if kick-idlers is false. block-idle-items will prevent idlers from picking up
#items; only works if kick-idlers is false.
#Tue Jul 19 04:51:02 EDT 2011
kick-message=Kicked for idling.
block-idle-items=false
timeout-check-interval=10
exempt-players=name1,name2,name3
kick-broadcast=kicked for idling.
use-faux-sleep=true
use-jump-ignoring=false
ignore-vehicle-movement=false
listened-events=
player-count-threshold=19
kick-idlers=true
kick-timeout=900

As a temporary fix, I had to set my threshold to 19, since my server cap is 18, so no one's getting booted, so at least that works. :/