config.yml
# AfkTerminator Configuration File
# Author: Edge209
###################################################
# DO NOT CHANGE THE VERSION number for this file #
configVersion: 11
###################################################
#
###########
# GENERAL #
###########
# Enable/disable the whole function
afkMachineDetectEnable: true
#
# Enable if afkTerminator should check for latest plugin version (from bukkitdev)
updateCheckEnable: true
#
# The plugin can be enabled/disabled on a per-world basis. Simply list the worlds (one per line proceeded with " - ") where it should be enabled, or set to " - all"
#
worlds:
- all
#
#########################
# AFK Machine Detection #
#########################
#
# Enable/Disable detection of different types of AFK Machines
detectWater: true
detectMineCart: true
detectHorse: true
detectPig: true
detectJump: true
detectPiston: true
detectFishing: true
detectProjectile: true
detectInteraction: true
#
# The following specifies how sensitive afkTerminator should be in declaring a AFK machine is being used by a player.
# The higher the number the more sensitive the plugin will be. At a higher sensitivity the plugin will detect
# afk machines faster, but it is also more likely to generate false positives. (a.k.a think someone is using an AFK
# machine when they are not.). Higher sensitivity also will take more server processing power because the plugin
# is checking more often. The valid range is 1 to 10.
#
# 1 = Lowest sensitivity. AFK detection > 4 min on average. Lowest processor requirement. Lowest false-positive chance.
# 5 = Medium sensitivity. AFK detection around 1 - 3 minutes. Recommended value.
# 10 = Highest sensitivity. AFK detection < 30 seconds. Highest processor requirement. Highest false-positive chance.
#
afkSensitivity: 5
#
###############
# Punishments #
###############
#
# How shall we punish the use of the AFK Machine:
# NONE, LAVA, TNT, KICK, KILL, COMMAND, SPAWNMOB
punishment: NONE
#
# If the punishment setting is "COMMAND", this is that command (or commands).
# "[player]" will be replaced with't players name on execution
# Multiple commands can be executed by separating commands with " /n " (note required [space] before and after '/n')
# All commands must be on a single line in this file. e.g. commandPenalty: 'kill [player] /n ban [player]'
commandPenalty: 'ban [player]'
#
# If the punishment setting is "SPAWNMOB", this is the mob to spawn
mobToSpawn: ZOMBIE
# The LAVA, TNT, SPAWNMOB & COMMAND punishments normally are applied multiple times for maximum effect,
# but this can be limited by setting the following to any value > 0. If <=0 maximum punishment will be dealt
# For KILL and KICK punishments this will auto default to "1"
punishmentLimit: -1
#
###########################
# Auto-Relogin Prevention #
###########################
#
# The following set of configurations are intended to prevent client mods which have auto-login functions (such as Nodus)
# from minimizing the impact of AFK kicks, by simply re-logging in the player automatically.
#
# Enable if attempts by auto login mods are used in an attempt to get around AFK kicks
blockAutoLoginEnable: true
#
# The minimum time a player must wait before trying to login after leaving/kicked from the server (in seconds)
autoLoginMinTime: 5
#
# The multiplier to be used to increase/vary the minimum time needed for each subsequent attempt (supports fractions e.g. 1.5)
minTimeMultiplier: 1.0
#
# The number of repeated login attempts blocks allowed before further action is taken against a player
autoLoginMaxAttempts: 5
#
# The command to be executed if the max attempts is exceeded
maxAttemptsCommand: 'ban [player]'
#
# The message to display to a player when they are blocked due to auto-login
# Variables supported: [cooldown] = Number of seconds until login will be allowed
# [player] = Name of player that is the subject of the message
#
autoLoginBlockMsg: '[player] please wait [cooldown] seconds before trying to log in again.'
#
#######################
# Logging / Messaging #
#######################
#
# Enable logging of AfkTerminator Activity, including identification of AFK Machines
logEnable: true
#
# Level of detail in the logs (3=least detail; 1= most detail)
logLevel: 3
#
# Level of detail in the console during startup etc. (3 = least detail; 1= most detail)
# Set to level 2 to see Machine Detection events in the console
consoleLevel: 2
#
# The following when set 'true' will have afkTerminator look for and maintain a list of players with the
# permission 'afkterminator.mailReceive', and send these players mail when AFK machines are detected. (See more below)
mailNotifyEnable: false
#
# The message to display and/or mail to admins/moderators when an AFK machine is detected
# To receive the messages, players must have one or both permissions: afkTerminator.notify; afkTerminator.mailReceive
#
# Variables supported: [player] = Name of player that is the subject of the message
# [location] = Location of the AFK Machine (x,y,z)
# [afkMachine] = Type of AFK Machine
# [detection] = Method of detection
# [duration] = How long player was in the machine/activity before detection
# [time] = Day, Time, & Date of the detection
# [vehicle] = type of vehicle used ('N/A' if not a vehicle-based afk machine)
#
afkDetectMsg: 'AFK Machine ([afkMachine]) detected. [player] has [detection] at [location]. On [time]'
#
# AFK Detection messages (defined above) are sent to players with the permission 'afkTerminator.mailReceive'. This is accomplished
# by issuing a 'console command', using the syntax specified below. (Default is compatible with Essentials' mail function)
#
mailCommand: 'mail send [player] [message]'
#
# afkTerminator automatically maintains a list of players with the 'afkterminator.mailReceive' permission. Players which do not
# login to the server at least once during the interval (days) below, will be removed from the list. (Set to -1 to disable this function)
mailListRemovalTime: 7
#
###########
# THE END #
###########