# 请注意:这是原版 AdvancedBan 或 AdvancedBanX 插件的一个分支版本。请勿在官方 AdvancedBan Discord 中寻求支持;相反,请在 GitHub 仓库的 Issues 页面寻求帮助。
描述
AdvancedBanZ 是 AdvancedBanX 的一个分支,而 AdvancedBanX 本身是由 Leoko 开发的原始 AdvancedBan 插件的现代更新版本。它是一个全能的惩罚系统,支持警告(warn)、临时警告(tempwarn)、禁言(mute)、临时禁言(tempmute)、封禁(ban)、临时封禁(tempban)、IP 封禁(ipban)以及踢出(kick)。该插件还提供了玩家历史记录功能,用于查看过去的惩罚记录。
该插件支持可配置的时间和消息模板,并根据特定原因自动计算和增加惩罚持续时间。AdvancedBanZ 提供了完整的消息文件,允许您自由修改和翻译所有提示,并包含一个详细的配置文件,其中有许多实用选项。
目前,AdvancedBanZ 支持 Bukkit(Spigot/Paper)和 BungeeCord 平台,并支持 MySQL 和本地文件存储以实现数据持久化。
安装步骤
- 从 Modrinth 下载插件。
- 将插件放入
plugins 文件夹(适用于 Bukkit 和 BungeeCord)。
- 重新加载或重启服务器。
- 使用
/advancedban 检查插件是否成功加载。
- 根据需要配置并开始使用。
可选提示:如果您在连接数据库时遇到问题,请尝试将 MySQL 版本调整为 5.X。
命令参考
查看所有命令
图例:
-
[必需] <可选>:| 表示“或”,-s 表示静默惩罚(不通知他人)
-
/kick<-s> [玩家] <原因 | @布局名称>
踢出玩家
-
/ban /mute /warn /note <-s> [玩家] <原因 | @LayoutName>
封禁/静音/警告一名玩家,或为其添加备注
-
/banip <-s> [玩家/IP] <原因 | @LayoutName>
封禁玩家的 IP(如果输入的是玩家名称,则使用缓存的 IP)
-
/tempban /tempmute /tempwarn <-s> [玩家] [Xmo|Xd|Xh|Xm|Xs|#时间格式] <原因 | @布局名称>
发出具有指定持续时间或基于时间格式自动计算的持续时间的临时处罚
-
/tempipban <-s> [玩家/IP] [Xmo|Xd|Xh|Xm|Xs|#时间格式] <原因 | @布局名称>
临时封禁玩家的 IP(别名:/tipban)
-
/change-reason [ID] [New Reason]
根据处罚 ID 修改处罚原因
-
/change-reason [ban/mute] [Player] [New Reason]
修改玩家当前封禁或禁言的原因
-
/unban /unmute [Player]
解除对玩家的封禁或禁言
-
/unwarn /unnote [ID]
移除警告或备注
-
/unwarn /unnote clear [Player]
移除指定玩家的所有警告或备注
-
/unpunish [ID]
移除任何类型的处罚记录
-
/warns /notes <玩家>
查看自己或其他玩家的警告/备注列表
-
/check [Player]
查看玩家状态:UUID / IP / 国家 / 封禁状态 / 禁言状态 / 警告次数 / 备注数量
-
/banlist <Page>
查看所有当前生效的处罚记录
-
/history [Player] <Page>
查看玩家的过往处罚记录(需要权限 ab.history)
-
/advancedban reload
重载消息文件及部分设置
-
/advancedban help
显示所有命令及其简要说明
-
/systemprefs
显示有助于配置的系统信息
权限节点
所有权限
ab.kick.use - /kick
ab.kick.exempt - 免于被踢出
ab.notify.kick - 接收踢出通知
ab.ban.perma - /ban
ab.ban.temp - /tempban
ab.ban.undo - /unban
ab.ban.exempt - 免于被封禁
ab.notify.ban - 接收封禁通知
ab.undoNotify.ban - 接收解封通知
ab.notify.tempban - 接收临时封禁通知
ab.ipban.perma - /ipban
ab.ipban.temp - /tempipban
ab.notify.ipban - 接收 IP 封禁通知
ab.tempipban.exempt - 免于临时 IP 封禁
ab.notify.tempipban - 接收临时 IP 封禁通知
ab.mute.perma - /mute
ab.mute.temp - /tempmute
ab.mute.undo - /unmute
ab.mute.exempt - 免于被禁言
ab.notify.mute - 接收禁言通知
ab.undoNotify.mute - 接收解除禁言通知
ab.notify.tempmute - 接收临时禁言通知
ab.warn.perma - /warn
ab.warn.temp - /tempwarn
ab.warn.undo - /unwarn
ab.warn.exempt - 免于被警告
ab.notify.warn - 接收警告通知
ab.undoNotify.warn - 接收撤销警告通知
ab.notify.tempwarn - 接收临时警告通知
ab.note.use - /note
ab.note.undo - /unnote
ab.note.exempt - 免于添加备注
ab.notify.note - 接收备注通知
ab.undoNotify.note - 接收删除备注通知
ab.all.undo - /unpunish
ab.warns.own - /warns (查看自身)
ab.warns.other - /warns PLAYER (查看他人)
ab.notes.own - /notes (查看自身)
ab.notes.other - /notes PLAYER (查看他人)
ab.check - /check
ab.check.ip - 同时显示 IP
ab.changeReason - /change-reason
ab.banlist - /banlist
ab.history - /history
ab.reload - /advancedban reload
ab.help - /advancedban help
ab.systemprefs - /systemprefs
限制处罚时长
默认情况下,只要用户拥有相应的权限,他们就可以对其他人进行无限时长的处罚。你可以通过 ab.tempban/tempmute/tempwarn.dur.X 来设置最大处罚时长。
在配置文件中,有一个名为 TempPerms 的部分,可用于为不同的 ID 定义最大处罚时长。例如:
1: 3600
这意味着拥有权限 ab.tempban.dur.1 的用户最多只能进行 3600 秒(即 1 小时)的封禁。单位为秒。如果用户拥有多个此类权限,则以数值较高的为准。更多详情请参见 config.yml。
层级豁免权限
对于拥有大型团队和复杂层级的服务器,你可能需要更精细地控制谁能处罚谁。
为此,你可以按照以下格式为用户分配豁免等级权限:
ab.TYPE.exempt.X
其中:
TYPE 可以是:ban(封禁)、tempban(临时封禁)、ipban(IP封禁)、tempipban(临时IP封禁)、warn(警告)、tempwarn(临时警告)、kick(踢出)、mute(静音)、tempmute(临时静音)
X 是 1 到 10 之间的整数(10 为最高权限)
如果未指定 X(即仅使用 ab.TYPE.exempt),则等同于 ab.TYPE.exempt.11,表示完全免疫。
注意:除非使用 LuckPerms,否则豁免权限仅在目标玩家在线时生效
同级用户之间无法互相处罚。
示例:
- 拥有
ab.ban.exempt 权限的用户不会被任何人封禁。
- 拥有
ab.ban.exempt.4 权限的用户不会被拥有 ab.ban.exempt.3 权限的用户封禁,但会被拥有 ab.ban.exempt.5 权限的用户封禁。
其他说明
如果你是在 BungeeCord 上使用此插件,你需要在 BungeeCord 的 config.yml 中定义权限,或通过专用的 BungeeCord 权限插件进行管理。
BungeeCord 的权限系统不支持 * 通配符,因此拥有 ab.* 并不能授予所有命令的访问权限。为了简化配置,AdvancedBanZ 提供了一个名为 EnableAllPermissionNodes 的设置。启用后,你可以使用 .all 代替 .*。例如,ab.all 将授予所有 AdvancedBanZ 命令的权限。(注意:此功能不适用于否定权限,例如 -ab.all 无效。)
配置文件说明
config.yml
配置文件应易于理解,每个选项都有详细注释。
config.yml
# AdvancedBan v4 - 原作者 Leoko,由 2vY (hlpdev) 和 Author87668 更新并维护
# 每个设置都有简短描述;修改前请仔细阅读。
# 更多信息请访问:https://www.spigotmc.org/resources/advancedban.8695/
# 设置为 false 以将所有封禁记录保存在本地 SQLite 数据库中
UseMySQL: false
MySQL:
IP: localhost
DB-Name: database-name
Username: admin
Password: superSecret
Port: 3306
Properties: 'verifyServerCertificate=false&useSSL=false&useUnicode=true&characterEncoding=utf8'
# 是否在插件启用/禁用时仅显示简要日志
DetailedEnableMessage: true
DetailedDisableMessage: true
# 当发生数据库连接错误(如 MySQL 宕机)时,是否阻止玩家加入服务器
LockdownOnError: true
# 默认处罚原因(当未指定原因时使用)
# 支持标准颜色代码或 MiniMessage 格式 (https://docs.advntr.dev/minimessage/format.html)
DefaultReason: "No reason provided."
# 如果服务器时间与你的时区不同,请在此处调整偏移量
# 示例:服务器时间 16:43,你的时间 13:43,则设置为 -3
# 你可以通过 /systemPrefs 查看服务器时间
TimeDiff: 0
# 被静音的玩家无法使用的命令列表(以防止绕过)
MuteCommands:
- 'me'
- 'say'
- 'action'
- 'eaction'
- 'describe'
- 'edescribe'
- 'eme'
- 'w'
- 'm'
- 'pm'
- 'whisper'
- 'ewhisper'
- 'emsg'
- 'msg'
- 'etell'
- 'tell'
- 'er'
- 'r'
- 'reply'
- 'ereply'
- 'ac'
- 'eac'
- 'amsg'
- 'eamsg'
- 'ehelpop'
- 'p msg'
# 这些玩家不能被以任何方式处罚(即使离线也生效)
# 建议配合 Vault 插件使用,以确保离线豁免能正确工作
ExemptPlayers:
- 'Leoko'
- 'md5'
- 'dutchy1001'
- 'ItzSomebody'
# %DATE% 变量的日期格式
DateFormat: "MM/dd/yyyy HH:mm"
# 是否启用 .all 权限节点(针对不支持 * 的权限系统,如 BungeeCord)
# 启用后,可以使用 ab.all 代替 ab.*
# 注意:否定权限(例如 -ab.all)无效
EnableAllPermissionNodes: false
# UUID 获取器设置
UUID-Fetcher:
# 动态模式会自动选择最佳的获取方法;建议保持启用
Dynamic: true
Enabled: true
Intern: false
REST-API:
URL: "https://api.mojang.com/users/profiles/minecraft/%NAME%?at=%TIMESTAMP%"
Key: "id"
BackUp-API:
URL: "https://api.minetools.eu/uuid/%NAME%"
Key: "id"
# 当警告达到指定数量时触发的操作
# 支持变量:%PLAYER% %REASON% %COUNT%
# 支持 MiniMessage 格式
WarnActions:
3: "kick %PLAYER% &c&oYou have received your 3rd warning!"
4: "tempban %PLAYER% 30m &c&oYou have received your 4th warning!"
5: "tempban %PLAYER% 5h &c&oYou have received your 5th warning!"
6: "tempban %PLAYER% 7d &c&oYou have received your 6th warning!"
7: "tempban %PLAYER% 1mo &c&oYou have received your %COUNT%th warning!"
10: "ban %PLAYER% &c&oYou have received your 10th warning!"
# 最大处罚持续时间权限映射(单位:秒)
TempPerms:
1: 600 # 10 分钟
2: 3600 # 1 小时
3: 43200 # 12 小时
# 是否启用调试模式(输出更多日志,有助于故障排除)
Debug: false
# 保留插件日志的天数(位于 plugins/AdvancedBan/logs 目录)
Log Purge Days: 10
# 是否在每条消息中禁用插件前缀
Disable Prefix: false
# 是否以更友好的方式注册命令(仅限 Bukkit)
# 默认禁用,以便允许覆盖来自其他插件的 /ban 等命令
Friendly Register Commands: false
messages.yml
包含所有面向用户的提示文本,支持标准颜色代码和 MiniMessage 格式。
messages.yml(关键结构节选,完整内容省略)
文件结构包括:
- General(通用)
- Ban / Ipban / Tempban / Tempipban(封禁 / IP封禁 / 临时封禁 / 临时IP封禁)
- Mute / Tempmute(静音 / 临时静音)
- Warn / Tempwarn / Note(警告 / 临时警告 / 备注)
- Kick(踢出)
- UnBan / UnMute / UnWarn / UnNote / UnPunish(解除封禁 / 解除静音 / 解除警告 / 解除备注 / 解除处罚)
- Banlist / History / Warns / Notes(封禁列表 / 历史记录 / 警告记录 / 备注记录)
- Check(查询)
所有消息均可自定义,并支持 %NAME%、%OPERATOR%、%REASON%、%DURATION% 等变量。
layouts.yml
用于定义预设的消息模板和时间递增模板。
layouts.yml
# 消息模板:可通过 @TemplateName 调用
Message:
ExampleLayout:
- '%PREFIX% &7因作弊被封禁'
- '&c&o执行者:%OPERATOR%'
- '&7'
- "&c检测到使用"
- "&c非法客户端,请立即停止!"
- "&c解封时间 &8» &7%DURATION%"
- '&7'
- '&8请通过 TS 或论坛申请解封'
- "&eTS 地址 &8» &c&n即将推出"
- "&e论坛地址 &8» &c&n即将推出"
# 时间模板:可通过 #TemplateName 调用,每次处罚后持续时间自动递增
Time:
ExampleLayout:
- '30m' # 第1次
- '2h' # 第2次
- '1d' # 第3次
- '1w'
- '1mo'
- '2mo'
- '4mo'
- 'perma' # 永久
用法示例:
/tempban PlayerA #ExampleLayout Cheating
/warn PlayerB @ExampleLayout
功能特性
- 集封禁、踢出、静音和警告于一体的系统
- 高性能运行
- 支持 BungeeCord 和 Bukkit/Spigot/Paper
- 玩家处罚历史记录
- 高级 UUID 支持(内置/外部获取器 + 备用 API)
- 支持 MySQL 或本地 SQLite 存储
- 完全自定义的消息和行为
- 多行封禁/踢出消息
- 预设原因模板
- 自动递增的处罚时长(第1次1小时,第2次6小时……)
- 自定义时区偏移
- 自动关联警告操作(例如,收到3次警告后自动踢出)
/check 命令可查询 UUID、IP、国家、封禁/静音/警告状态
- 完整支持 MiniMessage 格式化语法
技术支持
如果遇到任何问题,请先检查控制台错误日志。如果问题仍然存在,请在我们的 GitHub Issues 页面 提交问题。
统计信息
本插件使用 bStats 匿名收集服务器信息(如玩家数量、服务器版本等)。
Bukkit
BungeeCord
API 开发
在开发插件扩展时,请确保服务器上已安装 AdvancedBanZ 主插件。
Maven 依赖
<repositories>
...
<repository>
<id>hnt8</id>
<url>https://java.hnt8.net</url>
</repository>
...
</repositories>
<dependencies>
...
<dependency>
<groupId>net.hnt8.advancedban</groupId>
<artifactId>AdvancedBanZ</artifactId>
<version>3.0.6</version>
<scope>provided</scope>
</dependency>
...
</dependencies>
# Please note: This is a fork of the original AdvancedBan or AdvancedBanX plugin. Do not request support in the official AdvancedBan Discord; instead, seek help on the GitHub repository's issues page.
Description
AdvancedBanZ is a fork of AdvancedBanX, which itself is a modernized update of the original AdvancedBan plugin developed by Leoko. It is an all-in-one punishment system supporting warnings (warn), temporary warnings (tempwarn), mutes, temporary mutes (tempmute), bans, temporary bans (tempban), IP bans (ipban), and kicks. The plugin also provides a player history feature to view past punishment records.
The plugin supports configurable time and message templates, automatically calculating and increasing punishment durations based on specific reasons. AdvancedBanZ provides complete message files, allowing you to freely modify and translate all prompts, and includes a detailed main configuration file with numerous practical options.
Currently, AdvancedBanZ supports Bukkit (Spigot/Paper) and BungeeCord platforms, and supports both MySQL and local file storage for data persistence.
Installation Steps
- Download the plugin from Modrinth.
- Place the plugin into your
plugins folder (applicable for both Bukkit and BungeeCord).
- Reload or restart your server.
- Use
/advancedban to check if the plugin loaded successfully.
- Configure as needed and start using it.
Optional Tip: If you encounter issues connecting to the database, try adjusting the MySQL version to 5.X.
Command Reference
View All Commands
Legend:
-
[Required] <Optional>: | means "or", -s indicates a silent punishment (does not notify others)
-
/kick<-s> [Player] <Reason | @LayoutName>
Kick a player
-
/ban /mute /warn /note <-s> [Player] <Reason | @LayoutName>
Ban / Mute / Warn a player, or add a note to them
-
/banip <-s> [Player/IP] <Reason | @LayoutName>
Ban a player's IP (if a player name is entered, the cached IP is used)
-
/tempban /tempmute /tempwarn <-s> [Player] [Xmo|Xd|Xh|Xm|Xs|#TimeLayout] <Reason | @LayoutName>
Issue a temporary punishment with a specified duration or auto-calculated duration based on a time layout
-
/tempipban <-s> [Player/IP] [Xmo|Xd|Xh|Xm|Xs|#TimeLayout] <Reason | @LayoutName>
Temporarily ban a player's IP (Alias: /tipban)
-
/change-reason [ID] [New Reason]
Modify the reason based on the punishment ID
-
/change-reason [ban/mute] [Player] [New Reason]
Modify the reason for a player's current ban or mute
-
/unban /unmute [Player]
Unban or unmute a player
-
/unwarn /unnote [ID]
Remove a warning or note
-
/unwarn /unnote clear [Player]
Remove all warnings or notes for a player
-
/unpunish [ID]
Remove any type of punishment record
-
/warns /notes <Player>
View your own or another player's list of warnings/notes
-
/check [Player]
Get player status: UUID / IP / Country / Ban Status / Mute Status / Warning Count / Note Count
-
/banlist <Page>
View all currently active punishments
-
/history [Player] <Page>
View a player's historical punishment records (requires permission ab.history)
-
/advancedban reload
Reload message files and some settings
-
/advancedban help
Display all commands and their brief descriptions
-
/systemprefs
Display system information helpful for configuration
Permission Nodes
All Permissions
ab.kick.use - /kick
ab.kick.exempt - Exempt from being kicked
ab.notify.kick - Receive kick notifications
ab.ban.perma - /ban
ab.ban.temp - /tempban
ab.ban.undo - /unban
ab.ban.exempt - Exempt from being banned
ab.notify.ban - Receive ban notifications
ab.undoNotify.ban - Receive unban notifications
ab.notify.tempban - Receive temporary ban notifications
ab.ipban.perma - /ipban
ab.ipban.temp - /tempipban
ab.notify.ipban - Receive IP ban notifications
ab.tempipban.exempt - Exempt from temporary IP bans
ab.notify.tempipban - Receive temporary IP ban notifications
ab.mute.perma - /mute
ab.mute.temp - /tempmute
ab.mute.undo - /unmute
ab.mute.exempt - Exempt from being muted
ab.notify.mute - Receive mute notifications
ab.undoNotify.mute - Receive unmute notifications
ab.notify.tempmute - Receive temporary mute notifications
ab.warn.perma - /warn
ab.warn.temp - /tempwarn
ab.warn.undo - /unwarn
ab.warn.exempt - Exempt from being warned
ab.notify.warn - Receive warning notifications
ab.undoNotify.warn - Receive unwarn notifications
ab.notify.tempwarn - Receive temporary warning notifications
ab.note.use - /note
ab.note.undo - /unnote
ab.note.exempt - Exempt from having notes added
ab.notify.note - Receive note notifications
ab.undoNotify.note - Receive note removal notifications
ab.all.undo - /unpunish
ab.warns.own - /warns (view self)
ab.warns.other - /warns PLAYER (view others)
ab.notes.own - /notes (view self)
ab.notes.other - /notes PLAYER (view others)
ab.check - /check
ab.check.ip - Also display IP
ab.changeReason - /change-reason
ab.banlist - /banlist
ab.history - /history
ab.reload - /advancedban reload
ab.help - /advancedban help
ab.systemprefs - /systemprefs
Limiting Punishment Durations
By default, users can punish others indefinitely as long they have the corresponding permission. You can set maximum punishment durations via ab.tempban/tempmute/tempwarn.dur.X.
In the configuration file, there is a section named TempPerms that can be used to define the maximum punishment duration for different IDs. For example:
1: 3600
This means a user with the permission ab.tempban.dur.1 can only ban for a maximum of 3600 seconds (i.e., 1 hour). The unit is seconds. If a user has multiple such permissions, the one with the higher number takes precedence. See config.yml for more details.
Hierarchical Exemption Permissions
For servers with large teams and complex hierarchies, you may need finer control over who can punish whom.
To do this, you can assign exemption level permissions to users in the following format:
ab.TYPE.exempt.X
Where:
TYPE can be: ban, tempban, ipban, tempipban, warn, tempwarn, kick, mute, tempmute
X is an integer from 1 to 10 (10 is the highest privilege)
If X is not specified (i.e., just ab.TYPE.exempt), it is equivalent to ab.TYPE.exempt.11, meaning complete immunity.
Note: Exemption permissions only take effect when the target player is online (unless using LuckPerms!)
Users of the same level cannot punish each other.
Examples:
- A user with
ab.ban.exempt cannot be banned by anyone.
- A user with
ab.ban.exempt.4 cannot be banned by a user with ab.ban.exempt.3, but can be banned by a user with ab.ban.exempt.5.
Additional Notes
If you are using this plugin on BungeeCord, you need to define permissions in BungeeCord's config.yml or manage them via a dedicated BungeeCord permissions plugin.
The BungeeCord permission system does not support the * wildcard, so having ab.* does not grant access to all commands. To simplify configuration, AdvancedBanZ provides a setting called EnableAllPermissionNodes. When enabled, you can use .all instead of .*. For example, ab.all grants permission for all AdvancedBanZ commands. (Note: This feature does not work with negative permissions, e.g., -ab.all is invalid.)
Configuration File Explanation
config.yml
The configuration file should be easy to understand, with detailed comments for each option.
config.yml
# AdvancedBan v4 - Original author Leoko, updated and maintained by 2vY (hlpdev) and Author87668
# Each setting has a brief description; please read carefully before modifying.
# For more information, visit: https://www.spigotmc.org/resources/advancedban.8695/
# Set to false to save all ban records in a local SQLite database
UseMySQL: false
MySQL:
IP: localhost
DB-Name: database-name
Username: admin
Password: superSecret
Port: 3306
Properties: 'verifyServerCertificate=false&useSSL=false&useUnicode=true&characterEncoding=utf8'
# Whether to show only brief logs on plugin enable/disable
DetailedEnableMessage: true
DetailedDisableMessage: true
# Whether to prevent players from joining the server when a database connection error occurs (e.g., MySQL downtime)
LockdownOnError: true
# Default punishment reason (used when none is specified)
# Supports standard color codes or MiniMessage format (https://docs.advntr.dev/minimessage/format.html)
DefaultReason: "No reason provided."
# If the server time differs from your time zone, adjust the offset here
# Example: Server time 16:43, your time 13:43, then set to -3
# You can view server time via /systemPrefs
TimeDiff: 0
# List of commands that muted players cannot use (to prevent bypassing)
MuteCommands:
- 'me'
- 'say'
- 'action'
- 'eaction'
- 'describe'
- 'edescribe'
- 'eme'
- 'w'
- 'm'
- 'pm'
- 'whisper'
- 'ewhisper'
- 'emsg'
- 'msg'
- 'etell'
- 'tell'
- 'er'
- 'r'
- 'reply'
- 'ereply'
- 'ac'
- 'eac'
- 'amsg'
- 'eamsg'
- 'ehelpop'
- 'p msg'
# These players cannot be punished in any way (effective even when offline)
# Recommended to use with the Vault plugin to ensure offline exemptions work correctly
ExemptPlayers:
- 'Leoko'
- 'md5'
- 'dutchy1001'
- 'ItzSomebody'
# Date format for the %DATE% variable
DateFormat: "MM/dd/yyyy HH:mm"
# Whether to enable the .all permission node (for permission systems that do not support *, such as BungeeCord)
# When enabled, ab.all can be used instead of ab.*
# Note: Negative permissions (e.g., -ab.all) are invalid
EnableAllPermissionNodes: false
# UUID Fetcher Settings
UUID-Fetcher:
# Dynamic mode automatically selects the best fetching method; recommended to keep enabled
Dynamic: true
Enabled: true
Intern: false
REST-API:
URL: "https://api.mojang.com/users/profiles/minecraft/%NAME%?at=%TIMESTAMP%"
Key: "id"
BackUp-API:
URL: "https://api.minetools.eu/uuid/%NAME%"
Key: "id"
# Actions triggered when warnings reach specified counts
# Supports variables: %PLAYER% %REASON% %COUNT%
# Supports MiniMessage format
WarnActions:
3: "kick %PLAYER% &c&oYou have received your 3rd warning!"
4: "tempban %PLAYER% 30m &c&oYou have received your 4th warning!"
5: "tempban %PLAYER% 5h &c&oYou have received your 5th warning!"
6: "tempban %PLAYER% 7d &c&oYou have received your 6th warning!"
7: "tempban %PLAYER% 1mo &c&oYou have received your %COUNT%th warning!"
10: "ban %PLAYER% &c&oYou have received your 10th warning!"
# Maximum punishment duration permission mapping (unit: seconds)
TempPerms:
1: 600 # 10 minutes
2: 3600 # 1 hour
3: 43200 # 12 hours
# Whether to enable debug mode (outputs more logs, useful for troubleshooting)
Debug: false
# Number of days to retain plugin logs (located in plugins/AdvancedBan/logs)
Log Purge Days: 10
# Whether to disable the plugin prefix in all messages
Disable Prefix: false
# Whether to register commands in a friendlier way (Bukkit only)
# Disabled by default to allow overriding /ban and other commands from other plugins
Friendly Register Commands: false
messages.yml
Contains all user-facing prompt text, supporting standard color codes and MiniMessage format.
messages.yml (excerpt of key structure, full content omitted)
File structure includes:
- General
- Ban / Ipban / Tempban / Tempipban
- Mute / Tempmute
- Warn / Tempwarn / Note
- Kick
- UnBan / UnMute / UnWarn / UnNote / UnPunish
- Banlist / History / Warns / Notes
- Check
All messages are customizable and support variables such as %NAME%, %OPERATOR%, %REASON%, %DURATION%, etc.
layouts.yml
Used to define preset message templates and time increment templates.
layouts.yml
# Message Templates: Can be called via @TemplateName
Message:
ExampleLayout:
- '%PREFIX% &7Banned for cheating'
- '&c&oExecuted by %OPERATOR%'
- '&7'
- "&cDetected use of"
- "&cillegal client, please stop immediately!"
- "&cUnban time &8» &7%DURATION%"
- '&7'
- '&8Please apply for unban via TS or Forum'
- "&eTS Address &8» &c&nComing Soon"
- "&eForum Address &8» &c&nComing Soon"
# Time Templates: Can be called via #TemplateName, duration increases automatically with each punishment
Time:
ExampleLayout:
- '30m' # 1st time
- '2h' # 2nd time
- '1d' # 3rd time
- '1w'
- '1mo'
- '2mo'
- '4mo'
- 'perma' # Permanent
Usage Examples:
/tempban PlayerA #ExampleLayout Cheating
/warn PlayerB @ExampleLayout
Features
- All-in-one system for bans, kicks, mutes, and warnings
- High-performance performance
- Supports both BungeeCord and Bukkit/Spigot/Paper
- Player punishment history
- Advanced UUID support (built-in/external fetchers + backup API)
- Supports MySQL or local SQLite storage
- Fully customizable messages and behaviors
- Multi-line ban/kick messages
- Preset reason templates
- Automatic punishment duration escalation (1st time 1 hour, 2nd time 6 hours...)
- Custom time zone offset
- Automatic warning linkage actions (e.g., auto-kick after 3 warnings)
/check command to query UUID, IP, country, ban/mute/warning status
- Full support for MiniMessage formatting syntax
Technical Support
If you encounter issues, please check the console error logs first. If the problem persists, please submit an issue on our GitHub Issues page.
Statistics
This plugin uses bStats to anonymously collect server information (such as player count, server version, etc.).
Bukkit
BungeeCord
API Development
When developing plugin extensions, ensure that the AdvancedBanZ main plugin is installed on the server.
Maven Dependency
<repositories>
...
<repository>
<id>hnt8</id>
<url>https://java.hnt8.net</url>
</repository>
...
</repositories>
<dependencies>
...
<dependency>
<groupId>net.hnt8.advancedban</groupId>
<artifactId>AdvancedBanZ</artifactId>
<version>3.0.6</version>
<scope>provided</scope>
</dependency>
...
</dependencies>
评论 0
登录后参与评分
还没有评论,来抢沙发吧