Advertisement
Guest User

Untitled

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