SHARE
TWEET

Untitled

a guest Jun 18th, 2017 84 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 option has no effect if the plugin is running directly under BungeeCord.
  4. bungeecord: true
  5.  
  6. # If this option is enabled and the server is connected to a remote database (e.g. MySQL),
  7. # LiteBans will synchronize across all servers connected to that database with sync enabled.
  8. sync: true
  9.  
  10. # If enabled, broadcasts will be synchronized.
  11. sync_broadcasts: true
  12.  
  13. # If enabled, notifications will be synchronized.
  14. sync_notifications: true
  15.  
  16. # If enabled, dupeip notifications will be synchronized.
  17. # This will appear multiple times if a player joins multiple servers, so you might want to leave this disabled.
  18. sync_dupeip_notifications: false
  19.  
  20. # The server name is an identifier used in cross-server synchronization.
  21. # It represents a single plugin instance and can be updated at any time.
  22. # If multiple servers have the same server name, they will be called "litebans-1", "litebans-2", etc.
  23. # The "$server" variable can be used in broadcast messages.
  24. server_name: 'litebans'
  25.  
  26. sql:
  27.   # H2, MySQL, MariaDB, and PostgreSQL are supported database drivers.
  28.   driver: H2
  29.  
  30.   ## MySQL/PostgreSQL settings ##
  31.   # If using H2, the database will be stored in the LiteBans plugin folder,
  32.   # and most of these settings won't apply.
  33.  
  34.   # Database server address.
  35.   address: localhost:3306
  36.  
  37.   # Database name, username and password.
  38.   database: 'litebans'
  39.   username: ''
  40.   password: ''
  41.  
  42.   table_prefix: 'litebans_'
  43.  
  44.   # LiteBans utilizes connection pooling for extra performance and reliability.
  45.   # min_connections: Minimum amount of pooled connections.
  46.   # max_connections: Maximum amount of pooled connections. See: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
  47.   # timeout: Connection timeout.
  48.   # idle_timeout: Maximum amount of time a pooled connection can remain idle before it is closed for inactivity.
  49.   pool:
  50.     min_connections: 1
  51.     max_connections: 10
  52.     timeout: 30 seconds
  53.     idle_timeout: 1 minute
  54.  
  55.   # Database engine. Only applies to MySQL.
  56.   engine: InnoDB
  57.  
  58.   # Format: <name>:<class>[:URL]
  59.   drivers:
  60.   - mysql:com.mysql.jdbc.Driver:https://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.37/mysql-connector-java-5.1.37.jar
  61.   - pgsql:org.postgresql.Driver:https://repo1.maven.org/maven2/org/postgresql/postgresql/9.4-1201-jdbc41/postgresql-9.4-1201-jdbc41.jar
  62.   - 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
  63.   - sqlite:org.sqlite.JDBC:https://repo1.maven.org/maven2/org/xerial/sqlite-jdbc/3.8.11.1/sqlite-jdbc-3.8.11.1.jar
  64.   - h2:org.h2.Driver:https://repo1.maven.org/maven2/com/h2database/h2/1.4.188/h2-1.4.188.jar
  65.  
  66. durations:
  67.   # Can be bypassed with the permission "litebans.unlimited.ban"
  68.   tempban_max: 7 days
  69.   # Can be bypassed with the permission "litebans.unlimited.mute"
  70.   mute_max: 1 day
  71.   # If true, players will not get an error when using a duration higher than the configured limit.
  72.   # The duration will be rounded down to the maximum duration instead.
  73.   round_down: true
  74.  
  75. mutes:
  76.   enabled: true
  77.  
  78.   # All of these commands can not be used while muted.
  79.   command_blacklist:
  80.   - /me
  81.   - /say
  82.   - /tell
  83.   - /whisper
  84.   - /reply
  85.   - /pm
  86.   - /msg
  87.   - /emsg
  88.   - /epm
  89.   - /etell
  90.   - /ewhisper
  91.   - /w
  92.   - /m
  93.   - /t
  94.   - /r
  95.   mutechat_command_blacklist:
  96.   - /me
  97.   - /say
  98.   # If enabled, muted players cannot use commands containing ":", for example: "/minecraft:me".
  99.   prevent_bypass: true
  100.  
  101. # If set, a ban or mute reason must be provided, otherwise players will get an error.
  102. # When set to false, "default_ban_reason" and "default_mute_reason" in messages.yml are used as reasons when no reason is provided.
  103. require_ban_mute_reason: false
  104.  
  105. warnings:
  106.   # Warnings will expire after this duration has passed.
  107.   expire_after: 7 days
  108.  
  109.   # Warning actions.
  110.   # Format: <amount>[+]:<action>
  111.   # If '+' is provided after the amount, the action will execute if the player has that amount of warnings or more.
  112.   actions:
  113.   - '3:/kick -s:$silent $player Final warning: $reason'
  114.   - '4:/tempban -s:$silent $player 1 day Reached 4 warnings: $list'
  115.  
  116.   # If enabled, the console will execute warning actions.
  117.   # Otherwise, the player who executes the last warning also executes the warning action.
  118.   actions_execute_as_console: false
  119.  
  120.   # If enabled, all active warnings will be deactivated after a warning action is executed.
  121.   delete_warnings_after_action: false
  122.  
  123. notify:
  124.   # If enabled, players with the permission 'litebans.notify' or 'litebans.notify.banned_join' will be notified when a banned player tries to join.
  125.   banned_player_join: true
  126.  
  127.   # If enabled, /dupeip output will be shown on join if the player meets certain conditions.
  128.   dupeip_on_join: true
  129.  
  130.   # Notify if the player has a banned account on the same IP.
  131.   dupeip_on_banned_account: true
  132.  
  133.   # If you set this to a lower value, players with X accounts will send dupeip notifications.
  134.   dupeip_on_join_threshold: 9999999
  135.  
  136.   # Log all notifications to the console?
  137.   notify_console: true
  138.  
  139. exempt:
  140.   enable: true
  141.   # By default, the first loaded world is used for permission checks.
  142.   permission_world: default
  143.  
  144.   # Permission groups that are exempt from bans, mutes, warnings, and kicks.
  145.   exempt_groups: []
  146.  
  147.   # Players who are exempt from bans, mutes, warnings, and kicks.
  148.   # Format: <name/UUID>[:type]
  149.   # Type can be ban, mute, warning, or kick.
  150.   # Example:
  151.   # exempt_players: ['Player', 'Player:kick', 'Player2']
  152.   exempt_players: []
  153.  
  154. geoip:
  155.   enable: false
  156.   # Anyone from these locations will not be able to join.
  157.   # A full list of countries that can be blacklisted:
  158.   # https://dev.maxmind.com/geoip/legacy/codes/iso3166/
  159.   # 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".
  160.   blacklist: []
  161.   download:
  162.     # Download links for the API and database. They are downloaded to the 'plugins/LiteBans/geoip' folder.
  163.     # You shouldn't need to change these, but if it isn't working, you can search for these files.
  164.     api:
  165.     - https://repo1.maven.org/maven2/com/maxmind/geoip2/geoip2/2.1.0/geoip2-2.1.0.jar
  166.     - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.4.3/jackson-databind-2.4.3.jar
  167.     - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-core/2.4.3/jackson-core-2.4.3.jar
  168.     - https://repo1.maven.org/maven2/com/maxmind/db/maxmind-db/1.0.0/maxmind-db-1.0.0.jar
  169.     - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.4.3/jackson-annotations-2.4.3.jar
  170.     # Will be extracted and saved as 'GeoLite2-Country.mmdb'.
  171.     db: https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.mmdb.gz
  172.  
  173. import:
  174.   # You can import from: MaxBans/Ultrabans/BanHammer/BanManagerv4/BanManagerv5/BungeeAdminTools/LiteBans/Vanilla.
  175.   # Vanilla means importing from banned-players.json, which is also used by Essentials.
  176.   from: maxbans
  177.  
  178.   # If enabled, importing will be done from a SQLite database instead of a MySQL database.
  179.   # You can ignore this if importing from banned-players.json.
  180.   # If importing from LiteBans, H2 will be used instead of SQLite.
  181.   sqlite: true
  182.  
  183.   # SQLite file locations:
  184.   #  MaxBans: plugins/MaxBans/bans.db
  185.   #  Ultrabans: plugins/Ultrabans/banlist.db
  186.   #  BanHammer: plugins/BanHammer/BanHammer.db
  187.   #  LiteBans: plugins/LiteBans/litebans.sqlite (legacy)
  188.   sqlite_file: plugins/MaxBans/bans.db
  189.  
  190.   import_ipbans: true
  191.   ## MySQL import settings ##
  192.   import_mysql_address: localhost:3306
  193.   import_mysql_database: maxbans
  194.   import_mysql_username: ''
  195.   import_mysql_password: ''
  196.  
  197. # Use display names?
  198. # This means that when moderators and punished players change their name using /nick,
  199. # this name will be used in broadcasts and other messages instead of their regular name.
  200. # The BungeeCord version of the plugin cannot detect Spigot-side display names.
  201. use_display_names: false
  202.  
  203. # Instead of "CONSOLE", this name will be used to represent the console.
  204. console_sender_name: Console
  205.  
  206. # Players in this list will not be shown in /dupeip output. UUIDs can also be specified.
  207. hidden_dupeip_players: []
  208.  
  209. # A player cannot be warned again while they are on cooldown.
  210. # This prevents two moderators from warning the same player for the same reason.
  211. warning_cooldown: 30
  212.  
  213. # If enabled, online player names will be auto-completed.
  214. # Example: /ban Pl -> /ban Player
  215. autocomplete_online_player_names: false
  216.  
  217. # This allows /dupeip and /ipreport to scan every single IP address that a player has ever joined with.
  218. # If set to false, it will only scan the last IP address.
  219. dupeip_scan_all_ips: false
  220.  
  221. # /ipreport will not show accounts that have no other players attached by default.
  222. ipreport_minimum_accounts: 1
  223.  
  224. # If disabled, all previous IP addresses will be recorded, allowing /iphistory to work.
  225. delete_previous_history: true
  226.  
  227. # If enabled (default), all previous login history will be unbanned when unbanning a player.
  228. unban_all_history: true
  229.  
  230. # This is the amount of bans shown on each page for /banlist.
  231. # Note that ban entries can span 2-3 lines.
  232. banlist_bans_per_page: 5
  233.  
  234. # Only show active bans for /banlist?
  235. banlist_show_active_only: false
  236.  
  237. # If enabled, AuthMe will be detected and IP history will only be added after a player has successfully logged in.
  238. # This option will only work under Spigot, since AuthMe is a Spigot plugin.
  239. support_authme: false
  240.  
  241. lockdown:
  242.   # If enabled, /lockdown will continue after restarts.
  243.   persist_enabled: true
  244.  
  245. debug_level: 0
  246.  
  247. # If enabled, this performs an additional two database queries on each join
  248. # in order to provide case-insensitive name bans.
  249. ban_names: false
  250.  
  251. # If a kick message contains any of these, it will not be added to the database.
  252. # You can set this list to [''] if you don't want any kicks to be added to the database.
  253. ignored_kick_messages: ['restarting']
  254.  
  255. # This option controls how often notifications are sent from a single player.
  256. # When a player tries to join when banned or talk while muted,
  257. # you won't see any more messages from them for a short while.
  258. notification_throttle_ticks: 12000
  259.  
  260. # If enabled, LiteBans will use the database server's time rather than the system time.
  261. use_database_time: false
  262.  
  263. # If enabled, the plugin will notify you when an update is available.
  264. update_check: true
  265.  
  266. # If enabled, players will be checked for bans after they have joined. (Spigot only)
  267. check_after_join: false
  268.  
  269. # If enabled, ProtocolLib will be detected and chat events will be cancelled before they can be processed by any other plugins.
  270. # This can help prevent plugin conflicts which allow muted players to chat.
  271. # This option will only work under Spigot, since ProtocolLib is a Spigot plugin.
  272. use_protocollib: true
  273.  
  274. # This option controls the behaviour of the "-N" flag. This flag prevents active bans/mutes from being overridden.
  275. # If enabled, the "-N" flag will only prevent bans from being overridden if the active ban has a lower duration.
  276. override_lower_duration: true
  277.  
  278. # This option allows you to disable recording IP history on specific servers under BungeeCord.
  279. # Example: ignored_history_servers: ['Lobby']
  280. ignored_history_servers: []
  281.  
  282. # If enabled, the local system timezone will be used.
  283. # UTC time will be stored in the database, but dates will be formatted using the timezone offset.
  284. use_timezone: true
  285.  
  286. # This option controls how often the database is polled for sync data (cross-server punishments, kicks, notifications).
  287. sync_poll_ticks: 20
  288.  
  289. # If this is set above 0, the plugin will skip polling up to N times while no players are online.
  290. sync_poll_skip: 5
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