FoxGate AntiVPN 1.1.1

Fixed older version, update to this asap!

• Fixed option database.cache_database no working correctly. Now seems to works perfectly.
• Feature consolefilter now passed to Free Edition, decision made by me and my community. This now has been passed to configuration section:

#     ___             __ _                       _   _            
#    / __\___  _ __  / _(_) __ _ _   _ _ __ __ _| |_(_) ___  _ __
#   / /  / _ \| '_ \| |_| |/ _` | | | | '__/ _` | __| |/ _ \| '_ \
#  / /__| (_) | | | |  _| | (_| | |_| | | | (_| | |_| | (_) | | | |
#  \____/\___/|_| |_|_| |_|\__, |\__,_|_|  \__,_|\__|_|\___/|_| |_|
#                          |___/                                  

# Configure some others little options.
configuration:

   # Allow the usage of Metrics (bStats) in your server?
   # - This is only for stadistics usage.
   #
   #   ❝ What data is collected?
   #   We are using bStats (https://bstats.org/), this does not collect
   #   any personal data. Most of the collected data is information about
   #   the plugin's server like player count, online mode, Minecraft version,
   #   Java version, and more. All data gets sent and stored completely
   #   anonymously. See more in information about this in "bStats: Getting Started"
   #   https://bstats.org/getting-started
   #
   # (!) Since 1.0.2 (premium) and 1.1.0 (free), FoxGate uses
   #     their own code base for Metrics, but following their
   #     rules. This use asynchronous methods to send data and
   #     changes to Gson for better stability; improving the
   #     performance of this. You can safety has enable this to
   #     help to the creator without affecting the performance.
   metrics: true

   # Print to console?
   # - Enable this to send the equal notification to the console when
   #   a player is flagged.
   console: true

   # Define the permission.
   # - Set here the permission to see the notification in case this
   #   is used in case a player is using VPN. By default, this is one
   #   permission default of the antivpn: 'foxav.notifications'
   permission: 'foxav.notifications'

   # Do you want to enable this feature?
   # - Automatic check new updates in the Market pages. This only detect
   #   when the server is starting. You need to have connection for check
   #   new updates.
   #
   # (!) Since 1.0.0 (premium) and 1.0.6 (free), FoxGate uses
   #     their own code code for update chacking. This use
   #     asynchronous methods to scan updates; improving the
   #     performance of this. You can safety has enable this to
   #     verify updates without affecting the performance.
   update: true
 
   # Do you want debug enable debug messages of FoxGate?
   # - Set what messages you want to debug when the debugging mode
   #   is enabled with the command '/fg debug'. This only shows in
   #   the console.
   debug:
     # Messages about Events of the player?
      events: true
      # Messages returning service's responses for better
      # creation or control of this. Enable only for testing,
      # don't recommend enable this in production, otherwise,
      # your console can be flooded a lot.
      services: true
      # Messages about actions making by FoxGate.
      # Like, sending discord webhooks (responses), downloading
      # GeoLocation databases and seding Telegram (requests).
      actions: true
     
    # Enable the option to hide any disconnection message
    # when a player is detected for VPN, it's blocked for
    # their Country or ASN.
    # This probably doesn't go to work in some platforms or
    # versions, because only support Apache Log4J and SLF4J.
    consolefilter:
       # Enable hide the message of disconnection if the next
        # scenaries.
        vpn: true
        limiter: true
        # Premium Edition features.
        country: true
        asn: true

FoxGate Premium was released! :D
See the description section to view where you can purchase it, you can join to the discord server for any question about it.

• Improved the performance with remaking the handling of detection in all supported loaders/softwares.
• Added ViaProxy loader/software support.
• Updated all libraries:
  • MariaDB from 3.5.1 -> 3.5.3
  • SQLite from 3.49.0.0 -> 3.49.1.0
  • MiniMessage from 4.18.0 -> 4.20.0
  • MiniMessage Option from 1.0.0 -> 1.1.0
  • HikariCP from 6.2.1 -> 6.3.0
  • SLF4JAPI from 2.0.16 -> 2.1.0-alpha1
  • SL4FJJDK new in 2.1.0-alpha1
  • GSON from 2.12.2 -> 2.13.1
  • ASM from 9.7.1 -> 9.8
  • Jar-Relocator now is using my fork.
• Added new command /fg debug for debugging all actions of FoxGate:
  (config.yml)
  

  # Do you want debug enable debug messages of FoxGate?
   # - Set what messages you want to debug when the debugging mode
   #   is enabled with the command '/fg debug'. This only shows in
   #   the console.
   debug:
      # Messages about Events of the player?
      events: true
      # Messages returning service's responses for better
      # creation or control of this. Enable only for testing,
      # don't recommend enable this in production, otherwise,
      # your console can be flooded a lot.
      services: true
      # Messages about actions making by FoxGate.
      # Like, sending discord webhooks (responses), downloading
      # GeoLocation databases and seding Telegram (requests).
      actions: true
  
  message:
   help:
      debug: 'Debug actions made by FoxGate in the console.'
   debug:
      enable: '{prefix} <green>You enabled the debug mode. Check the console.'
      disable: '{prefix} <red>You disabled the debug mode.'

• Added new command to whitelist add/remove to the configuration. Also, moved all whitelist to new file created by default called whitelist.yml.
  (whitelist.yml)
  

  # Whitelist the detection to this name's.
  # - Allow players in the list to bypass the detection of
  #   the antivpn. To disable this feature, use the value:
  #
  #   names: []
  #
  # (!) It's case sensetive!
  names:
  - ImZowi
  
  # Whitelist the detection to this IP's.
  # - Allow ip's in the list to bypass the detection of
  #   the antivpn. To disable this feature, use the value:
  #
  #   ips: []
  #
  # (!) The value under is the default in localhost.
  ips:
  - "127.0.0.1"

  (config.yml)

  message:
     help:
        whitelist: 'Edit configuration via command whitelist user/IP.'
     whitelist:
        invalid_usage: '{prefix} Use the command <aqua>/foxgate whitelist <add/remove> <name/ip><reset>.'
        already: '{prefix} {IP}<red> is already whitelisted/unwhitelisted in the configuration!'
        whitelisted: '{prefix} {IP}<green> was whitelisted in the configuration with type <white>{type}</white>. You can <white><underlined><click:run_command:"/foxgate whitelist remove {IP}">click here for remove again</click></underlined></white>.'
        unwhitelisted: '{prefix} {IP}<green> was unwhitelisted in the configuration with type <white>{type}</white>. You can <white><underlined><click:run_command:"/foxgate whitelist add {IP}">click here for add again</click></underlined></white>.'
        type_ip: 'IP'
        type_name: 'Name'
        problem: '{prefix} <red>Error while trying to add/remove to the whitelist. Check the console.'

• Added new option for using name in proxies and new command /fg clearcache. This works with using a cache file or using database in case it's multi-proxy.
  (config.yml)
  

  database:
    # You want to save the cache in the database in new table
    # instead of use a file? Use this only if you want to use
    # multi-proxy or you're sure you don't has problems with your
    # database.
    #
    # Name of this table it's '"table"_cache', so, if the "table"
    # it's "foxgate", the name will be: "foxgate_cache", or if
    # the "table" it's "vpn_cache", will be "vpn_cache_cache". Always
    # finish with "_cache".
    cache_database: false
  
  message:
     help:
        clearcache: 'Clear the cache file with username saves.'
     clearcache:
        purging: '{prefix} <white>We are <yellow>purging</yellow> the cache file...'
        purging_correctly: '{prefix} <green>The cache file has been purged/reseted.'
        purging_problem: '{prefix} <red>Error while trying to purge the cache file. Check the console.'

• Added option to Limit connections per IP. Default it's 3.
  (config.yml)
  

  antivpn:
  
     # Limit maximum connections per IP.
     # - When a player join to the server, this is saved
     #   in a list for count the numbers of players in
     #   a connection. If the limit is reached, the
     #   player isn't allowed from joining.
     limiter:
       # Enable this feature?
       enable: true
       # Determine the maximum limit of connections per
       # IP. '3' is the best value by default, increase in
       # case is required. This can help in prevent bots with
       # same IP.
       maxium: 3
       # Message to return when a player is kicked with this option.
       # placeholders: %PLAYER%, %IP%, %UUID%, %COUNTRY% (Premium and
       # only if function is enabled) and %ASN% (Premium and only if
       # function is enabled).
       kick: "<red>You have been disconnected by FoxGate:\n<white>Maximum accounts per IP in your connection.\n\n<gray>This is an error? <white>Join to our discord server.\n<aqua><underlined>discord.idcteam.xyz"

• Using our custom base for bStats (Metrics) to avoid taking performance. For the Creator for the site, please, read our uncompiled comment inside the classes.
  
  (config.yml)
  

  configuration:
  
     # Allow the usage of Metrics (bStats) in your server?
     # - This is only for stadistics usage.
     #
     #   ❝ What data is collected?
     #   We are using bStats (https://bstats.org/), this does not collect
     #   any personal data. Most of the collected data is information about
     #   the plugin's server like player count, online mode, Minecraft version,
     #   Java version, and more. All data gets sent and stored completely
     #   anonymously. See more in information about this in "bStats: Getting Started"
     #   https://bstats.org/getting-started
     #
     # (!) Since 1.0.2 (premium) and 1.1.0 (free), FoxGate uses
     #     their own code base for Metrics, but following their
     #     rules. This use asynchronous methods to send data and
     #     changes to Gson for better stability; improving the
     #     performance of this. You can safety has enable this to
     #     help to the creator without affecting the performance.
     metrics: true

• Added new database type: JayBird.
  (config.yml)
  

  # This database is experimental.
  jaybird:
    hostname: "localhost"
    port: 3050
    database: "FoxGate.fdb"
    username: "foxgate"
    password: ""
  
    # These settings apply to this Firebird database, as it uses Hikari for connection pooling.
    # - Default values are suitable for most users. Modify only if necessary.
    pool-settings:
  
      # The maximum number of connections in the connection pool.
      # - Determines the upper limit of active database connections that can be managed simultaneously.
      # - Setting this too high can overload your database server, while setting it too low can cause delays.
      # Recommended: 10
      maximum-pool-size: 10
  
      # Minimum number of idle connections to maintain in the pool.
      # - The pool will try to maintain this number of idle (inactive) connections ready for use.
      # Recommended: 1
      minimum-idle: 1
  
      # Maximum lifetime of a connection in the pool, in milliseconds.
      # - Connections older than this value will be closed and replaced.
      # Recommended: 1800000 (30 minutes)
      maximum-lifetime: 1800000
  
      # The maximum time in milliseconds to wait for a connection from the pool.
      # - If no connection is available within this time, an exception will be thrown.
      # Recommended: 30000 (30 seconds)
      connection-timeout: 30000

• Added new 5 services in the default configuration. (Thanks for our buyer, @_bad_, for making these configurations for FoxGate in the default section)
  
  IPAPI IS
  

    # ⛽ IPAPI IS
    #  https://ipaphttps://ipapi.is/i.is/
    #
    #  Details:
    #  https://ipapi.is/app/signup
    #
    # - 1k daily requests, free account or without key (IP-based for limit).
    # - 10k daily requests, pay $10 monthly.
    # - 20k daily requests, pay $20 monthly.
    # - 50k daily requests, pay $50 monthly.
    # - 100k daily requests, pay $100 monthly.
    # - 2M daily requests, pay $200 monthly.
    ipapiis:
       # Enable this service?
       enabled: true
       # Model request to use.
       model: "JSON"
       # You can use this field in case you
       # has an account in this page.
       key: ""
       # URL.
       url: "https://api.ipapi.is/?q=%IP%&key=%KEY%"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "is_datacenter"
          - "is_tor"
          - "is_proxy"
          - "is_vpn"
          - "is_abuser"
          - "is_bogon" # Read more about this in https://ipgeolocation.io/blog/bogon-ip-addresses
          # Type to determine.
          type: boolean

  IPStack
  

    # ⛽ IPStack
    #  https://ipstack.com/
    #
    #  Details:
    #  https://ipstack.com/signup/free
    #
    # - 100 monthly requests, free account.
    # - 50k monthly requests, basic account.
    # - 500k monthly requests, professional account.
    # - 2M monthly requests, professional plus account.
    ipstack:
       # Enable this service?
       enabled: false
       # Model request to use.
       model: "JSON"
       # Insert your key here.
       # Don't delete this field!
       key: ""
       # URL.
       url: "https://api.ipstack.com/%IP%?access_key=%KEY%&security=1"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "security.is_proxy"
          - "security.is_crawler"
          - "security.is_tor"
          - "security.hosting_facility"
          # Type to determine.
          type: boolean

  2IP
  

    # ⛽ 2IP
    #  https://2ip.io/
    #
    #  Details:
    #  https://2ip.io/registration/api/
    #
    # - 10k requests free per month.
    # (Based in Billing)
    2ip:
       # Enable this service?
       enabled: false
       # Model request to use.
       model: "JSON"
       # Insert your key here.
       # Don't delete this field!
       key: ""
       # URL.
       url: "https://api.2ip.io/%IP%?token=%KEY%"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "asn.hosting"
          # Type to determine.
          type: boolean

  GreIP
  

    # ⛽ GreIP
    #  https://greip.io/
    #
    #  Details:
    #  https://dashboard.greip.io/login
    #
    # - 15k monthly requests, free account.
    # - 170k monthly requests, Standard account.
    # - 400k monthly requests, Premium account.
    # - Unlimited requests, "Pay-as-you-go".
    greip:
       # Enable this service?
       enabled: false
       # Model request to use.
       model: "JSON"
       # Headers in case is necessary.
       #
       # Set to: 'headers: []' to disable.
       headers:
          'Authorization': 'Bearer KEY'
       # URL.
       url: "https://greipapi.com/lookup/ip/threats?ip=%IP%"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "data.threats.isProxy"
          - "data.threats.isRelay"
          - "data.threats.isTor"
          - "data.threats.isHosting"
          # Type to determine.
          type: boolean

  IPGeolocation (PAID)
  

  # ⛽ IPGeolocation (PAID SERVICE)
    #  https://ipgeolocation.io/
    #
    #  Details:
    #  https://app.ipgeolocation.io/login
    #
    # This is a PAID SERVICE, require starting from
    # $15 monthly subscription for using IP-security
    # feature. First plan it's $15 (Bronze).
    #
    # - 150k monthly requests, Bronze ($15)
    # - 1M monthly requests, Solver ($65)
    # - 6M monthly requests, Gold ($200)
    # - 120M+ monthly requests, Enterprise.
    ipgeolocation:
       # Enable this service?
       enabled: false
       # Model request to use.
       model: "JSON"
       # Insert your key here.
       # Don't delete this field!
       key: ""
       # URL.
       url: "https://api.ipgeolocation.io/ipgeo?apiKey=%KEY%&ip=%IP%"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "security.is_tor"
          - "security.is_proxy"
          - "security.is_cloud_provider"
          - "security.is_known_attacker"
          - "security.is_anonymous"
          # Type to determine.
          type: boolean

• Fixed permissions with LuckPerms providing support multi-platform.
• Fixed PostgreSQL support.

➡️ Reset your configuration in case you want to apply already all the changes instead of copy manually.


FoxGate Premium was released! 
See the description section to view where you can purchase it, you can join to the discord server for any question about it.

• Improved the performance with remaking the handling of detection in all supported loaders/softwares.
• Added ViaProxy loader/software support.
• Updated all libraries:
  • MariaDB from 3.5.1 -> 3.5.3
  • SQLite from 3.49.0.0 -> 3.49.1.0
  • MiniMessage from 4.18.0 -> 4.20.0
  • MiniMessage Option from 1.0.0 -> 1.1.0
  • HikariCP from 6.2.1 -> 6.3.0
  • SLF4JAPI from 2.0.16 -> 2.1.0-alpha1
  • SL4FJJDK new in 2.1.0-alpha1
  • GSON from 2.12.2 -> 2.13.1
  • ASM from 9.7.1 -> 9.8
  • Jar-Relocator now is using my fork.
• Added new command /fg debug for debugging all actions of FoxGate:
  (config.yml)
  

  # Do you want debug enable debug messages of FoxGate?
   # - Set what messages you want to debug when the debugging mode
   #   is enabled with the command '/fg debug'. This only shows in
   #   the console.
   debug:
      # Messages about Events of the player?
      events: true
      # Messages returning service's responses for better
      # creation or control of this. Enable only for testing,
      # don't recommend enable this in production, otherwise,
      # your console can be flooded a lot.
      services: true
      # Messages about actions making by FoxGate.
      # Like, sending discord webhooks (responses), downloading
      # GeoLocation databases and seding Telegram (requests).
      actions: true
  
  message:
   help:
      debug: 'Debug actions made by FoxGate in the console.'
   debug:
      enable: '{prefix} <green>You enabled the debug mode. Check the console.'
      disable: '{prefix} <red>You disabled the debug mode.'

• Added new command to whitelist add/remove to the configuration. Also, moved all whitelist to new file created by default called whitelist.yml.
  (whitelist.yml)
  

  # Whitelist the detection to this name's.
  # - Allow players in the list to bypass the detection of
  #   the antivpn. To disable this feature, use the value:
  #
  #   names: []
  #
  # (!) It's case sensetive!
  names:
  - ImZowi
  
  # Whitelist the detection to this IP's.
  # - Allow ip's in the list to bypass the detection of
  #   the antivpn. To disable this feature, use the value:
  #
  #   ips: []
  #
  # (!) The value under is the default in localhost.
  ips:
  - "127.0.0.1"

  (config.yml)

  message:
     help:
        whitelist: 'Edit configuration via command whitelist user/IP.'
     whitelist:
        invalid_usage: '{prefix} Use the command <aqua>/foxgate whitelist <add/remove> <name/ip><reset>.'
        already: '{prefix} {IP}<red> is already whitelisted/unwhitelisted in the configuration!'
        whitelisted: '{prefix} {IP}<green> was whitelisted in the configuration with type <white>{type}</white>. You can <white><underlined><click:run_command:"/foxgate whitelist remove {IP}">click here for remove again</click></underlined></white>.'
        unwhitelisted: '{prefix} {IP}<green> was unwhitelisted in the configuration with type <white>{type}</white>. You can <white><underlined><click:run_command:"/foxgate whitelist add {IP}">click here for add again</click></underlined></white>.'
        type_ip: 'IP'
        type_name: 'Name'
        problem: '{prefix} <red>Error while trying to add/remove to the whitelist. Check the console.'

• Added new option for using name in proxies and new command /fg clearcache. This works with using a cache file or using database in case it's multi-proxy.
  (config.yml)
  

  database:
    # You want to save the cache in the database in new table
    # instead of use a file? Use this only if you want to use
    # multi-proxy or you're sure you don't has problems with your
    # database.
    #
    # Name of this table it's '"table"_cache', so, if the "table"
    # it's "foxgate", the name will be: "foxgate_cache", or if
    # the "table" it's "vpn_cache", will be "vpn_cache_cache". Always
    # finish with "_cache".
    cache_database: false
  
  message:
     help:
        clearcache: 'Clear the cache file with username saves.'
     clearcache:
        purging: '{prefix} <white>We are <yellow>purging</yellow> the cache file...'
        purging_correctly: '{prefix} <green>The cache file has been purged/reseted.'
        purging_problem: '{prefix} <red>Error while trying to purge the cache file. Check the console.'

• Added option to Limit connections per IP. Default it's 3.
  (config.yml)
  

  antivpn:
  
     # Limit maximum connections per IP.
     # - When a player join to the server, this is saved
     #   in a list for count the numbers of players in
     #   a connection. If the limit is reached, the
     #   player isn't allowed from joining.
     limiter:
       # Enable this feature?
       enable: true
       # Determine the maximum limit of connections per
       # IP. '3' is the best value by default, increase in
       # case is required. This can help in prevent bots with
       # same IP.
       maxium: 3
       # Message to return when a player is kicked with this option.
       # placeholders: %PLAYER%, %IP%, %UUID%, %COUNTRY% (Premium and
       # only if function is enabled) and %ASN% (Premium and only if
       # function is enabled).
       kick: "<red>You have been disconnected by FoxGate:\n<white>Maximum accounts per IP in your connection.\n\n<gray>This is an error? <white>Join to our discord server.\n<aqua><underlined>discord.idcteam.xyz"

• Using our custom base for bStats (Metrics) to avoid taking performance. For the Creator for the site, please, read our uncompiled comment inside the classes.
  
  (config.yml)
  

  configuration:
  
     # Allow the usage of Metrics (bStats) in your server?
     # - This is only for stadistics usage.
     #
     #   ❝ What data is collected?
     #   We are using bStats (https://bstats.org/), this does not collect
     #   any personal data. Most of the collected data is information about
     #   the plugin's server like player count, online mode, Minecraft version,
     #   Java version, and more. All data gets sent and stored completely
     #   anonymously. See more in information about this in "bStats: Getting Started"
     #   https://bstats.org/getting-started
     #
     # (!) Since 1.0.2 (premium) and 1.1.0 (free), FoxGate uses
     #     their own code base for Metrics, but following their
     #     rules. This use asynchronous methods to send data and
     #     changes to Gson for better stability; improving the
     #     performance of this. You can safety has enable this to
     #     help to the creator without affecting the performance.
     metrics: true

• Added new database type: JayBird.
  (config.yml)
  

  # This database is experimental.
  jaybird:
    hostname: "localhost"
    port: 3050
    database: "FoxGate.fdb"
    username: "foxgate"
    password: ""
  
    # These settings apply to this Firebird database, as it uses Hikari for connection pooling.
    # - Default values are suitable for most users. Modify only if necessary.
    pool-settings:
  
      # The maximum number of connections in the connection pool.
      # - Determines the upper limit of active database connections that can be managed simultaneously.
      # - Setting this too high can overload your database server, while setting it too low can cause delays.
      # Recommended: 10
      maximum-pool-size: 10
  
      # Minimum number of idle connections to maintain in the pool.
      # - The pool will try to maintain this number of idle (inactive) connections ready for use.
      # Recommended: 1
      minimum-idle: 1
  
      # Maximum lifetime of a connection in the pool, in milliseconds.
      # - Connections older than this value will be closed and replaced.
      # Recommended: 1800000 (30 minutes)
      maximum-lifetime: 1800000
  
      # The maximum time in milliseconds to wait for a connection from the pool.
      # - If no connection is available within this time, an exception will be thrown.
      # Recommended: 30000 (30 seconds)
      connection-timeout: 30000

• Added new 5 services in the default configuration. (Thanks for our buyer, @_bad_, for making these configurations for FoxGate in the default section)
  
  IPAPI IS
  

    # ⛽ IPAPI IS
    #  https://ipaphttps://ipapi.is/i.is/
    #
    #  Details:
    #  https://ipapi.is/app/signup
    #
    # - 1k daily requests, free account or without key (IP-based for limit).
    # - 10k daily requests, pay $10 monthly.
    # - 20k daily requests, pay $20 monthly.
    # - 50k daily requests, pay $50 monthly.
    # - 100k daily requests, pay $100 monthly.
    # - 2M daily requests, pay $200 monthly.
    ipapiis:
       # Enable this service?
       enabled: true
       # Model request to use.
       model: "JSON"
       # You can use this field in case you
       # has an account in this page.
       key: ""
       # URL.
       url: "https://api.ipapi.is/?q=%IP%&key=%KEY%"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "is_datacenter"
          - "is_tor"
          - "is_proxy"
          - "is_vpn"
          - "is_abuser"
          - "is_bogon" # Read more about this in https://ipgeolocation.io/blog/bogon-ip-addresses
          # Type to determine.
          type: boolean

  IPStack
  

    # ⛽ IPStack
    #  https://ipstack.com/
    #
    #  Details:
    #  https://ipstack.com/signup/free
    #
    # - 100 monthly requests, free account.
    # - 50k monthly requests, basic account.
    # - 500k monthly requests, professional account.
    # - 2M monthly requests, professional plus account.
    ipstack:
       # Enable this service?
       enabled: false
       # Model request to use.
       model: "JSON"
       # Insert your key here.
       # Don't delete this field!
       key: ""
       # URL.
       url: "https://api.ipstack.com/%IP%?access_key=%KEY%&security=1"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "security.is_proxy"
          - "security.is_crawler"
          - "security.is_tor"
          - "security.hosting_facility"
          # Type to determine.
          type: boolean

  2IP
  

    # ⛽ 2IP
    #  https://2ip.io/
    #
    #  Details:
    #  https://2ip.io/registration/api/
    #
    # - 10k requests free per month.
    # (Based in Billing)
    2ip:
       # Enable this service?
       enabled: false
       # Model request to use.
       model: "JSON"
       # Insert your key here.
       # Don't delete this field!
       key: ""
       # URL.
       url: "https://api.2ip.io/%IP%?token=%KEY%"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "asn.hosting"
          # Type to determine.
          type: boolean

  GreIP
  

    # ⛽ GreIP
    #  https://greip.io/
    #
    #  Details:
    #  https://dashboard.greip.io/login
    #
    # - 15k monthly requests, free account.
    # - 170k monthly requests, Standard account.
    # - 400k monthly requests, Premium account.
    # - Unlimited requests, "Pay-as-you-go".
    greip:
       # Enable this service?
       enabled: false
       # Model request to use.
       model: "JSON"
       # Headers in case is necessary.
       #
       # Set to: 'headers: []' to disable.
       headers:
          'Authorization': 'Bearer KEY'
       # URL.
       url: "https://greipapi.com/lookup/ip/threats?ip=%IP%"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "data.threats.isProxy"
          - "data.threats.isRelay"
          - "data.threats.isTor"
          - "data.threats.isHosting"
          # Type to determine.
          type: boolean

  IPGeolocation (PAID)
  

  # ⛽ IPGeolocation (PAID SERVICE)
    #  https://ipgeolocation.io/
    #
    #  Details:
    #  https://app.ipgeolocation.io/login
    #
    # This is a PAID SERVICE, require starting from
    # $15 monthly subscription for using IP-security
    # feature. First plan it's $15 (Bronze).
    #
    # - 150k monthly requests, Bronze ($15)
    # - 1M monthly requests, Solver ($65)
    # - 6M monthly requests, Gold ($200)
    # - 120M+ monthly requests, Enterprise.
    ipgeolocation:
       # Enable this service?
       enabled: false
       # Model request to use.
       model: "JSON"
       # Insert your key here.
       # Don't delete this field!
       key: ""
       # URL.
       url: "https://api.ipgeolocation.io/ipgeo?apiKey=%KEY%&ip=%IP%"
       # Values to check.
       values:
          # Fields to check.
          fields:
          - "security.is_tor"
          - "security.is_proxy"
          - "security.is_cloud_provider"
          - "security.is_known_attacker"
          - "security.is_anonymous"
          # Type to determine.
          type: boolean

• Fixed permissions with LuckPerms providing support multi-platform.
• Fixed PostgreSQL support.

➡️ Reset your configuration in case you want to apply already all the changes instead of copy manually.


FoxGate Premium was released! 
See the description section to view where you can purchase it, you can join to the discord server for any question about it.

1. ⚠ Fixed users without permissions to the command can see tab-arguments. This can show cached IP's, update now! (If you don't has plugin that hide tab-completion)
2. Support now 1.3.x to 1.21.x, changed internal libraries to Gson.
3. Improved command and improved performance.
4. Now libraries message are hidden by default, enable it with using argument '-Dfoxgate.enableLibrariesLog'.
5. Fixed in BungeeCord, player's get invalid packet for commands, making this only working in console only, now works in both.

FoxGate Premium was released! :D
See the description section to view where you can purchase it, you can join to the discord server for any question about it.

We are happy to announce... FoxGate Premium was released! :D
See the description section to view where you can purchase it, you can join to the discord server for any question about it.

Changelogs:

1. Fixed compatibility with some services, like ProxyCheck.
2. Improved performance and handling with the database, using totally async for Velocity and BungeeCord.

#      ___      _        _
#     /   \__ _| |_ __ _| |__   __ _ ___  ___
#    / /\ / _` | __/ _` | '_ \ / _` / __|/ _ \
#   / /_// (_| | || (_| | |_) | (_| \__ \  __/
#  /___,' \__,_|\__\__,_|_.__/ \__,_|___/\___|

# Configure a database for use.
database:

    # - Available options in type.
    #   All options use HikariCP for better performance.
    #  |=> MySQL
    #  |=> MariaDB
    #  |=> PostgreSQL
    #  |=> SQLite
    #  |=> H2
    #
    # If you change this configuration and your server is already
    # started. You can use the command "/foxgate db reconnect" to
    # apply the changes without restarting plugin or server.
    # Remember first reload the plugin with "/foxgate reload"
    # and use that command.
    type: "SQLite"
    # Edit table in case you want a different.
    # If you want to use your actually stats (of 1.0.5-pre4 or older),
    # use the next:
    # - "vpn_cache"
    table: "foxgate"
 
    # MariaDB/MySQL databases type. Edit here.
    remote:
      # Determine information of your database.
      hostname: "localhost"
      port: 3306
      database: "foxav_db"
      username: "root"
      password: "password123"
   
      # These settings apply to the MySQL/MariaDB connection pool (HikariCP).
      # - Default values are suitable for most users. Only modify these if you know what you're doing!
      pool-settings:

        # The maximum number of connections in the connection pool.
        # - Determines the upper limit of active database connections that can be managed simultaneously.
        # - Setting this too high can overload your database server, while setting it too low can cause delays.
        # Example:
        #   If your server has high traffic and the database can handle it, set this to 10 or higher.
        # Recommended: 10
        # More information: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
        maximum-pool-size: 10

        # Minimum number of idle connections to maintain in the pool.
        # - The pool will try to maintain this number of idle (inactive) connections ready for use.
        # - Setting this equal to 'maximum-pool-size' creates a fixed-size connection pool,
        #   ensuring consistent resource allocation.
        # Example:
        #   For a server with occasional traffic spikes, set this to half of 'maximum-pool-size'.
        # Recommended: 2
        minimum-idle: 2
    
        # Sets the maximum time an idle connection can remain in the pool before being automatically closed.
        # - Connections that remain idle for longer than the configured value will be removed from the pool
        #   and replaced with new connections as needed.
        # - This is useful to free up resources and keep connections "fresh" avoiding possible problems with
        #   stale connections.
        # Recommended: 600000 (10 minutes)
        idle-timeout: 600000

        # Maximum lifetime of a connection in the pool, in milliseconds.
        # - Connections older than this value will be closed and replaced.
        # - This prevents stale connections from lingering indefinitely and reduces database timeout issues.
        # - Should be at least 30 seconds less than the timeout imposed by the database itself.
        # Example:
        #   If your database timeout is 30 minutes, set this value to 25 minutes (1500000 ms).
        # Recommended: 1500000 (25 minutes)
        maximum-lifetime: 1500000

        # Frequency of pings to keep the connection alive, in milliseconds.
        # - This prevents connections from being closed due to inactivity (common in many databases or firewalls).
        # - Must be less than 'maximum-lifetime' and greater than 30 seconds (30000 ms).
        # Example:
        #   For long-running servers, a value of 10 minutes (600000 ms) is generally ideal.
        # Recommended: 600000 (10 minutes)
        keepalive-time: 600000

        # The maximum time in milliseconds to wait for a connection from the pool.
        # - If no connection is available within this time, an exception will be thrown.
        # - Setting a low value ensures responsiveness but may cause issues under heavy load.
        # Example:
        #   For responsive applications, a value between 3-5 seconds (3000-5000 ms) is ideal.
        # Recommended: 5000 (5 seconds)
        connection-timeout: 5000

        # Custom validation timeout (time taken to validate a connection), in milliseconds.
        # - Determines how long the pool will wait while testing if a connection is still valid.
        # - A low value improves responsiveness, but setting it too low may cause false negatives.
        # Example:
        #   For most databases, 3 seconds (3000 ms) is sufficient for validation.
        # Recommended: 3000 (3 seconds)
        validation-timeout: 3000
     
        # Leak detection threshold in milliseconds.
        # - This setting helps detect connections that are not properly closed.
        # - If a connection is checked out but not closed within this time, a warning will be logged.
        # - Useful for debugging connection leaks in plugins or applications.
        # Example:
        #   If you expect queries to be fast, a value of 60 seconds (60000 ms) can help catch leaks.
        #   If you have long transactions, set a higher value to avoid false positives.
        # Recommended: 60000 (1 minute)
        leak-detection-threshold: 60000
 
      # Custom properties for advanced users.
      # Add any additional properties to fine-tune the connection.
      #
      # You can uncomment unnecesary properties or remove,
      # also edit to values that is perfect for you.
      # (!) THIS PROPERTIES IS BASED WITH SUPPORT
      # MARIADB, IF YOU GET ERROR IN MYSQL, YOU CAN
      # ADAPT OR CONSIDERING TO CHANGE TO MARIADB,
      # THAT WORKS WITH MYSQL DATABASES.
      properties:

        # - SSL.
        # Database connection settings.
        # Adjust these properties to optimize the connection with your MySQL/MariaDB server.
        # Enables or disables SSL for secure connections.
        # It is highly recommended to set this to true if your server supports SSL.
        # Default is false, as many MySQL/MariaDB servers do not support SSL.
        sslMode: "disabled"
        requireSSL: "false"                   # If set to "true", forces SSL connections. Overrides 'sslMode'.
        verifyServerCertificate: "false"      # Validates the server's SSL certificate. Set to "true" for production.
        # - Connection Optimization
        cachePrepStmts: "true"                # Enables prepared statement caching
        prepStmtCacheSize: "250"              # Number of prepared statements to cache
        prepStmtCacheSqlLimit: "2048"         # Maximum size of a query in the cache
        useServerPrepStmts: "true"            # Uses server-side prepared statements
        # - Performance and Buffering
        rewriteBatchedStatements: "true"      # Optimizes batch insert/update performance
        useCompression: "false"               # Enables compression for data transfer (optional)
        maintainTimeStats: "false"            # Disables time statistics for improved performance
        autoReconnect: "true"                 # Automatically reconnects if the connection is lost
        # - Character Encoding
        # Specifies whether Unicode character encoding should be used.
        # If working with multilingual data, this is highly recommended.
        useUnicode: "true"
        # Defines the character encoding for the database connection.
        # Use "utf8" for compatibility with most character sets.
        characterEncoding: "utf8"
        # - Time Zone
        serverTimezone: "UTC"                 # Ensures consistent timezone handling

    postgresql:
      hostname: "localhost"
      port: 5432
      database: "foxav_db"
      username: "postgres"
      password: "password123"

      # Database connection settings for PostgreSQL.
      settings:

        # Adjust these properties to optimize the connection with your PostgreSQL server.
        # Enables or disables SSL for secure connections.
        # It is highly recommended to set this to true if your server supports SSL.
        # Default is false.
        ssl: false
        # The maximum time in seconds to wait for a connection from the pool.
        # Choose a value between 1 and 5 for a balance between availability and performance.
        # Recommended: 3.0
        connectiontimeout: 3.0

        # Specifies whether Unicode character encoding should be used.
        # PostgreSQL natively supports Unicode, so this can be left as true.
        useUnicode: true

        # Defines the character encoding for the database connection.
        # Use "UTF-8" to handle multilingual data and ensure compatibility.
        characterEncoding: "UTF-8"

        # Keeps idle connections alive.
        tcpKeepAlive: true

        # Timeout for socket operations in seconds.
        socketTimeout: 30

        # Number of prepared statement executions before switching to server-side prepared statements.
        prepareThreshold: 5

        # Application name for debugging or monitoring purposes.
        applicationName: "FoxGate"

        # Enables optimized binary transfer for certain data types.
        binaryTransfer: true
   
      # These settings apply to this PostgreSQL, because uses Hikari for connection.
      # - Default values are suitable for most users. Only modify these if you know what you're doing!
      pool-settings:

        # The maximum number of connections in the connection pool.
        # - Determines the upper limit of active database connections that can be managed simultaneously.
        # - Setting this too high can overload your database server, while setting it too low can cause delays.
        # Example:
        #   If your server has high traffic and the database can handle it, set this to 10 or higher.
        # Recommended: 10
        # More information: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
        maximum-pool-size: 10

        # Minimum number of idle connections to maintain in the pool.
        # - The pool will try to maintain this number of idle (inactive) connections ready for use.
        # - Setting this equal to 'maximum-pool-size' creates a fixed-size connection pool,
        #   ensuring consistent resource allocation.
        # Example:
        #   For a server with occasional traffic spikes, set this to half of 'maximum-pool-size'.
        # Recommended: 2
        minimum-idle: 2

        # Maximum lifetime of a connection in the pool, in milliseconds.
        # - Connections older than this value will be closed and replaced.
        # - This prevents stale connections from lingering indefinitely and reduces database timeout issues.
        # - Should be at least 30 seconds less than the timeout imposed by the database itself.
        # Example:
        #   If your database timeout is 30 minutes, set this value to 25 minutes (1500000 ms).
        # Recommended: 1800000 (30 minutes)
        maximum-lifetime: 1800000

        # The maximum time in milliseconds to wait for a connection from the pool.
        # - If no connection is available within this time, an exception will be thrown.
        # - Setting a low value ensures responsiveness but may cause issues under heavy load.
        # Example:
        #   For responsive applications, a value between 30-50 seconds (30000-50000 ms) is ideal.
        # Recommended: 30000 (30 seconds)
        connection-timeout: 30000
     
        # Leak detection threshold in milliseconds.
        # - This setting helps detect connections that are not properly closed.
        # - If a connection is checked out but not closed within this time, a warning will be logged.
        # - Useful for debugging connection leaks in plugins or applications.
        # Example:
        #   If you expect queries to be fast, a value of 60 seconds (60000 ms) can help catch leaks.
        #   If you have long transactions, set a higher value to avoid false positives.
        # Recommended: 60000 (1 minute)
        leak-detection-threshold: 60000

    sqlite:
      file: "FoxGate.db"
  
      # These settings apply to this SQLite, because uses Hikari for connection.
      # - Default values are suitable for most users. Only modify these if you know what you're doing!
      #
      # Yeah... I know HikariCP isn't better to use with SQLite, but is only for avoid any
      # type of errors! Please, don't kill me!
      pool-settings:

        # The maximum number of connections in the connection pool.
        # - Determines the upper limit of active database connections that can be managed simultaneously.
        # - Setting this too high can overload your database server, while setting it too low can cause delays.
        # Example:
        #   If your server has high traffic and the database can handle it, set this to 10 or higher.
        # Recommended: 10
        # More information: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
        maximum-pool-size: 10

        # Minimum number of idle connections to maintain in the pool.
        # - The pool will try to maintain this number of idle (inactive) connections ready for use.
        # - Setting this equal to 'maximum-pool-size' creates a fixed-size connection pool,
        #   ensuring consistent resource allocation.
        # Example:
        #   For a server with occasional traffic spikes, set this to half of 'maximum-pool-size'.
        # Recommended: 1
        minimum-idle: 1

        # Maximum lifetime of a connection in the pool, in milliseconds.
        # - Connections older than this value will be closed and replaced.
        # - This prevents stale connections from lingering indefinitely and reduces database timeout issues.
        # - Should be at least 30 seconds less than the timeout imposed by the database itself.
        # Example:
        #   If your database timeout is 30 minutes, set this value to 25 minutes (1500000 ms).
        # Recommended: 1800000 (30 minutes)
        maximum-lifetime: 1800000

        # The maximum time in milliseconds to wait for a connection from the pool.
        # - If no connection is available within this time, an exception will be thrown.
        # - Setting a low value ensures responsiveness but may cause issues under heavy load.
        # Example:
        #   For responsive applications, a value between 30-50 seconds (30000-50000 ms) is ideal.
        # Recommended: 30000 (30 seconds)
        connection-timeout: 30000
     
        # Leak detection threshold in milliseconds.
        # - This setting helps detect connections that are not properly closed.
        # - If a connection is checked out but not closed within this time, a warning will be logged.
        # - Useful for debugging connection leaks in plugins or applications.
        # Example:
        #   If you expect queries to be fast, a value of 60 seconds (60000 ms) can help catch leaks.
        #   If you have long transactions, set a higher value to avoid false positives.
        # Recommended: 60000 (1 minute)
        leak-detection-threshold: 60000

    h2:
      file: "h2db"
   
      # These settings apply to this H2, because uses Hikari for connection.
      # - Default values are suitable for most users. Only modify these if you know what you're doing!
      pool-settings:

        # The maximum number of connections in the connection pool.
        # - Determines the upper limit of active database connections that can be managed simultaneously.
        # - Setting this too high can overload your database server, while setting it too low can cause delays.
        # Example:
        #   If your server has high traffic and the database can handle it, set this to 10 or higher.
        # Recommended: 10
        # More information: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
        maximum-pool-size: 10

        # Minimum number of idle connections to maintain in the pool.
        # - The pool will try to maintain this number of idle (inactive) connections ready for use.
        # - Setting this equal to 'maximum-pool-size' creates a fixed-size connection pool,
        #   ensuring consistent resource allocation.
        # Example:
        #   For a server with occasional traffic spikes, set this to half of 'maximum-pool-size'.
        # Recommended: 1
        minimum-idle: 1

        # Maximum lifetime of a connection in the pool, in milliseconds.
        # - Connections older than this value will be closed and replaced.
        # - This prevents stale connections from lingering indefinitely and reduces database timeout issues.
        # - Should be at least 30 seconds less than the timeout imposed by the database itself.
        # Example:
        #   If your database timeout is 30 minutes, set this value to 25 minutes (1500000 ms).
        # Recommended: 1800000 (30 minutes)
        maximum-lifetime: 1800000

        # The maximum time in milliseconds to wait for a connection from the pool.
        # - If no connection is available within this time, an exception will be thrown.
        # - Setting a low value ensures responsiveness but may cause issues under heavy load.
        # Example:
        #   For responsive applications, a value between 30-50 seconds (30000-50000 ms) is ideal.
        # Recommended: 30000 (30 seconds)
        connection-timeout: 30000
     
        # Leak detection threshold in milliseconds.
        # - This setting helps detect connections that are not properly closed.
        # - If a connection is checked out but not closed within this time, a warning will be logged.
        # - Useful for debugging connection leaks in plugins or applications.
        # Example:
        #   If you expect queries to be fast, a value of 60 seconds (60000 ms) can help catch leaks.
        #   If you have long transactions, set a higher value to avoid false positives.
        # Recommended: 60000 (1 minute)
        leak-detection-threshold: 60000

    # When an IP isn't detected a vpn or proxy, this need to save in
    # cache to don't make more requests for a little time for save
    # performance and requests, customizable here.
    bypass:
        # Enable this feature?
        enable: true

        # Determine the amount in hours to save the IP in cache and avoid
        # make more requests to this IP. Useful to save performance and
        # verify only one time for certain time.
        #
        # Recommended: 2
        # Type 'permanent' for bypass permanent.
        expiration_time: 2

    # When an IP is detected in a result, this is save in the cache
    # to don't make more request for a little time, this value is
    # saved in hours.
    #
    # Recommended: 36
    # Type 'permanent' for blocking permanent.
    expiration_time: 36

1. Added new service for detecting Proxy, VPN and Datacenter: IPDetective

      # ⛽ IPDetective
      # https://ipdetective.io/
      #
      # Details:
      # https://ipdetective.io/login
      #
      # - 1,000 daily requests, free account.
      # - 30k daily requests, basic account.
      # - 80k daily requests, premium account.
      # - 200k daily requests, enterprise account.
      ipdetective:
         # Enable this service?
         enabled: false
         # Model request to use.
         model: "JSON"
         # Headers in case is necessary.
         #
         # Set to: 'headers: []' to disable.
         headers:
            'x-api-key': 'KEY'
         # URL.
         url: "https://api.ipdetective.io/ip/%IP%?info=true"
         # Values to check.
         values:
            # Fields to check.
            fields:
            - "type"
            # Type to determine.
            type: ["vpn", "datacenter", "bot", "proxy"]

1. FIXED VELOCITY SUPPORT, USE THIS VERSION FOR VELOCITY USERS NOW.
2. Fixed updater checker returning invalid version.
3. Fixed some displays.

We are working for the premium version, this for the moment has the webhook and geo (new, view how this system is in new configuration of this version) system, you can contact in the discord support for purchase with PayPal (for the moment, only). This go to be public for purchase when I finish all the systems planned.

1. Fixed some problems.
2. Improved a little more the performance.
3. Updated libraries.
4. Libraries now relocate to avoid problems with software, like Carbon.
5. Fixed permissions problems with Velocity.
6. Fixed problems with caching in the database.
7. Now the plugin use shaded class for reduce size and better compatibility.
8. Improved a little more the system of detection in VPNs.
9. Improved compatibility with Minecraft 1.7.x.
10. Fixed AntiVPNio endpoint.

We are working for the premium version, this for the moment has the webhook system, you can contact in the discord support for purchase with PayPal (for the moment, only). This go to be public for purchase when I finish all the systems planned.

Changelogs

1. Fixing default value for MySQL, adding configuration for MariaDB and MySQL default compatibility.
2. Fixed all errors with H2, it's now stable and usable in production.
3. Added a startup java argument for suppressing all log about the library downloader.
4. Added stable support for Velocity (and Forks).
5. Added stable support for BungeeCord (and Forks).
6. Using now Java 11 and applied A LOT OF CHANGES FOR PERFORMANCE.
7. Fixed some rarely errors in backend.
8. Improved SQLite performance with adding some execution.
9. Updated HikariCP from 4.0.3 to 6.2.1.
10. Added Negativity API (unlimited usage).

THIS UPDATE DOESN'T REQUIRE RESET YOUR CONFIG, YOU CAN COMPARE YOUR CONFIG.YML WITH THE .JAR INSIDE IF YOU WANT GET SOME LITTLE CHANGES.

(showing updates from 1.0.4 -> 1.0.5-pre5) - This version has been launched for public for testing, this seems to be stable, but if you find errors or problems, please, JOIN TO THE DISCORD SUPPORT.
Changelogs:

1. Added IPRisk API (unlimited usage).
2. Added FreeIPAPI.
3. Increased max_flags option to 3 for better avoid false flags for the amount of free APIs.
4. Added IPdb-Amelia API (unlimited usage).
5. Disabled SkyDB by default in configuration because their big delay in response.
6. Fixed value to check for VPN in case the API return in array list.
7. Added option to use value with array list. (this feature was added for IPdb-Amelia, for better results)
8. Added reload command for the plugin.
9. Fixed bypass permission.
10. Added auto-complete for add/remove sub-arguments.
11. Fixed Folia support.
12. Implemented a little API for developers.
13. Download their dependencies automatically when the server start, so you can use MySQL and SQLite in Proxy (BungeeCord/Velocity).
14. Added support for MiniMessage.
15. Added support for new databases: MariaDB, PostgreSQL and H2 with HikariCP.
16. Added new command /foxgate db; in this you can purge the database, all saved IP's (/foxgate db purge) and reconnect the database if you applied changes and you don't want restart your server (/foxgate db reconnect).
17. Added new command /foxgate status, with this you can see information from an IP saved in the database.
18. Improved the structure in the config.yml.
19. Updated and fixed some fields in the API.
20. Fixed in Velocity backends, this only detecting IP of host.
21. Fixed a lot of errors in 1.0.4 version.
22. Changed PlayerPreLoginEvent to AsyncPlayerPreLoginEvent for better performance.
23. Added default values in case your config is older. RECOMMENDED TO RESET IN UPDATES!

THIS UPDATE ONLY WORKS IN BACKEND, PROXY GO TO WILL BE SUPPORTED IN 1.0.5 (FINAL VERSION OF THIS PRE-VERSIONS). ALSO THIS VERSION REQUIRE RESET YOUR CONFIGURATION FILE FOR APPLY ALL NEW CHANGES!

1.0.5-pre2:

• Fixed loading in Velocity (still in experimental)

1.0.5-pre1:

• Added Velocity (experimental) support.