Advertisement
SergOmarov

Untitled

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