Untitled

#------------------------------------------------------------#
#       ____        __     _____            __               #
#      / __ )____  / /_   / ___/___  ____  / /________  __   #
#     / __  / __ \/ __/   \__ \/ _ \/ __ \/ __/ ___/ / / /   #
#    / /_/ / /_/ / /_    ___/ /  __/ / / / /_/ /  / /_/ /    #
#   /_____/\____/\__/   /____/\___/_/ /_/\__/_/   \__, /     #
#                                                /____/      #
#              ___                __  _                      #
#             / __\ ___   _ __   / _|(_)  __ _               #
#            / /   / _ \ | '_ \ | |_ | | / _` |              #
#           / /___| (_) || | | ||  _|| || (_| |              #
#           \____/ \___/ |_| |_||_|  |_| \__, |              #
#                                        |___/               #
#                                                            #
#           Developed by xDefcon & BlackDemonZyT             #
#                                                            #
#------------------------------------------------------------#
# This is the default configuration file, we did our best to #
# achieve the settings that could fit almost any network.    #
# In some cases, if your network is big for instance, you    #
# may have to edit the values and do some tests by yourself  #
# in order to find the most suitable way.                    #
##############################################################


# The name of your server(s) where players do /login and /register commands
auth-lobby:
  - "PRELOBBY3"

# Define that if in X seconds, Y connections are established, it will enable the AntiBot mode.
# You can also change the duration and ActionBar message.
antibot-mode:
  seconds: 2
  connections: 10
  duration: 30
  activated-msg: "&a&lAntiBot mode activated."
  deactivated-msg: "&c&lAntiBot mode deactivated."

# Configure when an IP should be Banned using the Linux command specified below
# based on their N connection per X seconds.
# Format: "Connections;Seconds"
thresholds:
  - "30;60"
  - "60;120"
  - "75;140"
  - "100;200"

# If one of the above criteria is met, then the rate limiter kicks in.
ratelimit:
  enabled: true
  # Should ban ip via linux command?
  ban: true
  # The LINUX command that will be executed to ban IP addresses internally.
  ban-command: "echo {ip}"
  # The LINUX command that will be executed to unban IP addresses internally.
  unban-command: "echo {ip}"
  # Change the delay between unban of each IP (in milliseconds, recommended not to touch)
  unban-delay: 75
  # Every how many hours should the plugin unban all banned IPs?
  reset-banned-hrs: 24

# This section is related to BotSentry checks and algorithms configuration.
# You basically don't need to understand the following, as it could result difficult or not clear.
#
# The default settings are set in order to define whether a client is a BOT or a clean USER.
# BotSentry uses the following to tune-up the detection, please keep those values updated with feature
# releases of the plugin.
#
# If you encounter difficulties or problems with bot attacks, please contact the developer on Discord (preferred).
bot-behaviour:
  # Enable a first-step mechanism to determine if a user is a bot or not.
  basic: true
  # The following, when enabled. will check the behaviour of the connected client, usually most bots are caught
  # by this system.
  advanced: true
  # This value should never be more than 3500. If you encounter false positives, please contact developers before
  # playing with this value.
  min-value: 2500
  # This section is intended to check, during a bot attack, the number of new connections and compare them with a
  # previous recorded "normal-behaviour"
  consistency:
    enabled: false
    count: 20
    delta: 11
  # The following should be enabled when "consistency" is enabled too, it compares the previous data over a long period
  # and adds some leniency in order to avoid false positives.
  collection:
    enabled: true
    count: 25
    leniency: 3
  # Do you want to kick bots from the specified authlobby after banning them via IPTables?
  # We suggest to leave this as true, mainly because after blocking an address via firewall, the related connections
  # will remain open for some time.
  kick-authlobby: true

# The first join check will ask, during a bot attack, all new players to rejoin.
# The kick message will be displayed once ONLY for NEW players.
first-join:
  enabled: true
  time: 2000
  kick-message: "&aPlease, rejoin the server."

whitelist:
  # After N seconds of playtime, the player is added to the BotSentry whitelist, and not checked anymore.
  seconds-to-play: 70

# This check will limit how many players can play with the same IP address during an attack and not.
max-address:
  # Toggle the check
  enabled: true
  threshold:
    # Max ip addresses that are allowed to play in normal conditions
    normal: 3
    # Max ip addresses that are allowed to play during a bot attack
    antibotmode: 2

# The following section will check all incoming connections in order to determine wheter a number of connection could be
# considered as bot attack (similar to "AntiBotMode").
networking:
  # This value should be related to the average players' latency. We suggest to leave this as 45, and playing with
  # leniency option. This value should never be changed with values over "52".
  tolerance: 50
  trigger: 2
  leniency: 1.26

# Section related to actionbar messages - "botsentry.advice" permission.
actionbar:
  # Toggle actionbar notification to admins.
  enabled: true
  msg: "&8[&a{ip}&8] &7has been detected as a &cBOT"
  first-join: "&8[&a{username}&8] &7has been kicked for &cFIRST JOIN"
  rejoin: "&8[&a{username}&8] &7has been kicked for &cREJOIN"
  rejoin-success: "&8[&a{username}&8] &7rejoined &aSUCCESSFULLY"
  whitelist: "&8[&a{username}&8] &7joined, he is in the &aWHITELIST"
  whitelisted: "&8[&a{username}&8] &7has been &aWHITELISTED"
  collection: "&8[&a{username}&8] &7got kicked for &cCOLLECTION"
  consistency: "&8[&a{username}&8] &7got kicked for &cCONSISTENCY"
  collection-active: "&a&lCOLLECTION ENABLED"
  consistency-active: "&a&lCONSISTENCY ENABLED"

# Section related to title message - "botsentry.advice" permission - sent every 10 seconds during an attack.
title:
  enabled: true
  title: "&c&lFresh Bots"
  subtitle: "&e&l{num} &6&lbots IPTables banned in 10 seconds!"

# The message that is shown every connection to the console.
console-message: "&cFreshcraft &7>> &7[&e{ip}&7] [&a{nickname}&7] &6has connected! &7[&eNum. {count}&7]"

# Plugin messages sent to players.
msg:
  kick: "&6&l[Freshcraft] &6You have been detected as a &c&lBOT&6! \n &7Do you think that this is an error? \n &7Contact us on Twitter! \n &btwitter.com/FreshcraftNT"
  unbanning: "&aUnbanning IP addresses (this could take a while)..."
  unbanned: "&aUnbanned {count} IP addresses."
  reloaded: "&aPlugin reloaded."
  insufficient-permissions: "&cInsufficient permissions."
  ip-banned: "&aSuccessfully banned IP address."
  banning-via-firewall: "&4Freshcraft &7>> &aUsing Linux ban command: &b{ip} &7- &aThreshold: &b{threshold}"
  toggled-notifications: "&aSuccessfully toggled actionbar and title notifications."
  help: "&6&m--------------&c &lFreshBots HELP &6&m--------------\n
    &b \n
    &9Aliases: &b/bs &7& &b/botsentry\n
    &b \n
    &7/bs now &8> &eSee the banned bots in that time period\n
    &7/bs stats &8> &eSee the total banned bots in life period\n
    &7/bs ban &a{IP} &8> &eBan the specified IP via IPTables\n
    &7/bs unban &a{IP} &8> &eUnban the specified IP via IPTables\n
    &7/bs unban &aall &8> &eUnban all banned IPs via IPTables\n
    &b \n
    &6&m-----------------------------------------------"