SHARE
TWEET

Untitled

a guest Dec 13th, 2016 67 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. # If bungeecord is set to true, banned players will be kicked from BungeeCord itself.
  2. # (Players will not be kicked to the lobby when they are banned.)
  3. # This will also implicitly set ban_sync_ticks and mutes.sync_ticks if not configured.
  4. # This option has no effect if the plugin is running under BungeeCord rather than Bukkit.
  5. bungeecord: false
  6.  
  7. sql:
  8.   # MySQL, PostgreSQL, SQLite, and H2 are supported database drivers.
  9.   driver: SQLite
  10.  
  11.   ## MySQL/PostgreSQL settings ##
  12.   # If using SQLite/H2, the database will be stored in the LiteBans plugin folder,
  13.   # and most of these settings won't apply.
  14.  
  15.   # Database server address.
  16.   address: localhost:3306
  17.  
  18.   # Database name, username and password.
  19.   database: litebans
  20.   username: ''
  21.   password: ''
  22.  
  23.   table_prefix: 'litebans_'
  24.  
  25.   # LiteBans utilizes connection pooling for extra performance and reliability.
  26.   # min_connections: Minimum amount of pooled connections.
  27.   # max_connections: Maximum amount of pooled connections. See: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
  28.   # timeout: Connection timeout.
  29.   # idle_timeout: Maximum amount of time a pooled connection can remain idle before it is closed for inactivity.
  30.   pool:
  31.     min_connections: 1
  32.     max_connections: 10
  33.     timeout: 30 seconds
  34.     idle_timeout: 1 minute
  35.  
  36.   # Database engine. Only applies to MySQL.
  37.   engine: InnoDB
  38.  
  39.   # Format: <name>:<class>[:URL]
  40.   drivers:
  41.   - mysql:com.mysql.jdbc.Driver:https://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.37/mysql-connector-java-5.1.37.jar
  42.   - pgsql:org.postgresql.Driver:https://repo1.maven.org/maven2/org/postgresql/postgresql/9.4-1201-jdbc41/postgresql-9.4-1201-jdbc41.jar
  43.   - mariadb:org.mariadb.jdbc.Driver:https://repo1.maven.org/maven2/org/mariadb/jdbc/mariadb-java-client/1.3.0/mariadb-java-client-1.3.0.jar
  44.   - sqlite:org.sqlite.JDBC:https://repo1.maven.org/maven2/org/xerial/sqlite-jdbc/3.8.11.1/sqlite-jdbc-3.8.11.1.jar
  45.   - h2:org.h2.Driver:https://repo1.maven.org/maven2/com/h2database/h2/1.4.188/h2-1.4.188.jar
  46.  
  47. durations:
  48.   # Can be bypassed with the permission "litebans.unlimited.ban"
  49.   tempban_max: 7 days
  50.   # Can be bypassed with the permission "litebans.unlimited.mute"
  51.   mute_max: 1 day
  52.   # If true, players will not get an error when using a duration higher than the configured limit.
  53.   # The duration will be rounded down to the maximum duration instead.
  54.   round_down: true
  55.  
  56. mutes:
  57.   enabled: true
  58.  
  59.   # All of these commands can not be used while muted.
  60.   command_blacklist:
  61.   - /me
  62.   - /say
  63.   - /tell
  64.   - /whisper
  65.   - /reply
  66.   - /pm
  67.   - /msg
  68.   - /emsg
  69.   - /epm
  70.   - /etell
  71.   - /ewhisper
  72.   - /w
  73.   - /m
  74.   - /t
  75.   - /r
  76.   # If enabled, muted players cannot use commands containing ":", for example: "/minecraft:me".
  77.   prevent_bypass: true
  78.  
  79.   sync_ticks: 0
  80.  
  81. # All online players will be re-checked for bans per interval when this is set.
  82. # This only makes sense in a multi-server configuration,
  83. # or if you're otherwise manipulating the database while the server is running.
  84. ban_sync_ticks: 0
  85.  
  86. # If set, a ban or mute reason must be provided, otherwise players will get an error.
  87. # When set to false, "default_ban_reason" and "default_mute_reason" in messages.yml are used as reasons when no reason is provided.
  88. require_ban_mute_reason: false
  89.  
  90. warnings:
  91.   # Warnings will expire after this duration has passed.
  92.   expire_after: 7 days
  93.  
  94.   # Warning actions.
  95.   # Format: <amount>[+]:<action>
  96.   # If '+' is provided after the amount, the action will execute if the player has that amount of warnings or more.
  97.   actions:
  98.   - '3:/kick -s:$silent $player Final warning: $reason'
  99.   - '4:/tempban -s:$silent $player 1 day Reached 4 warnings: $list'
  100.  
  101.   # If enabled, the console will execute warning actions.
  102.   # Otherwise, the player who executes the last warning also executes the warning action.
  103.   actions_execute_as_console: false
  104.  
  105.   # If enabled, all active warnings will be deactivated after a warning action is executed.
  106.   delete_warnings_after_action: false
  107.  
  108. notify:
  109.   # If enabled, players with the permission 'litebans.notify' or 'litebans.notify.banned_join' will be notified when a banned player tries to join.
  110.   banned_player_join: true
  111.  
  112.   # If enabled, /dupeip output will be shown on join if the player meets certain conditions.
  113.   dupeip_on_join: true
  114.  
  115.   # Notify if the player has a banned account on the same IP.
  116.   dupeip_on_banned_account: true
  117.  
  118.   # If you set this to a lower value, players with X accounts will send dupeip notifications.
  119.   dupeip_on_join_threshold: 999999
  120.  
  121.   # Log all notifications to the console?
  122.   notify_console: true
  123.  
  124. exempt:
  125.   enable: true
  126.   # By default, the first loaded world is used for permission checks.
  127.   permission_world: default
  128.  
  129.   # Permission groups that are exempt from bans, mutes, warnings, and kicks.
  130.   exempt_groups: []
  131.  
  132.   # Players who are exempt from bans, mutes, warnings, and kicks.
  133.   # Format: <name/UUID>[:type]
  134.   # Type can be ban, mute, warning, or kick.
  135.   # Example:
  136.   # exempt_players: ['Player', 'Player:kick', 'Player2']
  137.   exempt_players: []
  138.  
  139. geoip:
  140.   enable: false
  141.   # Anyone from these locations will not be able to join.
  142.   # A full list of countries that can be blacklisted:
  143.   # https://dev.maxmind.com/geoip/legacy/codes/iso3166/
  144.   # You can use /geoip on any IP address. The countries returned from this command can be directly added to the blacklist, for example, "United States".
  145.   # The configuration includes "Anonymous Proxy" which matches a few open proxies and high profile VPNs according to the GeoLite2 database.
  146.   # This may block some proxies, but it's not completely reliable as a proxy blocking solution.
  147.   blacklist: ['Anonymous Proxy']
  148.   download:
  149.     # Download links for the API and database. They are downloaded to the 'plugins/LiteBans/geoip' folder.
  150.     # You shouldn't need to change these, but if it isn't working, you can search for these files.
  151.     api:
  152.     - https://repo1.maven.org/maven2/com/maxmind/geoip2/geoip2/2.1.0/geoip2-2.1.0.jar
  153.     - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.4.3/jackson-databind-2.4.3.jar
  154.     - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-core/2.4.3/jackson-core-2.4.3.jar
  155.     - https://repo1.maven.org/maven2/com/maxmind/db/maxmind-db/1.0.0/maxmind-db-1.0.0.jar
  156.     - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.4.3/jackson-annotations-2.4.3.jar
  157.     # Will be extracted and saved as 'GeoLite2-Country.mmdb'.
  158.     db: https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.mmdb.gz
  159.  
  160. import:
  161.   # You can import from: MaxBans/Ultrabans/BanHammer/BanManagerv4/BanManagerv5/BungeeAdminTools/LiteBans/Vanilla.
  162.   # Vanilla means importing from banned-players.json, which is also used by Essentials.
  163.   from: maxbans
  164.  
  165.   # If enabled, importing will be done from a SQLite database instead of a MySQL database.
  166.   # You can ignore this if importing from banned-players.json.
  167.   sqlite: true
  168.  
  169.   # SQLite file locations:
  170.   #  MaxBans: plugins/MaxBans/bans.db
  171.   #  Ultrabans: plugins/Ultrabans/banlist.db
  172.   #  BanHammer: plugins/BanHammer/BanHammer.db
  173.   #  LiteBans: plugins/LiteBans/litebans.sqlite
  174.   sqlite_file: plugins/MaxBans/bans.db
  175.  
  176.   import_ipbans: true
  177.   ## MySQL import settings ##
  178.   import_mysql_address: localhost:3306
  179.   import_mysql_database: maxbans
  180.   import_mysql_username: ''
  181.   import_mysql_password: ''
  182.  
  183. # Use display names?
  184. # This means that when moderators and punished players change their name using /nick,
  185. # this name will be used in broadcasts and other messages instead of their regular name.
  186. use_display_names: false
  187.  
  188. # Instead of "CONSOLE", this name will be used to represent the console.
  189. console_sender_name: Console
  190.  
  191. # Players in this list will not be shown in /dupeip output. UUIDs can also be specified.
  192. hidden_dupeip_players: []
  193.  
  194. # A player cannot be warned again while they are on cooldown.
  195. # This prevents two moderators from warning the same player for the same reason.
  196. warning_cooldown: 30
  197.  
  198. # If enabled, online player names will be auto-completed.
  199. # Example: /ban Pl -> /ban Player
  200. autocomplete_online_player_names: false
  201.  
  202. # This allows /dupeip and /ipreport to scan every single IP address that a player has ever joined with.
  203. # If set to false, it will only scan the last IP address.
  204. dupeip_scan_all_ips: false
  205.  
  206. # /ipreport will not show accounts that have no other players attached by default.
  207. ipreport_minimum_accounts: 1
  208.  
  209. # If disabled, all previous IP addresses will be recorded, allowing /iphistory to work.
  210. # It is not recommended to disable this for SQLite databases.
  211. delete_previous_history: true
  212.  
  213. # If enabled (default), all previous login history will be unbanned when unbanning a player.
  214. unban_all_history: true
  215.  
  216. # This is the amount of bans shown on each page for /banlist.
  217. # Note that ban entries can span 2-3 lines.
  218. banlist_bans_per_page: 5
  219.  
  220. # Only show active bans for /banlist?
  221. banlist_show_active_only: false
  222.  
  223. # If enabled, AuthMe will be detected and IP history will only be added after a player has successfully logged in.
  224. support_authme: true
  225.  
  226. lockdown:
  227.   # If enabled, /lockdown will continue after restarts.
  228.   persist_enabled: true
  229.  
  230. debug_level: 0
  231.  
  232. # This forces most commands registered by LiteBans to be handled by LiteBans.
  233. # Set it to false if you want another plugin to override a LiteBans command.
  234. # This won't work for commands used from the console.
  235. force_command_override: false
  236.  
  237. # If enabled, this performs an additional two database queries on each join
  238. # in order to provide case-insensitive name bans.
  239. ban_names: false
  240.  
  241. # If a kick message contains any of these, it will not be added to the database.
  242. # You can add '' (empty string) to this list if you don't want any kicks to be added to the database.
  243. ignored_kick_messages: ['restarting']
  244.  
  245. # This option controls how often notifications are sent from a single player.
  246. # When a player tries to join when banned or talk while muted,
  247. # you won't see any more messages from them for a short while.
  248. notification_throttle_ticks: 12000
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top