Advertisement
Guest User

Untitled

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