Advertisement
Guest User

Untitled

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