Anti-VPN (Bungee)

Code (Text):

# How the plugin stores long-term data
# Note that you must configure at least one storage engine
storage:
  engines:
    # Engine name. Can be anything
    engine1:
      # Engine type. Can be "mysql", "old_mysql", "mariadb", "postgresql", "h2", or "sqlite"
      # "mysql" is for MySQL versions > 5.5, "old_mysql" is for MySQL versions <= 5.5
      # https://mariadb.org/
      # https://www.postgresql.org/
      # https://www.h2database.com/html/main.html
      # https://www.sqlite.org/index.html
      type: 'mysql'
      # Whether or not to use this engine
      enabled: false
      connection:
        # Address and port (MySQL, MariaDB, PostgreSQL only)
        address: '127.0.0.1:3306'
        # The name of the database the plugin will store data in (MySQL only)
        # This must be created beforehand
        database: 'anti_vpn'
        # Credentials
        username: ''
        password: ''
        # Extra options to use with this storage engine
        # These values will override any others
        options: 'useSSL=false&useUnicode=true&characterEncoding=utf8'
    # Engine name. Can be anything
    engine2:
      # Engine type. Can be "mysql", "old_mysql", "mariadb", "postgresql", "h2", or "sqlite"
      # "mysql" is for MySQL versions > 5.5, "old_mysql" is for MySQL versions <= 5.5
      # https://mariadb.org/
      # https://www.postgresql.org/
      # https://www.h2database.com/html/main.html
      # https://www.sqlite.org/index.html
      type: 'h2'
      # Whether or not to use this engine
      enabled: true
      connection:
        # File name (SQLite, H2 only)
        file: 'anti_vpn'
        # Extra options to use with this storage engine
        # These values will override any others
        options: 'useUnicode=true&characterEncoding=utf8'
  settings:
    # The maximum size of the storage engine connection pool
    # Determines the max number of connections to storage engines
    max-pool-size: 4
    # The minimum size of the storage engine connection pool
    # Determines the min number of connections kept alive to storage engines
    min-idle: 4
    # The maximum lifetime of a connection in the pool
    # Should be at least 30 seconds less than any storage engine or infrastructure-imposed connection time limit
    max-lifetime: '30minutes'
    # The maximum amount of time that the plugin will wait for a new connection from the pool before timing out
    timeout: '5seconds'
  # The order in which the storage engines will be used
  # The first available engine will be considered the "master" and will be the authoritative data source
  # Keep in mind that, for redundancy, ALL defined and enabled storage engines will be used
  order:
    - 'engine1'
    - 'engine2'

# How the plugin rapidly shares information with other servers along the network
messaging:
  engines:
    # Engine name. Can be anything
    engine1:
      # Engine type. Can be "rabbitmq" or "redis"