# ------------------
# Warnings Settings
Warnings :

  # In this field you can decide whether to activate the logs also via the console.
  log_console : true

  # This message will be sent to those with permission: bettersecurity.broadcast.warnings
  # < ? > You can find more information about the executors in the header.
  # ATTENTION! Do not use the "@" in front for the broadcast, there is already the automatic one via the above permission.
  formats:
    commands :
      # You can use the following placeholders:
      # - %command% | (The command that was blocked)
      format :
       - ' [MESSAGE ] &e&l⚠ ┃ &b %player% &7attempted to execute the command: &c%command%'
      console : ' %player% attempted to execute the command: %command%'
    port_bypass_prevention :
      # You can use the following placeholders:
      # - %port% | (Port where it is trying to login)
      # - %ip% | (IP where you are trying to login)
      format :
       - ' [MESSAGE ] &e&l⚠ ┃ &b %player% &7tried to enter via port &a%port%&7 with the IP: &c%ip%'
      console : ' %player% tried to enter via port %port% with the IP: %ip%'

# ------------------
# Port Bypass Prevention Settings
Port_Bypass_Prevention :

  # --------- < ? > ---------
  # If your spigot is on the same machine as the proxy, this feature will not be needed!
  # This is because you can set the IP of the spigot to 127.0.0.1,
  # and change it also in the proxy (only the target of the spigot server, if you put this ip in the proxy it will not allow any user to enter).
  # The ip 127.0.0.1 is a private ip, it means that it will be read only by the machine.
  # In this way it will be impossible for everyone to be able to enter through the port,
  # only the proxy will be able to connect, and let users in.
  #
  # If you use the proxy on a machine other than the spigot, the use of this features is recommended to increase your security!
  # I also recommend that you block the port and make it accessible only through the proxy, see this guide:
  # --> https://www.spigotmc.org/wiki/firewall-guide/

  enabled : false

  # If it is "true", the login attempt through the port will be sent to the chat.
  warning : true

  # --------- < ⚠ > ---------
  # You must enter the IP that you find in the config of your proxy.
  # If you have set "0.0.0.0" or "127.0.0.1" you have to change them by entering the exact IP of your machine.
  #
  # If in the proxy you have set the IP of the machine, you will have to enter it in this list!
  # If you set 0.0.0.0 or 127.0.0.1 it could be bypassable. So this feature would be useless!

  # Here you have to enter the proxy IP.
  # This will prevent malicious users from being able to enter via your server port,
  # but only via the proxy IP.
  # The default ip in the "10.1.0.5" list is just an example, you have to put the IP of your proxy in it.
  whitelisted_ips :
   - '10.1.0.5'

  # If it is active you will not be able to put as IP: 0.0.0.0, or 127.0.0.1.
  # You will be hunted at the attempt! If you are aware of what you are doing you can turn it off.
  safety_kicks : true

  # This is the message that will be shown when a user tries to join via the server port.
  kick_message : '&6&lBETTER SECURITY\n\n&7You &ccannot &7connect directly via this port.\n&7You have to enter through the ip &bmc.example.net&7.'

  # Additional security system that kicks the player trying to connect if they are already online.
  already_connected :

    enabled : true

    # Message that will be shown during the kick.
    message : '&6&lBETTER SECURITY\n\n&7You are already inside the server,\n&7you have been &ckicked&7 out!'