Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # If bungeecord is set to true, banned players will be kicked from BungeeCord itself.
- # (Players will not be kicked to the lobby when they are banned.)
- # This will also implicitly set ban_sync_ticks and mutes.sync_ticks if not configured.
- # This option has no effect if the plugin is running under BungeeCord rather than Bukkit.
- bungeecord: true
- sql:
- # MySQL, PostgreSQL, SQLite, and H2 are supported database drivers.
- driver: MySQL
- ## MySQL/PostgreSQL settings ##
- # If using SQLite/H2, the database will be stored in the LiteBans plugin folder,
- # and most of these settings won't apply.
- # Database server address.
- address: play.adeptpvp.com:3306
- # Database name, username and password.
- database: mc18149
- username: 'mc18149'
- password: '3b5ea42bc7'
- table_prefix: 'AdeptPvP'
- # LiteBans utilizes connection pooling for extra performance and reliability.
- # min_connections: Minimum amount of pooled connections.
- # max_connections: Maximum amount of pooled connections. See: https://github.com/brettwooldridge/HikariCP/wiki/About-Pool-Sizing
- # timeout: Connection timeout.
- # idle_timeout: Maximum amount of time a pooled connection can remain idle before it is closed for inactivity.
- pool:
- min_connections: 1
- max_connections: 10
- timeout: 30 seconds
- idle_timeout: 1 minute
- # Database engine. Only applies to MySQL.
- engine: InnoDB
- # Format: <name>:<class>[:URL]
- drivers:
- - mysql:com.mysql.jdbc.Driver:https://repo1.maven.org/maven2/mysql/mysql-connector-java/5.1.37/mysql-connector-java-5.1.37.jar
- - pgsql:org.postgresql.Driver:https://repo1.maven.org/maven2/org/postgresql/postgresql/9.4-1201-jdbc41/postgresql-9.4-1201-jdbc41.jar
- - 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
- - sqlite:org.sqlite.JDBC:https://repo1.maven.org/maven2/org/xerial/sqlite-jdbc/3.8.11.1/sqlite-jdbc-3.8.11.1.jar
- - h2:org.h2.Driver:https://repo1.maven.org/maven2/com/h2database/h2/1.4.188/h2-1.4.188.jar
- durations:
- # Can be bypassed with the permission "litebans.unlimited.ban"
- tempban_max: 60 days
- # Can be bypassed with the permission "litebans.unlimited.mute"
- mute_max: 7 days
- # If true, players will not get an error when using a duration higher than the configured limit.
- # The duration will be rounded down to the maximum duration instead.
- round_down: true
- mutes:
- enabled: true
- # All of these commands can not be used while muted.
- command_blacklist:
- - /me
- - /say
- - /tell
- - /whisper
- - /reply
- - /pm
- - /msg
- - /emsg
- - /epm
- - /etell
- - /ewhisper
- - /w
- - /m
- - /t
- - /r
- # If enabled, muted players cannot use commands containing ":", for example: "/minecraft:me".
- prevent_bypass: true
- sync_ticks: 0
- # All online players will be re-checked for bans per interval when this is set.
- # This only makes sense in a multi-server configuration,
- # or if you're otherwise manipulating the database while the server is running.
- ban_sync_ticks: 0
- # If set, a ban or mute reason must be provided, otherwise players will get an error.
- # When set to false, "default_ban_reason" and "default_mute_reason" in messages.yml are used as reasons when no reason is provided.
- require_ban_mute_reason: false
- warnings:
- # Warnings will expire after this duration has passed.
- expire_after: 7 days
- # Warning actions.
- # Format: <amount>[+]:<action>
- # If '+' is provided after the amount, the action will execute if the player has that amount of warnings or more.
- actions:
- - '3:/kick -s:$silent $player Final warning: $reason'
- - '4:/tempban -s:$silent $player 1 day Reached 4 warnings: $list'
- # If enabled, the console will execute warning actions.
- # Otherwise, the player who executes the last warning also executes the warning action.
- actions_execute_as_console: false
- # If enabled, all active warnings will be deactivated after a warning action is executed.
- delete_warnings_after_action: false
- notify:
- # If enabled, players with the permission 'litebans.notify' or 'litebans.notify.banned_join' will be notified when a banned player tries to join.
- banned_player_join: true
- # If enabled, /dupeip output will be shown on join if the player meets certain conditions.
- dupeip_on_join: true
- # Notify if the player has a banned account on the same IP.
- dupeip_on_banned_account: true
- # If you set this to a lower value, players with X accounts will send dupeip notifications.
- dupeip_on_join_threshold: 999999
- # Log all notifications to the console?
- notify_console: true
- exempt:
- enable: true
- # By default, the first loaded world is used for permission checks.
- permission_world: default
- # Permission groups that are exempt from bans, mutes, warnings, and kicks.
- exempt_groups: []
- # Players who are exempt from bans, mutes, warnings, and kicks.
- # Format: <name/UUID>[:type]
- # Type can be ban, mute, warning, or kick.
- # Example:
- # exempt_players: ['Player', 'Player:kick', 'Player2']
- exempt_players: []
- geoip:
- enable: false
- # Anyone from these locations will not be able to join.
- # A full list of countries that can be blacklisted:
- # https://dev.maxmind.com/geoip/legacy/codes/iso3166/
- # 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".
- # The configuration includes "Anonymous Proxy" which matches a few open proxies and high profile VPNs according to the GeoLite2 database.
- # This may block some proxies, but it's not completely reliable as a proxy blocking solution.
- blacklist: ['Anonymous Proxy']
- download:
- # Download links for the API and database. They are downloaded to the 'plugins/LiteBans/geoip' folder.
- # You shouldn't need to change these, but if it isn't working, you can search for these files.
- api:
- - https://repo1.maven.org/maven2/com/maxmind/geoip2/geoip2/2.1.0/geoip2-2.1.0.jar
- - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.4.3/jackson-databind-2.4.3.jar
- - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-core/2.4.3/jackson-core-2.4.3.jar
- - https://repo1.maven.org/maven2/com/maxmind/db/maxmind-db/1.0.0/maxmind-db-1.0.0.jar
- - https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.4.3/jackson-annotations-2.4.3.jar
- # Will be extracted and saved as 'GeoLite2-Country.mmdb'.
- db: https://geolite.maxmind.com/download/geoip/database/GeoLite2-Country.mmdb.gz
- import:
- # You can import from: MaxBans/Ultrabans/BanHammer/BanManagerv4/BanManagerv5/BungeeAdminTools/LiteBans/Vanilla.
- # Vanilla means importing from banned-players.json, which is also used by Essentials.
- from: maxbans
- # If enabled, importing will be done from a SQLite database instead of a MySQL database.
- # You can ignore this if importing from banned-players.json.
- sqlite: true
- # SQLite file locations:
- # MaxBans: plugins/MaxBans/bans.db
- # Ultrabans: plugins/Ultrabans/banlist.db
- # BanHammer: plugins/BanHammer/BanHammer.db
- # LiteBans: plugins/LiteBans/litebans.sqlite
- sqlite_file: plugins/MaxBans/bans.db
- import_ipbans: true
- ## MySQL import settings ##
- import_mysql_address: localhost:3306
- import_mysql_database: maxbans
- import_mysql_username: ''
- import_mysql_password: ''
- # Use display names?
- # This means that when moderators and punished players change their name using /nick,
- # this name will be used in broadcasts and other messages instead of their regular name.
- use_display_names: false
- # Instead of "CONSOLE", this name will be used to represent the console.
- console_sender_name: Console
- # Players in this list will not be shown in /dupeip output. UUIDs can also be specified.
- hidden_dupeip_players: []
- # A player cannot be warned again while they are on cooldown.
- # This prevents two moderators from warning the same player for the same reason.
- warning_cooldown: 30
- # If enabled, online player names will be auto-completed.
- # Example: /ban Pl -> /ban Player
- autocomplete_online_player_names: false
- # This allows /dupeip and /ipreport to scan every single IP address that a player has ever joined with.
- # If set to false, it will only scan the last IP address.
- dupeip_scan_all_ips: false
- # /ipreport will not show accounts that have no other players attached by default.
- ipreport_minimum_accounts: 1
- # If disabled, all previous IP addresses will be recorded, allowing /iphistory to work.
- # It is not recommended to disable this for SQLite databases.
- delete_previous_history: true
- # If enabled (default), all previous login history will be unbanned when unbanning a player.
- unban_all_history: true
- # This is the amount of bans shown on each page for /banlist.
- # Note that ban entries can span 2-3 lines.
- banlist_bans_per_page: 5
- # Only show active bans for /banlist?
- banlist_show_active_only: false
- # If enabled, AuthMe will be detected and IP history will only be added after a player has successfully logged in.
- support_authme: true
- lockdown:
- # If enabled, /lockdown will continue after restarts.
- persist_enabled: true
- debug_level: 0
- # This forces most commands registered by LiteBans to be handled by LiteBans.
- # Set it to false if you want another plugin to override a LiteBans command.
- # This won't work for commands used from the console.
- force_command_override: false
- # If enabled, this performs an additional two database queries on each join
- # in order to provide case-insensitive name bans.
- ban_names: false
- # If a kick message contains any of these, it will not be added to the database.
- # You can add '' (empty string) to this list if you don't want any kicks to be added to the database.
- ignored_kick_messages: ['restarting']
- # This option controls how often notifications are sent from a single player.
- # When a player tries to join when banned or talk while muted,
- # you won't see any more messages from them for a short while.
- notification_throttle_ticks: 12000
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement