API tools faq
paste
Advertisement
Guest User

adfadf

a guest
Mar 22nd, 2016
90
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 18.00 KB | None | 0 0
raw download clone embed print report
  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 has no effect if the plugin is running under BungeeCord itself.
  5. bungeecord: false
  6.  
  7. sql:
  8. # MySQL, PostgreSQL(pgsql), SQLite, and H2 are supported database drivers.
  9. driver: sqlite
  10.  
  11. ## MySQL/PostgreSQL settings ##
  12. # If using SQLite/H2, the database will be stored in the LiteBans plugin folder,
  13. # and most of these settings won't apply.
  14.  
  15. # Database server address to connect to.
  16. # This can be set to a custom file path if using SQLite/H2.
  17. address: localhost:3306
  18.  
  19. # Database name, username and password
  20. database: litebans
  21. username: ''
  22. password: ''
  23.  
  24. table_prefix: 'litebans_'
  25.  
  26. # Database engine. Only applies to MySQL.
  27. engine: InnoDB
  28.  
  29. # Format: <name>:<class>[:URL]
  30. drivers:
  31. - mysql:com.mysql.jdbc.Driver
  32. - pgsql:org.postgresql.Driver:https://repo1.maven.org/maven2/org/postgresql/postgresql/9.4-1201-jdbc41/postgresql-9.4-1201-jdbc41.jar
  33. - sqlite:org.sqlite.JDBC:https://repo1.maven.org/maven2/org/xerial/sqlite-jdbc/3.8.11.1/sqlite-jdbc-3.8.11.1.jar
  34. - h2:org.h2.Driver:https://repo1.maven.org/maven2/com/h2database/h2/1.4.188/h2-1.4.188.jar
  35.  
  36. durations:
  37. # Can be bypassed with the permission "litebans.unlimited.ban"
  38. tempban_max: 7 days
  39. # Can be bypassed with the permission "litebans.unlimited.mute"
  40. mute_max: 1 day
  41. # If true, players will not get an error when placing bans above the configured limit.
  42. # The duration will be rounded down to the maximum duration instead.
  43. round_down: true
  44.  
  45. mutes:
  46. enabled: true
  47.  
  48. # All of these commands can not be used while muted.
  49. command_blacklist:
  50. - /me
  51. - /say
  52. - /tell
  53. - /whisper
  54. - /reply
  55. - /pm
  56. - /msg
  57. - /emsg
  58. - /epm
  59. - /etell
  60. - /ewhisper
  61. - /w
  62. - /m
  63. - /t
  64. - /r
  65. # If enabled, muted players cannot use commands containing ":", for example: "/minecraft:me".
  66. prevent_bypass: true
  67.  
  68. sync_ticks: 0
  69.  
  70. # All online players will be re-checked for bans per interval when this is set.
  71. # This only makes sense in a multi-server configuration,
  72. # or if you're otherwise manipulating the database while the server is running.
  73. ban_sync_ticks: 0
  74.  
  75. warnings:
  76. # Warnings will expire after this duration has passed.
  77. expire_after: 7 days
  78.  
  79. # Warning actions.
  80. # Format: <amount>[+]:<action>
  81. # If '+' is provided after the amount, the action will execute if the player has that amount of warnings or more.
  82. actions:
  83. - '3:/kick -s:$silent $player Final warning: $reason'
  84. - '4:/tempban -s:$silent $player 1 day Reached 4 warnings: $list'
  85.  
  86. # If enabled, the console will execute warning actions.
  87. # Otherwise, the player who executes the last warning also executes the warning action.
  88. actions_execute_as_console: false
  89.  
  90. # If enabled, all active warnings will be deactivated after a warning action is executed.
  91. delete_warnings_after_action: false
  92.  
  93. notify:
  94. # If enabled, players with the permission 'litebans.notify' or 'litebans.notify.banned_join' will be notified when a banned player tries to join.
  95. banned_player_join: true
  96.  
  97. # If enabled, /dupeip output will be shown on join if the player meets certain conditions.
  98. dupeip_on_join: true
  99.  
  100. # Notify if the player has a banned account on the same IP.
  101. dupeip_on_banned_account: true
  102.  
  103. # If you set this to a lower value, players with X accounts will send dupeip notifications.
  104. dupeip_on_join_threshold: 9999
  105.  
  106. # Log all notifications to the console?
  107. notify_console: true
  108.  
  109. exempt:
  110. enable: true
  111. # By default, the first loaded world is used for permission checks.
  112. permission_world: default
  113.  
  114. # Permission groups that are exempt from bans, mutes, warnings, and kicks.
  115. exempt_groups: []
  116. # Players who are exempt from bans, mutes, warnings, and kicks.
  117. # Format: <name/UUID>[:type]
  118. # Type can be ban, mute, warning, or kick.
  119. # Examples: 'Player', 'Player:kick'
  120. exempt_players: []
  121.  
  122. geoip:
  123. enable: false
  124. # Anyone from these locations will not be able to join.
  125. # A full list of countries that can be blacklisted:
  126. # https://dev.maxmind.com/geoip/legacy/codes/iso3166/
  127. # 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".
  128. # The configuration includes "Anonymous Proxy" which matches a few open proxies and high profile VPNs according to the GeoLite2 database.
  129. # This may block some proxies, but it's not completely reliable as a proxy blocking solution.
  130. blacklist: ['Anonymous Proxy']
  131. download:
  132. # Download links for the API and database. They are downloaded to the 'plugins/LiteBans/geoip' folder.
  133. # You shouldn't need to change these, but if it isn't working, you can search for these files.
  134. api:
  135. - https://repo1.maven.org/maven2/com/maxmind/geoip2/geoip2/2.1.0/geoip2-2.1.0.jar
  136. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.4.3/jackson-databind-2.4.3.jar
  137. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-core/2.4.3/jackson-core-2.4.3.jar
  138. - https://repo1.maven.org/maven2/com/maxmind/db/maxmind-db/1.0.0/maxmind-db-1.0.0.jar
  139. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.4.3/jackson-annotations-2.4.3.jar
  140. # Will be extracted and saved as 'GeoLite2-Country.mmdb'.
  141. db: https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.mmdb.gz
  142.  
  143. import:
  144. # You can import from: MaxBans/Ultrabans/BanHammer/BanManagerv4/BanManagerv5/BungeeAdminTools/LiteBans/Vanilla.
  145. # Vanilla means importing from banned-players.json, which is also used by Essentials.
  146. from: maxbans
  147.  
  148. # If enabled, importing will be done from a SQLite database instead of a MySQL database.
  149. # You can ignore this if importing from banned-players.json.
  150. sqlite: true
  151.  
  152. # SQLite file locations:
  153. # MaxBans: plugins/MaxBans/bans.db
  154. # Ultrabans: plugins/Ultrabans/banlist.db
  155. # BanHammer: plugins/BanHammer/BanHammer.db
  156. # LiteBans: plugins/LiteBans/litebans.sqlite
  157. sqlite_file: plugins/MaxBans/bans.db
  158.  
  159. import_ipbans: true
  160. ## MySQL import settings ##
  161. import_mysql_address: localhost:3306
  162. import_mysql_database: maxbans
  163. import_mysql_username: ''
  164. import_mysql_password: ''
  165.  
  166. # Use display names?
  167. # This means that when moderators and punished players change their name using /nick,
  168. # this name will be used in broadcasts and other messages instead of their regular name.
  169. use_display_names: false
  170.  
  171. # Instead of CONSOLE, this name will be used to represent the console.
  172. console_sender_name: Console
  173.  
  174. # Players in this list will not show up in /dupeip output. UUIDs can also be specified.
  175. hidden_dupeip_players: []
  176.  
  177. # A player cannot be warned again while they are on cooldown.
  178. # This prevents two moderators from warning the same player for the same reason.
  179. warning_cooldown: 30
  180.  
  181. # If enabled, online player names will be auto-completed.
  182. # Example: /ban Pl -> /ban Player
  183. autocomplete_online_player_names: false
  184.  
  185. # This allows /dupeip and /ipreport to scan every single IP address that a player has ever joined with.
  186. # If set to false, it will only scan the last IP address.
  187. dupeip_scan_all_ips: false
  188.  
  189. # /ipreport will not show accounts that have no other players attached by default.
  190. ipreport_minimum_accounts: 1
  191.  
  192. # If disabled, all previous IP addresses will be recorded, allowing /iphistory to work.
  193. # It is not recommended to disable this for SQLite databases.
  194. delete_previous_history: true
  195.  
  196. # If enabled (default), all previous login history will be unbanned when unbanning a player.
  197. unban_all_history: true
  198.  
  199. # This is the amount of bans shown on each page for /banlist.
  200. # Note that ban entries can span 2-3 lines.
  201. banlist_bans_per_page: 5
  202.  
  203. # Only show active bans for /banlist?
  204. banlist_show_active_only: true
  205.  
  206. # If enabled, AuthMe will be detected and IP history will only be added after a player has successfully logged in.
  207. support_authme: true
  208.  
  209. lockdown:
  210. # If enabled, /lockdown will continue after restarts.
  211. persist_enabled: true
  212.  
  213. debug_level: 0
  214.  
  215. # This forces most commands registered by LiteBans to be handled by LiteBans.
  216. # Set it to false if you want another plugin to override a LiteBans command.
  217. # This won't work for commands used from the console.
  218. force_command_override: false
  219.  
  220. # If enabled, this performs an additional two database queries on each join
  221. # in order to provide case-insensitive name bans.
  222. ban_names: false
  223.  
  224. # If a kick message contains any of these, it will not be added to the database.
  225. # You can add '' (empty string) to this list if you don't want any kicks to be added to the database.
  226. ignored_kick_messages: ['restarting']# If bungeecord is set to true, banned players will be kicked from BungeeCord itself.
  227. # (Players will not be kicked to the lobby when they are banned.)
  228. # This will also implicitly set ban_sync_ticks and mutes.sync_ticks if not configured.
  229. # This has no effect if the plugin is running under BungeeCord itself.
  230. bungeecord: false
  231.  
  232. sql:
  233. # MySQL, PostgreSQL(pgsql), SQLite, and H2 are supported database drivers.
  234. driver: sqlite
  235.  
  236. ## MySQL/PostgreSQL settings ##
  237. # If using SQLite/H2, the database will be stored in the LiteBans plugin folder,
  238. # and most of these settings won't apply.
  239.  
  240. # Database server address to connect to.
  241. # This can be set to a custom file path if using SQLite/H2.
  242. address: localhost:3306
  243.  
  244. # Database name, username and password
  245. database: litebans
  246. username: ''
  247. password: ''
  248.  
  249. table_prefix: 'litebans_'
  250.  
  251. # Database engine. Only applies to MySQL.
  252. engine: InnoDB
  253.  
  254. # Format: <name>:<class>[:URL]
  255. drivers:
  256. - mysql:com.mysql.jdbc.Driver
  257. - pgsql:org.postgresql.Driver:https://repo1.maven.org/maven2/org/postgresql/postgresql/9.4-1201-jdbc41/postgresql-9.4-1201-jdbc41.jar
  258. - sqlite:org.sqlite.JDBC:https://repo1.maven.org/maven2/org/xerial/sqlite-jdbc/3.8.11.1/sqlite-jdbc-3.8.11.1.jar
  259. - h2:org.h2.Driver:https://repo1.maven.org/maven2/com/h2database/h2/1.4.188/h2-1.4.188.jar
  260.  
  261. durations:
  262. # Can be bypassed with the permission "litebans.unlimited.ban"
  263. tempban_max: 7 days
  264. # Can be bypassed with the permission "litebans.unlimited.mute"
  265. mute_max: 1 day
  266. # If true, players will not get an error when placing bans above the configured limit.
  267. # The duration will be rounded down to the maximum duration instead.
  268. round_down: true
  269.  
  270. mutes:
  271. enabled: true
  272.  
  273. # All of these commands can not be used while muted.
  274. command_blacklist:
  275. - /me
  276. - /say
  277. - /tell
  278. - /whisper
  279. - /reply
  280. - /pm
  281. - /msg
  282. - /emsg
  283. - /epm
  284. - /etell
  285. - /ewhisper
  286. - /w
  287. - /m
  288. - /t
  289. - /r
  290. # If enabled, muted players cannot use commands containing ":", for example: "/minecraft:me".
  291. prevent_bypass: true
  292.  
  293. sync_ticks: 0
  294.  
  295. # All online players will be re-checked for bans per interval when this is set.
  296. # This only makes sense in a multi-server configuration,
  297. # or if you're otherwise manipulating the database while the server is running.
  298. ban_sync_ticks: 0
  299.  
  300. warnings:
  301. # Warnings will expire after this duration has passed.
  302. expire_after: 3 days
  303.  
  304. # Warning actions.
  305. # Format: <amount>[+]:<action>
  306. # If '+' is provided after the amount, the action will execute if the player has that amount of warnings or more.
  307. actions:
  308. - '3:/kick -s:$silent $player Final warning: $reason'
  309. - '4:/tempban -s:$silent $player 1 day Reached 4 warnings: $list'
  310.  
  311. # If enabled, the console will execute warning actions.
  312. # Otherwise, the player who executes the last warning also executes the warning action.
  313. actions_execute_as_console: false
  314.  
  315. # If enabled, all active warnings will be deactivated after a warning action is executed.
  316. delete_warnings_after_action: false
  317.  
  318. notify:
  319. # If enabled, players with the permission 'litebans.notify' or 'litebans.notify.banned_join' will be notified when a banned player tries to join.
  320. banned_player_join: true
  321.  
  322. # If enabled, /dupeip output will be shown on join if the player meets certain conditions.
  323. dupeip_on_join: true
  324.  
  325. # Notify if the player has a banned account on the same IP.
  326. dupeip_on_banned_account: true
  327.  
  328. # If you set this to a lower value, players with X accounts will send dupeip notifications.
  329. dupeip_on_join_threshold: 9999
  330.  
  331. # Log all notifications to the console?
  332. notify_console: true
  333.  
  334. exempt:
  335. enable: true
  336. # By default, the first loaded world is used for permission checks.
  337. permission_world: default
  338.  
  339. # Permission groups that are exempt from bans, mutes, warnings, and kicks.
  340. exempt_groups: []
  341. # Players who are exempt from bans, mutes, warnings, and kicks.
  342. # Format: <name/UUID>[:type]
  343. # Type can be ban, mute, warning, or kick.
  344. # Examples: 'Player', 'Player:kick'
  345. exempt_players: []
  346.  
  347. geoip:
  348. enable: false
  349. # Anyone from these locations will not be able to join.
  350. # A full list of countries that can be blacklisted:
  351. # https://dev.maxmind.com/geoip/legacy/codes/iso3166/
  352. # 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".
  353. # The configuration includes "Anonymous Proxy" which matches a few open proxies and high profile VPNs according to the GeoLite2 database.
  354. # This may block some proxies, but it's not completely reliable as a proxy blocking solution.
  355. blacklist: ['Anonymous Proxy']
  356. download:
  357. # Download links for the API and database. They are downloaded to the 'plugins/LiteBans/geoip' folder.
  358. # You shouldn't need to change these, but if it isn't working, you can search for these files.
  359. api:
  360. - https://repo1.maven.org/maven2/com/maxmind/geoip2/geoip2/2.1.0/geoip2-2.1.0.jar
  361. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.4.3/jackson-databind-2.4.3.jar
  362. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-core/2.4.3/jackson-core-2.4.3.jar
  363. - https://repo1.maven.org/maven2/com/maxmind/db/maxmind-db/1.0.0/maxmind-db-1.0.0.jar
  364. - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.4.3/jackson-annotations-2.4.3.jar
  365. # Will be extracted and saved as 'GeoLite2-Country.mmdb'.
  366. db: https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.mmdb.gz
  367.  
  368. import:
  369. # You can import from: MaxBans/Ultrabans/BanHammer/BanManagerv4/BanManagerv5/BungeeAdminTools/LiteBans/Vanilla.
  370. # Vanilla means importing from banned-players.json, which is also used by Essentials.
  371. from: maxbans
  372.  
  373. # If enabled, importing will be done from a SQLite database instead of a MySQL database.
  374. # You can ignore this if importing from banned-players.json.
  375. sqlite: true
  376.  
  377. # SQLite file locations:
  378. # MaxBans: plugins/MaxBans/bans.db
  379. # Ultrabans: plugins/Ultrabans/banlist.db
  380. # BanHammer: plugins/BanHammer/BanHammer.db
  381. # LiteBans: plugins/LiteBans/litebans.sqlite
  382. sqlite_file: plugins/MaxBans/bans.db
  383.  
  384. import_ipbans: true
  385. ## MySQL import settings ##
  386. import_mysql_address: localhost:3306
  387. import_mysql_database: maxbans
  388. import_mysql_username: ''
  389. import_mysql_password: ''
  390.  
  391. # Use display names?
  392. # This means that when moderators and punished players change their name using /nick,
  393. # this name will be used in broadcasts and other messages instead of their regular name.
  394. use_display_names: false
  395.  
  396. # Instead of CONSOLE, this name will be used to represent the console.
  397. console_sender_name: Console
  398.  
  399. # Players in this list will not show up in /dupeip output. UUIDs can also be specified.
  400. hidden_dupeip_players: []
  401.  
  402. # A player cannot be warned again while they are on cooldown.
  403. # This prevents two moderators from warning the same player for the same reason.
  404. warning_cooldown: 30
  405.  
  406. # If enabled, online player names will be auto-completed.
  407. # Example: /ban Pl -> /ban Player
  408. autocomplete_online_player_names: false
  409.  
  410. # This allows /dupeip and /ipreport to scan every single IP address that a player has ever joined with.
  411. # If set to false, it will only scan the last IP address.
  412. dupeip_scan_all_ips: false
  413.  
  414. # /ipreport will not show accounts that have no other players attached by default.
  415. ipreport_minimum_accounts: 1
  416.  
  417. # If disabled, all previous IP addresses will be recorded, allowing /iphistory to work.
  418. # It is not recommended to disable this for SQLite databases.
  419. delete_previous_history: true
  420.  
  421. # If enabled (default), all previous login history will be unbanned when unbanning a player.
  422. unban_all_history: true
  423.  
  424. # This is the amount of bans shown on each page for /banlist.
  425. # Note that ban entries can span 2-3 lines.
  426. banlist_bans_per_page: 5
  427.  
  428. # Only show active bans for /banlist?
  429. banlist_show_active_only: true
  430.  
  431. # If enabled, AuthMe will be detected and IP history will only be added after a player has successfully logged in.
  432. support_authme: true
  433.  
  434. lockdown:
  435. # If enabled, /lockdown will continue after restarts.
  436. persist_enabled: true
  437.  
  438. debug_level: 0
  439.  
  440. # This forces most commands registered by LiteBans to be handled by LiteBans.
  441. # Set it to false if you want another plugin to override a LiteBans command.
  442. # This won't work for commands used from the console.
  443. force_command_override: false
  444.  
  445. # If enabled, this performs an additional two database queries on each join
  446. # in order to provide case-insensitive name bans.
  447. ban_names: false
  448.  
  449. # If a kick message contains any of these, it will not be added to the database.
  450. # You can add '' (empty string) to this list if you don't want any kicks to be added to the database.
  451. ignored_kick_messages: ['restarting']
  452.  
  453. # This option controls how often notifications are sent from a single player.
  454. # When a player tries to join when banned or talk while muted,
  455. # you won't see any more messages from them for a short while.
  456. notification_throttle_ticks: 12000
  457.  
  458.  
  459. # This option controls how often notifications are sent from a single player.
  460. # When a player tries to join when banned or talk while muted,
  461. # you won't see any more messages from them for a short while.
  462. notification_throttle_ticks: 12000
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!