AdvancedBan

AdvancedBan

外文名	AdvancedBan
最新版本	V2.3.0
源地址	https://www.spigotmc.org/resources/advancedban.8695/

综述

介绍

• AdvancedBan 是一个多合一的惩罚系统，带有警告、临时警告、禁言、临时禁言、封禁、临时封禁、IP封禁、临时IP封禁 和踢出。
• 该插件具有可配置的时间和消息布局，可出于某些原因自动计算和增加惩罚时间。
• AdvancedBan 还提供了一个完整的消息文件，因此您可以更改和翻译所有消息和一个包含许多有用设置的详细配置文件。
• 这是 BungeeCord 和 Bukkit/Spigot-Plugin 合二为一，它支持 MySQL 和本地嵌入式数据库以提供高性能。

由 Leoko

指令

[需要] <可选> | = 或 -s = 静默惩罚（不通知他人）

/kick <-s> [玩家] <原因 | @布局> 踢一名玩家

/ban /mute /warn /note <-s> [玩家] <原因 | @布局> 禁止/禁言/警告玩家/向玩家添加原因

/banip <-s> [玩家/IP] <原因 | @布局> 禁止玩家的IP。 如果您输入名称，它将使用缓存的 IP

/tempban /tempmute /tempwarn <-s> [玩家] [Xmo|Xd|Xh|Xm|Xs|#TIMELAYOUT] <原因 | @布局> 临时禁止/静音/警告玩家给定时间或自动时间计算的时间布局

/tempipban <-s> [玩家/IP] [Xmo|Xd|Xh|Xm|Xs|#TIMELAYOUT] <原因 | @布局> 临时IPban 一个给定时间或具有自动时间计算的时间布局的玩家 别名：/tipban

/change-reason [ID] [新原因] 通过id更改处罚原因

/change-reason [禁令/禁言] [玩家] [新理由] 更改玩家处罚的原因

/unban /unmute [玩家] 解禁令/解禁言玩家

/unwarn /unnote [ID] 删除警告/删除注释

/unwarn /unnote clear [玩家] 删除玩家的所有警告/注释

/unpunish [ID] 删除惩罚

/warns /notes <玩家> 查看您自己或玩家的警告/注意事项。

/check [玩家] 获取玩家状态：UUID/IP/Country/Ban-Status/Mute-Status/Warn-Count/Note-Count

/banlist <页面> 查看所有当前有效的惩罚

/history [玩家] <页面> 查看所有当前有效的惩罚 使用命令 - ab.history

/advancedban reload 重载插件

/advancedban help 显示advancedban的帮助

/systemprefs 显示一些对配置有用的系统信息

权限

ab.kick.use - /kick 踢出玩家 ab.kick.exempt - Immune to kicking 免疫被踢 ab.notify.kick - Receives notification 接收kick通知

ab.ban.perma - /ban 封禁 ab.ban.temp - /tempban 临时封禁 ab.ban.undo - /unban 解除封禁 ab.ban.exempt - Immune to ban 免疫封禁 ab.notify.ban - Receives notification 接收封禁通知 ab.undoNotify.ban - Receives notification when someone gets unbanned 当有人被解禁时收到通知

ab.notify.tempban - Receives notification 接收临时禁令通知

ab.ipban.perma - /ipban IP封禁 ab.ipban.temp - /tempipban 临时IP封禁 ab.notify.ipban - Receives notification 接收临时IP封禁通知

ab.tempipban.exempt - Immune to tempipban 对临时IP封禁免疫 ab.notify.tempipban - Receives notification 接收临时IP封禁通知

ab.mute.perma - /mute 禁言 ab.mute.temp - /tempmute 临时禁言 ab.mute.undo - /unmute 解除禁言 ab.mute.exempt - Immune to mute 免疫禁言 ab.notify.mute - Receives notification 接收禁言通知 ab.undoNotify.mute - Receives notification when someone gets unmuted 当有人取消禁言时收到通知

ab.notify.tempmute - Receives notification 接收临时禁言通知

ab.warn.perma - /warn 警告 ab.warn.temp - /tempwarn 临时警告 ab.warn.undo - /unwarn 解除警告 ab.warn.exempt - Immune to warn 免疫警告 ab.notify.warn - Receives notification 接收警告通知 ab.undoNotify.warn - Receives notification when someone gets unwarned 当没有人被警告是通知

ab.notify.tempwarn - Receives notification 接收临时警告通知

ab.note.use - /note ab.note.undo - /unnote ab.note.exempt - Immune to receiving notes ab.notify.note - Receives notification ab.undoNotify.note - Receives notification when someone gets unnoted

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 - Also shows IP

ab.changeReason - /change-reason ab.banlist - /banlist ab.history - /history ab.reload - /advancedban reload ab.help - /advancedban help ab.systemprefs - /systemprefs

配置

Config.yml: （翻译中）

1. AdvancedBan v2 - Coded by Leoko
2. For each setting, there is a small description.
3. Please read each description carefully before changing anything.
4. For more information visit: https://www.spigotmc.org/resources/advancedban.8695/
5. Do you want your own Plugin or Website? Check out our Dev-Page: http://dev.skamps.eu

1. If set to false all bans will be saved locally in a HSQLDB-Database

UseMySQL: false

1. Set to false if you want to have only short messages in the console
2. On startup and on the shutdown.

DetailedEnableMessage: true DetailedDisableMessage: true

1. This will be the default reason to be displayed if none is given

DefaultReason: "none"

1. Change this if your server has a different time that your users.
2. e.g.: ServerTime: 16:43 | Your Time: 13:43 | TimeDiff has to be set to -3
3. You can check the server time with /systemPrefs

TimeDiff: 0

1. This commands will be disabled for muted players
2. 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'

1. These players will not be able to get punished in any way
2. this also works if the player is offline

ExemptPlayers: - 'Leoko' - 'md5' - 'dutchy1001' - 'ItzSomebody'

1. The date-format which will be used for the %DATE% variable

DateFormat: "dd.MM.yyyy-HH:mm"

1. This is useful for bungeecord servers or server with permission systems which do not support *-Perms
2. So if you enable this you can use ab.all instead of ab.* or ab.ban.all instead of ab.ban.*
3. This does not work with negative permissions! e.g. -ab.all would not block all commands for that user.

EnableAllPermissionNodes: false

1. If you use external REST-APIs they will have to respond in JSON
2. The given APIs will only be used for NAME -> UUID
3. For UUID -> NAME will either use the official MojangAPI or the InternFetcher
4. To check if you can use the intern fetcher do /systemPerfs and compare your uuid
5. to the one you can see online on http://NamesMC.com
6. 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"

1. These are the commands that will be performed on warns
2. If you skip a number the command from before will be performed
3. You can also use non-AdvancedBan-Commands like 'broadcast' or 'clear %PLAYER%
4. 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!"

1. Here you can create permission-nodes for max-punishment-duration.
2. The permission "ab.tempban.dur.1" would allow the player to ban max. for 600sec = 10min
3. The permission "ab.tempwarn.dur.2" would allow the player to warn max. for 3600sec = 1h
4. 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