此 Bukkit 页面已停用!
请访问我们的 SpigotMC 页面以获取最新版本:
AdvancedBan 是一款集警告、临时警告、禁言、临时禁言、封禁、临时封禁、IP 封禁、临时 IP 封禁以及踢出于一体的综合处罚系统。它还包含玩家历史记录功能,您可以查看玩家过往的处罚记录,并且该插件支持可配置的时间与消息布局,能够根据特定原因自动计算并增加处罚时长。AdvancedBan 还提供完整的消息文件,允许您修改和翻译所有消息,并附带一份包含大量实用设置的详细配置文件。这是一个同时适用于 BungeeCord 和 Bukkit/Spigot 的插件,支持 MySQL 和本地嵌入式数据库,以提供高性能表现。
1. 下载插件
2. 将其放入你的插件文件夹中。(可以是 BungeeCord 服务器的,也可以是 Bukkit/Spigot 服务器的)
3. 重载/重启你的服务器(如果使用 BungeeCord,需使用 /end 命令重启)
4. 使用 /advancedban 检查插件是否已加载。
5. 按照你的喜好进行配置并享受游戏吧。
[必需]
可选>
| = 或
-s = 静默惩罚(不向其他玩家发送通知)
/kick [PLAYER] <-s> <REASON | @LAYOUT>
踢出某名玩家
/ban /mute /warn [PLAYER] <-s> <REASON | @LAYOUT>
封禁/禁言/警告一名玩家
/banip [PLAYER/IP] <-s> <REASON | @LAYOUT>
封禁玩家的 IP。如果输入的是名称,将使用缓存的 IP
/tempban /tempmute /tempwarn [PLAYER] [Xmo|Xd|Xh|Xm|Xs|#TIMELAYOUT] <-s> <REASON | @LAYOUT>
在指定时间内或使用时序布局自动计算时间,临时封禁/禁言/警告一名玩家
/tempipban [PLAYER/IP] [Xmo|Xd|Xh|Xm|Xs|#TIMELAYOUT] <-s> <REASON | @LAYOUT>
在指定时间内或使用时序布局自动计算时间,临时封禁玩家的 IP
别名:/tipban
/change-reason [ID] [New reason]
根据 ID 更改处罚原因
/change-reason [ban/mute] [PLAYER] [New reason]
更改某名玩家的处罚原因
/unban /unmute [PLAYER]
解除封禁/禁言
/unwarn [ID]
删除一条警告
/unpunish [ID]
删除一项处罚
/warns <PLAYER>
查看自己或某名玩家的警告记录。
/check [PLAYER]
获取玩家状态:UUID/IP/国家/封禁状态/禁言状态/警告次数
/banlist <PAGE>
查看所有当前生效的处罚
/history [PLAYER] <PAGE>
查看所有当前生效的处罚
使用该命令需要权限 ab.history
/advancedban reload
从文件中重新加载消息和“部分”设置
/advancedban help
显示所有命令列表及其简要说明
/systemprefs
显示一些对配置有用的系统信息
大多数权限节点遵循简单的布局:
ab.PUNISHMENT.TYPE 或 ab.COMMAND
例如,/ban 命令的权限节点是 ab.ban.perma,而 tempwarn 命令的权限节点是 ab.warn.temp
但无论如何请检查权限列表以确保您使用的是正确的权限:
ab.kick.use - /kick
ab.kick.exempt - 免疫踢出
ab.kick.notify - 接收通知
ab.ban.perma - /ban
ab.ban.temp - /tempban
ab.ban.exempt - 免疫封禁
ab.ban.notify - 接收通知
ab.ban.undo - /unban
ab.tempban.exempt - 免疫临时封禁
ab.tempban.notify - 接收通知
ab.ipban.perma - /ipban
ab.ipban.temp - /tempipban
ab.ipban.exempt - 免疫 IP 封禁
ab.ipban.notify - 接收通知
ab.tempipban.exempt - 免疫临时 IP 封禁
ab.tempipban.notify - 接收通知
ab.mute.perma - /mute
ab.mute.temp - /tempmute
ab.mute.exempt - 免疫禁言
ab.mute.notify - 接收通知
ab.mute.undo - /unmute
ab.tempmute.exempt - 免疫临时禁言
ab.tempmute.notify - 接收通知
ab.warn.perma - /warn
ab.warn.temp - /tempwarn
ab.warn.exempt - 免疫警告
ab.warn.notify - 接收通知
ab.warn.undo - /unwarn
ab.tempwarn.exempt - 免疫临时警告
ab.tempwarn.notify - 接收通知
ab.all.undo - /unpunish
ab.warns.own - /warns
ab.warns.other - /warns
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 中还有另一段说明。
使用 Bungeecord 时的注意事项:
如果您在 Bungeecord 上使用此插件,则需要在 Bungeecord 服务器的 config.yml 或通过特殊的 Bungeecord 权限插件中定义权限。
Bungeecord 权限的问题在于没有 *-Perms 这样的通配符,因此拥有 ab.* 的用户将无法访问所有命令。但为了简化设置,AdvancedBan 的配置中有一个名为 "EnableAllPermissionNodes" 的选项,允许您使用 .all 代替 .*。如果启用该选项,拥有 ab.all 权限的用户将可以访问所有 AdvancedBan 命令。(配置文件中另有说明)
一些截图:
警告:
临时禁言:
带消息布局的临时封禁:
封禁:
踢出:
检查:[无国家信息,因为这是本地回环地址]
Config.yml:
config.yml 应该是自解释的,并且配置文件中也有相应的说明
# AdvancedBan v2 - Coded by Leoko
# For each setting, there is a small description.
# Please read each description carefully before changing anything.
# For more information visit: https://www.spigotmc.org/resources/advancedban.8695/
# Do you want your own Plugin or Website? Check out our Dev-Page: http://dev.skamps.eu
If set to false all bans will be saved locally in a HSQLDB-Database
UseMySQL: false
Set to false if you want to have only short messages in the console
On startup and on the shutdown.
DetailedEnableMessage: true
DetailedDisableMessage: true
This will be the default reason to be displayed if none is given
DefaultReason: "none"
Change this if your server has a different time that your users.
例如:ServerTime: 16:43 | Your Time: 13:43 | TimeDiff 必须设置为 -3
你可以使用 /systemPrefs 命令查看服务器时间
TimeDiff: 0
以下命令将对被禁言的玩家禁用
玩家无法通过类似 "/minecraft:me" 的命令绕过此限制
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'
这些玩家将不会受到任何形式的惩罚
即使玩家离线,此设置也生效
ExemptPlayers:
- 'Leoko'
- 'md5'
- 'dutchy1001'
- 'ItzSomebody'
用于 %DATE% 变量的日期格式
DateFormat: "dd.MM.yyyy-HH:mm"
这对于 BungeeCord 服务器或权限系统不支持 *-Perms 的服务器很有用
启用此项后,你可以使用 ab.all 代替 ab.,或使用 ab.ban.all 代替 ab.ban.
这对负向权限无效!例如 -ab.all 不会阻止该用户的所有命令。
EnableAllPermissionNodes: false
如果你使用外部 REST API,它们必须以 JSON 格式响应
提供的 API 仅用于 NAME -> UUID 的转换
对于 UUID -> NAME 的转换,将优先使用官方 MojangAPI 或内部获取器 (InternFetcher)
检查你是否可以使用内部获取器,请执行 /systemPerfs 并将你的 UUID
# 与你在 上看到的在线 UUID 进行比较
# 如果两者相似,我们建议使用 InternFetcher
UUID-Fetcher:
# 如果 Dynamic 设置为 true,它将覆盖 'enabled' 和 'intern' 设置
# 并自动检测最适合你服务器的 UUID 获取设置。
# 我们的建议:如果没有问题,请不要将 dynamic 设置为 false。
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://us.mc-api.net/v3/uuid/%NAME%"
Key: "uuid"
以下是警告达到一定次数时将执行的命令
如果跳过某个数字,将重复执行前一个命令
你也可以使用非 AdvancedBan 命令,如 'broadcast' 或 'clear %PLAYER%'
变量:%PLAYER%, %REASON%, %COUNT%
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!"
在这里你可以为最大惩罚持续时间创建权限节点。
权限 "ab.tempban.dur.1" 允许玩家最多封禁 600秒 = 10分钟
权限 "ab.tempwarn.dur.2" 允许玩家最多警告 3600秒 = 1小时
你最多可以创建 10 个权限。这些权限可以被 "ab.COMMAND.dur.max" 覆盖
TempPerms:
1: 600
2: 3600
3: 43200
Messages.yml
在这里你可以更改所有消息。默认设置中使用了所有可用的消息变量。
Layout.yml
Messages:
在这里你可以定义预定义的处罚理由,这些理由可用于(临时)封禁/禁言/警告以及踢出玩家。
你可以直接输入 @LAYOUT-NAME 来代替理由。这样你就可以为不同的理由设置包含不同信息的不同布局。
一旦定义了这些布局,你就无需输入完整的理由文本。
Time:
在这里你可以定义时间布局,用于临时惩罚。
你可以直接输入 #LAYOUT-NAME 来代替持续时间。每次玩家使用相同的布局受到惩罚时,时间都会增加。
# 默认布局位于 Message.yml 文件中!
# 消息布局不仅可用于封禁,也可用于禁言和警告
# 变量:%OPERATOR%, %REASON%, %PREFIX%, %DURATION%
# 对于警告,你还可以使用变量 %COUNT%,它将被
# 替换为玩家当前已收到的警告总数
# 用法示例:/ban Leoko @ExampleLayout
Message:
ExampleLayout:
- '%PREFIX% &7Banned for Hacking'
- '&c&oBannd by %OPERATOR%'
- '&7'
- "&cIt seems like you are using a"
- "&chacked client please disabled it!"
- "&cUnban in &8\xbb &7%DURATION%"
- '&7'
- '&8Unban application in TS or forum'
- "&eTS-Ip &8\xbb &c即将推出"
- "&e论坛 &8\xbb &c即将推出"
例如,您可以像这样使用此时间布局:"/tempban Leoko #ExampleLayout FFA中的作弊行为"
或者使用 "/tempwarn Leoko #ExampleLayout 广告" 或 "/tempwarn Leoko #ExampleLayout 请勿使用大写锁定键"
您也可以将其与消息布局结合使用,例如 "/tempban Leoko #ExampleLayout @Hacking"
Time:
ExampleLayout:
- '30m'
- '2h'
- '1d'
- '1w'
- '1mo'
- '2mo'
- '4mo'
- '永久'
- 封禁、踢出、静音和警告系统
- 卓越的性能
- BungeeCord 与 Bukkit/Spigot 插件合二为一
- 玩家历史记录
- 易于使用的 API
- 高级 UUID 支持
- 内部或外部 UUID 获取器
- 当 Mojang 服务器离线时的备用 UUID 获取器
- 可更改 UUID 获取器的 REST API
- MySQL 或本地嵌入式 HyperSQL
- 完全自定义
- 踢出和封禁消息支持多行
- 预定义理由
- 自动时间计算 [首次临时封禁 -> 1小时 | 第二次临时封禁 -> 6小时 ...]
- 自定义时间偏移 [如果服务器时间错误,可更改时区]
- 自动警告操作
- 检查命令 [UUID, IP, 国家, 封禁/静音/警告次数]
>> 支持 AdvancedBan 的插件 <<
Party and Friends System 的附加组件 ([USER=67188]@simonsator[/USER]):
GUI 附加组件 ([USER=57888]@Boobah[/USER]):
英语:
(详细)
(简要)
荷兰语/Nederlands:
俄语:
西班牙语:
如果您制作了其他语言版本,请通过私信发送链接给我。
要求:
- AdvancedBan 版本 2.0.0 或更高
- 可从外部访问的 MySQL 服务器(不仅仅是 localhost)
- 启用 MySQL 而非文件存储
不需要 Web 服务器
注意:
Web 面板不是像第一个那样可以下载的东西。
它是一个网站,您可以在上面注册您的服务器,该网站将为您生成专属的封禁面板。
此外,该面板仅用于显示信息,并非用于管理,仅用于监控。
免费 MySQL 数据库:
BPlaced 目前无法使用
这里有一个实时演示:
功能:
- 安全的登录系统 (sha1 & 无 SQL 注入)
- 移动端优化
- 扁平化设计
- 独立子域名 [NAME.banpanel.eu]
- 自定义消息和设计 [即将推出]
- 能够集成到您的网站中
在此注册:
独立 Web 界面替代方案
感谢 [USER=138878]@mathhulk[/USER],这里有一个你可以下载并放置在自己 Web 服务器上的 Web 界面。如果……这将会非常有用:
……你的 MySQL 仅允许 localhost 访问
……你想对布局进行重大修改
此 Web 界面不包含上述所有功能,例如玩家搜索或高级移动设备优化。
最后请注意,本 Web 界面的所有功劳都归于 [USER=138878]@mathhulk[/USER],我们不会为其提供任何支持。
我不为此 Web 面板的安全性背书!
GitHub:
示例:
如果你在使用该插件时遇到任何问题,请首先检查控制台是否有任何错误消息以及解决问题的说明,并阅读下方的已知问题部分。
如果问题仍然存在,请将其发布到讨论区、GitHub 或我们的 Discord 服务器上 
AdvancedBan 的新版本耗费了大量精力,我投入了大量的时间和努力。
因此,如果你认可我的工作,我将非常感谢每一份捐赠 ^^
>> 使用 AdvancedBan 的服务器 <<
BlizzardCraft Network
> mc.blizzardcraft.net
我们使用一个名为 bStats 的指标系统来跟踪你服务器的信息
例如:玩家数量、位系统、MC 版本、服务器系统等。
有关 bStats 的更多信息可以在这里找到:
暂无 
关于 API 的所有信息都可以在 GitHub 上找到
This bukkit page is discontinued!
Visit our SpigotMC page to get the latest version:
AdvancedBan is an All-In-One Punishment-System with warns, tempwarns, mutes, tempmutes, bans, tempbans, ipbans, tempipbans and kicks. There is also a PlayerHistory so you can see the players past punishments and the plugin has configurable Time & Message-Layouts which automatically calculate and increase the Punishment-Time for certain reasons. AdvancedBan provides also a full Message-File so you can change and translate all messages & a detailed config file with a lot of useful settings. This is a BungeeCord & Bukkit/Spigot-Plugin in one and it supports MySQL and a local embedded Database to provide high performance.
1. Download the Plugin
2. Put it in your Plugin folder. [either in the one of your BungeeCord-Server or in the one of the Bukkit/Spigot]
3. Reload/Restart your Server [if BungeeCord you have to restart it with /end]
4. Check with /advancedban if the plugin is loaded.
5. Configure it like you want & have fun.
[NEEDED]
<OPTIONAL>
| = or
-s = Silent punishemnt (no notification to others)
/kick [PLAYER] <-s> <REASON | @LAYOUT>
Kick a player
/ban /mute /warn [PLAYER] <-s> <REASON | @LAYOUT>
Ban/Mute/Warn a player
/banip [PLAYER/IP] <-s> <REASON | @LAYOUT>
Ban a player's IP. If you enter a name it will use the cached IP
/tempban /tempmute /tempwarn [PLAYER] [Xmo|Xd|Xh|Xm|Xs|#TIMELAYOUT] <-s> <REASON | @LAYOUT>
Tempban/mute/warn a player for a given time or with a time-layout for automatic-time-calcualtion
/tempipban [PLAYER/IP] [Xmo|Xd|Xh|Xm|Xs|#TIMELAYOUT] <-s> <REASON | @LAYOUT>
Temippban a player for a given time or with a time-layout for automatic-time-calcualtion
Alias: /tipban
/change-reason [ID] [New reason]
Change the reason for a punishment by id
/change-reason [ban/mute] [PLAYER] [New reason]
Change the reason for a players punishment
/unban /unmute [PLAYER]
Unban/mute a player
/unwarn [ID]
Delete a warn
/unpunish [ID]
Delete a punishment
/warns <PLAYER>
See your own or a player's warnings.
/check [PLAYER]
Get player-status: UUID/IP/Country/Ban-Status/Mute-Status/Warn-Count
/banlist <PAGE>
See all currently active punishments
/history [PLAYER] <PAGE>
See all currently active punishments
To use the command - ab.history
/advancedban reload
Reloads the messages from file and "some" settings
/advancedban help
Shows a list of all commands and a brief explanation
/systemprefs
Displays some System-Information which are useful for the configuration
Most of the permission nodes follow a simple layout:
ab.PUNISHMENT.TYPE or ab.COMMAND
So, for example, the /ban command has the permission node ab.ban.perma and the tempwarn command has ab.warn.temp
But please check the list of permissions anyway to ensure you are using the right permissions:
ab.kick.use - /kick
ab.kick.exempt - Immune to kicking
ab.kick.notify - Receives notification
ab.ban.perma - /ban
ab.ban.temp - /tempban
ab.ban.exempt - Immune to ban
ab.ban.notify - Receives notification
ab.ban.undo - /unban
ab.tempban.exempt - Immune to tempban
ab.tempban.notify - Receives notification
ab.ipban.perma - /ipban
ab.ipban.temp - /tempipban
ab.ipban.exempt - Immune to ipban
ab.ipban.notify - Receives notification
ab.tempipban.exempt - Immune to tempipban
ab.tempipban.notify - Receives notification
ab.mute.perma - /mute
ab.mute.temp - /tempmute
ab.mute.exempt - Immune to mute
ab.mute.notify - Receives notification
ab.mute.undo - /unmute
ab.tempmute.exempt - Immune to tempmute
ab.tempmute.notify - Receives notification
ab.warn.perma - /warn
ab.warn.temp - /tempwarn
ab.warn.exempt - Immune to warn
ab.warn.notify - Receives notification
ab.warn.undo - /unwarn
ab.tempwarn.exempt - Immune to tempwarn
ab.tempwarn.notify - Receives notification
ab.all.undo - /unpunish
ab.warns.own - /warns
ab.warns.other - /warns
ab.check - /check
ab.check.ip - Also shows IP
ab.changeReason - /change-reason
ab.banlist - /banlist
ab.history - /history
ab.reload - /advancedban reload
ab.help - /advancedban help
ab.systemprefs - /systemprefs
How to limit the punish duration:
By default, the user will be able to punish an infinite amount of time if he has the perms to use the command.
You can set the max-punishment-time with ab.tempban/tempmute/tempwarn.dur.X
In the config, there is a section called "TempPerms".
There you can configure how long which ID will be able to punish
for example, you set
1: 3600
the player with the perms ab.tempban.dur.1 will only be able to ban 3600s -> 1h
The amount is entered in SEC and if a player has more than one perms the higher numbers override.
There is a second explanation in the config.yml.
Note when using Bungeecord:
If you use this plugin on bungeecord you need to define the permissions in the config.yml of the Bungeecord Server or through a spcial bBungeecord Permission Plugin.
The problem with bungeecord permissions is that there are not *-Perms so a user with ab.* won't have access to all commands. But to simplify the setup there is a setting in the advacnedban config called "EnableAllPermissionNodes" which allows you to use a .all instead of a .* so if enabled a user with ab.all will have access to all AdvancedBan commands. (There is another explanation in the config)
Some images:
Warn:
Tempmute:
Tempban with Message-Layout:
Ban:
Kick:
Check: [No country because it's a localhost-ip]
Config.yml:
The config.yml should be self-explaining and there are also explanations in the config.yml
# AdvancedBan v2 - Coded by Leoko
# For each setting, there is a small description.
# Please read each description carefully before changing anything.
# For more information visit: https://www.spigotmc.org/resources/advancedban.8695/
# Do you want your own Plugin or Website? Check out our Dev-Page: http://dev.skamps.eu
# If set to false all bans will be saved locally in a HSQLDB-Database
UseMySQL: false
# Set to false if you want to have only short messages in the console
# On startup and on the shutdown.
DetailedEnableMessage: true
DetailedDisableMessage: true
# This will be the default reason to be displayed if none is given
DefaultReason: "none"
# Change this if your server has a different time that your users.
# e.g.: ServerTime: 16:43 | Your Time: 13:43 | TimeDiff has to be set to -3
# You can check the server time with /systemPrefs
TimeDiff: 0
# This commands will be disabled for muted players
# A player wouldn't be able to bypass with eg "/minecraft:me"
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'
# These players will not be able to get punished in any way
# this also works if the player is offline
ExemptPlayers:
- 'Leoko'
- 'md5'
- 'dutchy1001'
- 'ItzSomebody'
# The date-format which will be used for the %DATE% variable
DateFormat: "dd.MM.yyyy-HH:mm"
# This is useful for bungeecord servers or server with permission systems which do not support *-Perms
# So if you enable this you can use ab.all instead of ab.* or ab.ban.all instead of ab.ban.*
# This does not work with negative permissions! e.g. -ab.all would not block all commands for that user.
EnableAllPermissionNodes: false
# If you use external REST-APIs they will have to respond in JSON
# The given APIs will only be used for NAME -> UUID
# For UUID -> NAME will either use the official MojangAPI or the InternFetcher
# To check if you can use the intern fetcher do /systemPerfs and compare your uuid
# to the one you can see online on http://NamesMC.com
# if they are similar we recommend using the InternFetcher
UUID-Fetcher:
# If dynamic it set to true it will override the 'enabled' and 'intern' settings
# and automatically detect the best possible uuid fetcher settings for your server.
# Our recommendation: don't set dynamic to false if you don't have any problems.
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://us.mc-api.net/v3/uuid/%NAME%"
Key: "uuid"
# These are the commands that will be performed on warns
# If you skip a number the command from before will be performed
# You can also use non-AdvancedBan-Commands like 'broadcast' or 'clear %PLAYER%
# Variables: %PLAYER%, %REASON%, %COUNT%
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!"
# Here you can create permission-nodes for max-punishment-duration.
# The permission "ab.tempban.dur.1" would allow the player to ban max. for 600sec = 10min
# The permission "ab.tempwarn.dur.2" would allow the player to warn max. for 3600sec = 1h
# You can only create up to 10 perms. The perms can be overridden with "ab.COMMAND.dur.max"
TempPerms:
1: 600
2: 3600
3: 43200
Messages.yml
Here you can change every message. All Message-Variables that are available are used in the default settings.
Layout.yml
Messages:
Here you can define predefined reasons which can be used for (temp-)banning/muting/warning & kicking.
You can use them by just typing @LAYOUT-NAME instead of the reason. So you can have different layouts with different information for different reasons.
And once you have defined them you do not have to type the whole reason.
Time:
Here you can define timelayouts which can be used for temporary-punishments.
You can use them by just typing #LAYOUT-NAME instead of the duration. The time increases every time a player gets punished with the same layout.
# The default layouts are in the Message.yml file!
# Message-Layouts can not only be used for bans but also for mutes and warns
# Varibales: %OPERATOR%, %REASON%, %PREFIX%, %DURATION%
# For warns you have also the variable %COUNT% which will be
# replaced with the current amount of warns the player already resived
# Example usage: /ban Leoko @ExampleLayout
Message:
ExampleLayout:
- '%PREFIX% &7Banned for Hacking'
- '&c&oBannd by %OPERATOR%'
- '&7'
- "&cIt seems like you are using a"
- "&chacked client please disabled it!"
- "&cUnban in &8\xbb &7%DURATION%"
- '&7'
- '&8Unban application in TS or forum'
- "&eTS-Ip &8\xbb &c&ncoming soon"
- "&eForum &8\xbb &c&ncoming soon"
# You would use this time-layout for example like this: "/tempban Leoko #ExampleLayout Hacking in FFA"
# Or with "/tempwarn Leoko #ExampleLayout Advertising" or with "/tempwarn Leoko #ExampleLayout No capslock please"
# You can also combine this with MessageLayouts like "/tempban Leoko #ExampleLayout @Hacking"
Time:
ExampleLayout:
- '30m'
- '2h'
- '1d'
- '1w'
- '1mo'
- '2mo'
- '4mo'
- 'perma'
- Ban-, Kick-, Mute- and Warn-System
- Excellent performance
- BungeeCord & Bukkit/Spigot-Plugin in one
- PlayerHistory
- Easy to use API
- Advanced-UUID-Support
- Intern or Extern UUID-Fetcher
- Backup-UUID-Fetcher if Mojang-Servers are offline
- Change UUID-Fetcher REST-API
- MySQL or local embedded HyperSQL
- Full customizable
- Multiple lines in Kick- and Ban-Messages
- Pre-Defined Reasons
- Automatic time calculation [1th-tempban -> 1h | 2th-tempban -> 6h ...]
- Custome Time-Offset [Change the timezone if the server has a wrong time]
- Automatic-Warn actions
- Check-Command [UUID, IP, COUNTRY, BAN/MUTE/WARNS]
>> Plugins supporting AdvancedBan <<
Addon for Party and Friends System ( [USER=67188]@simonsator[/USER] ):
GUI Addon ( [USER=57888]@Boobah[/USER] ):
English:
(detailed)
(brief)
Dutch/Nederlands:
Russian:
Spanish:
If you have made one just send me the link per PM.
Requirements:
- AdvancedBan version 2.0.0 or higher
- MySQL-Server that is reachable from outside (not just localhost)
- Enabled MySQL not file
A webserver is not required
Note:
The webpanel is not something to download like the first one.
It's a website where you can register your server and the website will generate your own banpanel.
Also the panel does only display things it is not for administration just for monitoring.
Free MySQL-Databases:
BPlaced is not working
Here is a live DEMO:
Features:
- Secure login-system (sha1 & no-SQLInjections)
- Mobile optimized
- Flat design
- Own subdomain [NAME.banpanel.eu]
- Own messages & design [coming soon]
- Able to integrate into your webside
Register here:
Standalone WebInterface Alternative
Thanks to [USER=138878]@mathhulk[/USER] there is a web interface which you can download and place on your own WebServer this can be great if...
... your MySQL is only accessible for localhost
... you want to make major changes in the layout
This web interface does not include all features listed above, like the player-search or advanced mobile optimization.
Finally please note that all credits of this web interface got to [USER=138878]@mathhulk[/USER] and that we won't provide any support for it.
I don NOT vouch for the security of this web panel!
GitHub:
Example:
If you have any problems with the Plugin make sure the first check the console for any error messages with instructions how to solve the issue and to read the Known-Issues-Section below
If you still have the issue just post your it into the discussion area, on GitHub or on our Discord-Server 
The new Version of AdvancedBan was a lot of work for and I spend a lot of time and effort on it.
So if you appreciate my work I'd be very thankful about every donation ^^
>> Servers using AdvancedBan <<
BlizzardCraft Network
> mc.blizzardcraft.net
We use a Metrics-System called bStats which tracks information about your server
eg. Player, Bit-System, MC-Version, Server-System ect.
More information about bStats can be found here:
None yet 
All information about the API can be found on GitHub
评论 0
登录后参与评分
还没有评论,来抢沙发吧