Bungee Server Litebans Config

Download Raw Clone


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

Raw paste data: