Advertisement
Guest User

Litebans file

a guest
Sep 9th, 2018
438
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 13.58 KB | None | 0 0
  1. # LiteBans config.yml generated by version 2.3.7
  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: false
  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 (or group of instances) and can be updated at any time.
  24. # If you need per-server bans, you have to change server_name on all instances
  25. # The "$serverScope" and "$serverOrigin" variables can be used in messages.
  26. # Maximum length is 32 characters.
  27. server_name: 'litebans'
  28.  
  29. # This option decides which server(s) will be affected in commands by default.
  30. default_server_scope: '*'
  31.  
  32. sql:
  33. # H2, MySQL, MariaDB, and PostgreSQL are supported database drivers.
  34. driver: H2
  35.  
  36. ## MySQL/PostgreSQL settings ##
  37. # If using H2, the database will be stored in the LiteBans plugin folder,
  38. # and most of these settings won't apply.
  39.  
  40. # Database server address.
  41. address: localhost:3306
  42.  
  43. # Database name, username and password.
  44. database: 'litebans'
  45. username: ''
  46. password: ''
  47.  
  48. table_prefix: 'litebans_'
  49.  
  50. # LiteBans utilizes connection pooling for extra performance and reliability.
  51. # min_connections: Minimum amount of pooled connections.
  52. # max_connections: Maximum amount of pooled connections. See: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
  53. # timeout: Connection timeout.
  54. # idle_timeout: Maximum amount of time a pooled connection can remain idle before it is closed for inactivity.
  55. pool:
  56. min_connections: 1
  57. max_connections: 10
  58. timeout: 30 seconds
  59. idle_timeout: 1 minute
  60.  
  61. # Database engine. Only applies to MySQL.
  62. engine: InnoDB
  63.  
  64. options: 'useSSL=false'
  65.  
  66. # Format: <name>:<class>[:URL:version]
  67. # SQLite is only included here for backwards compatibility, it is no longer supported (use H2 instead).
  68. drivers:
  69. - version:1
  70. - 'mysql:com.mysql.jdbc.Driver:https://repo1.maven.org/maven2/mysql/mysql-connector-java/{}/mysql-connector-java-{}.jar:8.0.11'
  71. - 'pgsql:org.postgresql.Driver:https://repo1.maven.org/maven2/org/postgresql/postgresql/{}/postgresql-{}.jar:9.4-1201-jdbc41'
  72. - 'mariadb:org.mariadb.jdbc.Driver:https://repo1.maven.org/maven2/org/mariadb/jdbc/mariadb-java-client/{}/mariadb-java-client-{}.jar:2.0.3'
  73. - 'sqlite:org.sqlite.JDBC:https://repo1.maven.org/maven2/org/xerial/sqlite-jdbc/{}/sqlite-jdbc-{}.jar:3.8.11.1'
  74. - 'h2:org.h2.Driver:https://repo1.maven.org/maven2/com/h2database/h2/{}/h2-{}.jar:1.4.196'
  75.  
  76. durations:
  77. # The highest limit matched by permissions will be used for duration limits.
  78. # If a player has "litebans.group.unlimited", they will bypass these.
  79. Helper:
  80. permission: litebans.group.helper
  81. tempban: 0 days
  82. tempmute: 6 hours
  83. JrMod:
  84. permission: litebans.group.jrmod
  85. tempban: 0 days
  86. tempmute: 1 day
  87. Mod:
  88. permission: litebans.group.mod
  89. tempban: 1 month
  90. tempmute: 1 week
  91. SrMod:
  92. permission: litebans.group.srmod
  93. tempban: 3 months
  94. tempmute: 1 month
  95. Admin:
  96. permission: litebans.group.admin
  97. tempban: 6 months
  98. tempmute: 3 months
  99. SrAdmin:
  100. permission: litebans.group.sradmin
  101. tempban: 12 months
  102. tempmute: 6 months
  103. Owner:
  104. permission: litebans.group.owner
  105. tempban: 12 months
  106. tempmute: 12 months
  107.  
  108. # If true, players will not get an error when using a duration higher than the configured limit.
  109. # The duration will be rounded down to the maximum duration instead.
  110. round_down: true
  111.  
  112. mutes:
  113. enabled: true
  114.  
  115. # All of these commands can not be used while muted.
  116. command_blacklist:
  117. - /me
  118. - /say
  119. - /tell
  120. - /whisper
  121. - /reply
  122. - /pm
  123. - /message
  124. - /msg
  125. - /emsg
  126. - /epm
  127. - /etell
  128. - /ewhisper
  129. - /w
  130. - /m
  131. - /t
  132. - /r
  133. - /mail send
  134. # This command blacklist specifically applies to players who are affected by /mutechat.
  135. mutechat_command_blacklist:
  136. - /me
  137. - /say
  138. # If enabled, muted players cannot use commands containing ":", for example: "/minecraft:me".
  139. prevent_bypass: true
  140.  
  141. # If enabled, a ban or mute reason must be provided, otherwise players will get an error.
  142. # When set to false, "default_ban_reason" and "default_mute_reason" in messages.yml are used as reasons when no reason is provided.
  143. require_ban_mute_reason: false
  144.  
  145. warnings:
  146. # Warnings will expire after this duration has passed.
  147. expire_after: 3 days
  148.  
  149. # Warning actions.
  150. # Format: <amount>[+]:<action>
  151. # If '+' is provided after the amount, the action will execute if the player has that amount of warnings or more.
  152. actions:
  153. - '2:/kick -s:$silent $player Final warning: $reason'
  154. - '3:/tempban -s:$silent $player 1 day Max warnings reached: $list'
  155.  
  156. # If enabled, the console will execute warning actions.
  157. # Otherwise, the player who executes the last warning also executes the warning action.
  158. actions_execute_as_console: true
  159.  
  160. # If enabled, all active warnings will be deactivated after a warning action is executed.
  161. delete_warnings_after_action: false
  162.  
  163. notify:
  164. # If enabled, players with the permission 'litebans.notify' or 'litebans.notify.banned_join' will be notified when a banned player tries to join.
  165. banned_player_join: true
  166.  
  167. # If enabled, /dupeip output will be shown on join if the player meets certain conditions.
  168. dupeip_on_join: true
  169.  
  170. # Notify if the player has a banned account on the same IP.
  171. dupeip_on_banned_account: true
  172.  
  173. # If enabled, muted accounts will be detected with /dupeip.
  174. # 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.
  175. dupeip_show_muted_accounts: false
  176.  
  177. # If you set this to a lower value, players with X accounts will send dupeip notifications.
  178. dupeip_on_join_threshold: 3
  179.  
  180. # Log all notifications to the console?
  181. notify_console: true
  182.  
  183. exempt:
  184. enable: true
  185. # By default, the first loaded world is used for permission checks.
  186. permission_world: default
  187.  
  188. # Permission groups that are exempt from bans, mutes, warnings, and kicks.
  189. exempt_groups: []
  190.  
  191. # Players who are exempt from bans, mutes, warnings, and kicks.
  192. # Format: <name/UUID>[:type]
  193. # Type can be ban, mute, warning, or kick. (All types apply if not specified)
  194. # Example:
  195. # exempt_players: ['Player', 'Player2', 'Player3', 'Player4:mute']
  196. exempt_players: []
  197.  
  198. geoip:
  199. enable: false
  200. # Anyone from these locations will not be able to join.
  201. # A full list of countries that can be blacklisted:
  202. # https://dev.maxmind.com/geoip/legacy/codes/iso3166/
  203. # Example:
  204. # blacklist: ['Australia', 'Brazil', 'Canada', 'Denmark']
  205. blacklist: []
  206.  
  207. # If the whitelist is not empty, all countries which are not found in the list will be blocked.
  208. whitelist: []
  209. download:
  210. # Download links for the API and database, which are downloaded to the 'plugins/LiteBans/geoip' folder.
  211. # You shouldn't need to change these, but if it isn't working, you can search for these files.
  212. api:
  213. - https://repo1.maven.org/maven2/com/maxmind/geoip2/geoip2/2.1.0/geoip2-2.1.0.jar
  214. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.4.3/jackson-databind-2.4.3.jar
  215. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-core/2.4.3/jackson-core-2.4.3.jar
  216. - https://repo1.maven.org/maven2/com/maxmind/db/maxmind-db/1.0.0/maxmind-db-1.0.0.jar
  217. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.4.3/jackson-annotations-2.4.3.jar
  218. # Will be extracted and saved as 'GeoLite2-Country.mmdb'.
  219. db: https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.mmdb.gz
  220.  
  221. # After configuring import options, run "/litebans import start" to begin the import.
  222. # The import process occurs while the server is running, no downtime is required.
  223. import:
  224. # You can import from: MaxBans, Ultrabans, BanHammer, BanManagerv4, BanManagerv5, BungeeAdminTools, AdvancedBan(MySQL only), LiteBans, Vanilla.
  225. # Vanilla means importing from banned-players.json, which is also used by Essentials.
  226. from: vanilla
  227.  
  228. # If enabled, importing will be done from a SQLite database instead of a MySQL database.
  229. # You can ignore this if importing from banned-players.json.
  230. # If importing from LiteBans, H2 will be used instead of SQLite.
  231. sqlite: true
  232.  
  233. # SQLite file locations:
  234. # MaxBans: plugins/MaxBans/bans.db
  235. # Ultrabans: plugins/Ultrabans/banlist.db
  236. # BanHammer: plugins/BanHammer/BanHammer.db
  237. # LiteBans: plugins/LiteBans/litebans.sqlite (legacy)
  238. sqlite_file: plugins/MaxBans/bans.db
  239.  
  240. import_ipbans: true
  241. ## MySQL import settings ##
  242. import_mysql_address: localhost:3306
  243. import_mysql_database: vanilla
  244. import_mysql_username: ''
  245. import_mysql_password: ''
  246.  
  247. # Use display names?
  248. # This means that when moderators and punished players change their name using /nick,
  249. # this name will be used in broadcasts and other messages instead of their regular name.
  250. # The BungeeCord version of the plugin cannot detect Spigot-side display names.
  251. use_display_names: false
  252.  
  253. # Instead of "CONSOLE", this name will be used to represent the console.
  254. console_sender_name: Animus
  255.  
  256. # Players in this list will not be shown in /dupeip or /alts output.
  257. # Names, UUIDs and IP addresses can be specified.
  258. hidden_dupeip_players: [Im_Just_Filip]
  259.  
  260.  
  261. # Moderators cannot use /ban or /warn twice within a specific time frame.
  262. # Additionally, the same player cannot be punished twice.
  263. # This can be bypassed with: "litebans.cooldown.bypass", "litebans.cooldown.bypass.ban", "litebans.cooldown.bypass.warn"
  264. ban_cooldown: 0
  265. warning_cooldown: 5
  266.  
  267. # If enabled, online player names will be auto-completed.
  268. # Example: /ban Pl -> /ban Player
  269. autocomplete_online_player_names: true
  270.  
  271. # This allows /dupeip and /ipreport to scan every single IP address that a player has ever joined with. (Multiple IP scanning)
  272. # If set to false, only the player's last IP address will be scanned.
  273. # (This option requires `delete_previous_history: false`)
  274. dupeip_scan_all_ips: true
  275.  
  276. # If disabled, all previous IP addresses will be recorded, allowing /iphistory to work.
  277. delete_previous_history: false
  278.  
  279. # /ipreport will not show accounts that have no other players attached by default.
  280. ipreport_minimum_accounts: 1
  281.  
  282.  
  283. # If enabled, all previous login history will be unbanned when unbanning a player.
  284. unban_all_history: false
  285.  
  286. # This is the amount of bans shown on each page for /banlist.
  287. # Note that ban entries can span 2-3 lines.
  288. banlist_bans_per_page: 5
  289.  
  290. # Only show active bans for /banlist?
  291. banlist_show_active_only: true
  292.  
  293. # If enabled, AuthMe will be detected and IP history will only be added after a player has successfully logged in.
  294. # This option will only work under Spigot, since AuthMe is a Spigot plugin.
  295. support_authme: true
  296.  
  297. lockdown:
  298. # If enabled, /lockdown will continue after restarts.
  299. persist_enabled: true
  300.  
  301. debug_level: 0
  302.  
  303. # If enabled, LiteBans performs an additional database query on login to provide case-insensitive name bans.
  304. ban_names: false
  305.  
  306. # If a kick message contains any of these, it will not be added to the database.
  307. # You can set this list to [''] if you don't want any kicks to be added to the database.
  308. ignored_kick_messages: ['']
  309.  
  310. # This option controls how often notifications are sent from a single player.
  311. # When a player tries to join when banned or talk while muted,
  312. # you won't see any more messages from them for a short while.
  313. notification_throttle_ticks: 12000
  314.  
  315. # If enabled, LiteBans will use the database server's timezone.
  316. use_database_time: true
  317.  
  318. # If enabled, the plugin will notify you when an update is available.
  319. update_check: true
  320.  
  321. # If enabled, players will be checked for bans after they have joined. (Spigot only)
  322. check_after_join: false
  323.  
  324. # If enabled, ProtocolLib will be detected and chat events will be cancelled before they can be processed by any other plugins.
  325. # This can help prevent plugin conflicts which allow muted players to chat.
  326. # This option will only work under Spigot, since ProtocolLib is a Spigot plugin.
  327. use_protocollib: true
  328.  
  329. # This option controls the behaviour of the "-N" flag. This flag prevents active bans/mutes from being overridden.
  330. # If enabled, the "-N" flag will only prevent bans from being overridden if the active ban has a lower duration.
  331. override_lower_duration: true
  332.  
  333. # This option allows you to disable recording IP history on specific servers under BungeeCord.
  334. # Example: ignored_history_servers: ['Lobby']
  335. ignored_history_servers: []
  336.  
  337. # If enabled, the local system timezone will be used.
  338. # UTC time will be stored in the database, but dates will be formatted using the timezone offset.
  339. use_timezone: true
  340.  
  341. # This option controls how often the database is polled for sync data (cross-server punishments, kicks, notifications).
  342. sync_poll_ticks: 20
  343.  
  344. # If this is set above 0, the plugin will skip polling up to N times while no players are online.
  345. sync_poll_skip: 5
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement