exempt:
enable: true
# By default, permission checks are global. You can set them to a specific world here.
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. (All types apply if not specified)
# Example:
# exempt_players: ['Player', 'Player2', 'Player3', 'Player4:mute']
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/
# Example:
# blacklist: ['Australia', 'Brazil', 'Canada', 'Denmark']
blacklist: []
# If the whitelist is not empty, all countries which are not found in the list will be blocked.
# NOTE: If you are hosting your server on your own machine, you should add "geoip.error" to the whitelist
# in order to allow local addresses (like 127.0.0.1 or 192.168.1.23) to join the server.
whitelist: []
download:
# https://gitlab.com/ruany/LiteBans/-/wikis/GeoIP
db: https://download.maxmind.com/app/geoip_download?edition_id=GeoLite2-Country&license_key=YOUR_LICENSE_KEY&suffix=tar.gz
api:
- https://repo1.maven.org/maven2/com/maxmind/geoip2/geoip2/2.1.0/geoip2-2.1.0.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-core/2.4.3/jackson-core-2.4.3.jar
- https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-annotations/2.4.3/jackson-annotations-2.4.3.jar
- https://repo1.maven.org/maven2/com/fasterxml/jackson/core/jackson-databind/2.4.3/jackson-databind-2.4.3.jar
security:
# If enabled, only the console can see IP addresses in /dupeip output.
# This does not prevent players from using /dupeip. It only prevents them from seeing IP addresses.
dupeip: true
# If enabled, only the console can use /iphistory.
iphistory: true
# If enabled, punishments will be silent by default.
# This can be overridden per-punishment by using the "-p" (public) flag (the opposite of "-s").
silent: false
# Instead of "CONSOLE", this name will be used to represent the console.
console_sender_name: Console
# 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.
# The BungeeCord version of the plugin cannot detect Spigot-side display names.
use_display_names: false
# This allows /dupeip and /ipreport to scan every single IP address that a player has ever joined with. (Multiple IP scanning)
# If set to false, only the player's last IP address will be scanned.
# (This option requires `delete_previous_history: false`)
dupeip_scan_all_ips: false
# If disabled, all previous IP addresses will be recorded, allowing /iphistory to work.
delete_previous_history: true
# If enabled, LiteBans performs an additional database query on login to provide case-insensitive name bans.
# This also prevents players from evading bans by switching from offline-mode to online-mode (through FastLogin, for example).
ban_names: false
# Moderators cannot use /ban or /warn twice within a specific time frame (in seconds).
# Additionally, the same player cannot be punished twice.
# This can be bypassed with: "litebans.cooldown.bypass", "litebans.cooldown.bypass.ban", "litebans.cooldown.bypass.warn"
ban_cooldown: 3
warning_cooldown: 3
# If enabled, all previous login history will be unbanned when unbanning a player.
# Essentially a "chain unban" - it can resolve multiple IP bans at the same time and it will be more effective if "delete_previous_history" is disabled.
unban_all_history: false
# If a kick message contains any of these, it will not be added to the database.
# You can set this list to [''] 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
# If enabled, 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
# After configuring import options, run "/litebans import start" to begin the import.
# The import process occurs while the server is running, no downtime is required.
import:
# You can import from: MaxBans, Ultrabans, BanHammer, BanManagerv4, BanManagerv5, BanManagerv7, BungeeAdminTools, AdvancedBan(MySQL only), LiteBans, Vanilla.
# Vanilla means importing from banned-players.json, which is also used by Essentials.
from: vanilla
# 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.
# If importing from LiteBans, H2 will be used instead of SQLite.
sqlite: true
# SQLite file locations:
# MaxBans: plugins/MaxBans/bans.db
# Ultrabans: plugins/Ultrabans/banlist.db
# BanHammer: plugins/BanHammer/BanHammer.db
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: ''
##############################
###### Advanced settings #####
##############################
# If enabled, broadcasts and notifications generated by this instance or obtained from other instances will be displayed here.
# If you're getting duplicate broadcasts, disable this on the BungeeCord instance.
# Disabling this does not disable synchronization, it only prevents an instance from sending messages locally.
# (On a BungeeCord instance, a "local" message will reach players on all servers on the network, not just the origin server)
local_messages: true
lockdown:
# If enabled, /lockdown will continue after restarts.
persist_enabled: true
# If enabled, the local system timezone will be used.
# UTC time will be stored in the database, but dates will be formatted using the timezone offset.
use_timezone: true
# If enabled, LiteBans will use the timezone stored in the database.
use_database_time: false
# This option allows you to disable recording IP history on specific servers.
# Example: ignored_history_servers: ['Lobby']
# This is useful when you have a layer of authentication (e.g. AuthMe or 2FA) if unauthenticated players cannot leave the lobby server.
# Under Spigot, you can add 'local' to this list to prevent this server from recording IP history.
ignored_history_servers: []
# Players in this list will not be shown in /dupeip or /alts output.
# Names, UUIDs and IP addresses can be specified.
hidden_dupeip_players: []
# This option controls the behaviour of the "-N" flag. This flag prevents active bans/mutes from being overridden.
# If enabled, the "-N" flag will only prevent bans from being overridden if the active ban has a lower duration.
override_lower_duration: false
# Amount of entries to show on /history and /staffhistory by default.
default_history_limit: 10
# 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 this is enabled, players with `litebans.exempt.bypass` permission can punish exempt players.
# Note that all operators will usually have this permission unless negated.
allow_exempt_bypass: false
# If this is enabled, players with `litebans.clearchat.bypass` permission can bypass /clearchat.
allow_clearchat_bypass: false
# If enabled, online player names will be auto-completed.
# Example: /ban Pl -> /ban Player
# This has absolutely nothing to do with tab-completion.
autocomplete_online_player_names: false
# If enabled, AuthMe will be detected and IP history will only be added after a player has successfully logged in.
# This option will only work under Spigot, since AuthMe is a Spigot plugin.
support_authme: true
# If enabled, ProtocolLib will be detected and chat events will be cancelled before they can be processed by any other plugins.
# This can help prevent plugin conflicts which allow muted players to chat.
# This option will only work under Spigot, since ProtocolLib is a Spigot plugin.
use_protocollib: true
# If enabled, players will be checked for bans after they have joined. (Spigot only)
# This should not be enabled unless you have a conflicting plugin which is un-cancelling login events and allowing banned players to log in.
# Players are checked before login regardless of this option.
check_after_join: false
# /ipreport will not show accounts that have no other players attached by default.
ipreport_minimum_accounts: 1
# If enabled, all players joining this instance will not be checked for bans.
# (Only works under Spigot)
disable_login_ban_check: false
# If enabled, the plugin will notify you when an update is available.
update_check: true
debug_level: 0
