Advertisement
Guest User

Untitled

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