OmniBans
欢迎!OmniBans 是专为你 Minecraft 网络设计的综合管理套件。它作为插件运行于你的 Paper、Spigot 或 Folia 服务器,并附带两个轻量级的桥接插件(分别用于 Velocity 和 BungeeCord),确保你在任一服务器上执行的封禁或静音操作会立即在整个网络中生效。感谢试用,我们希望它能让你运营服务器变得更加轻松。<3
如果你是第一次进行设置,INSTALL.md 将逐步引导你完成整个过程。以下内容假设插件已经正常运行,主要介绍 OmniBans 在日常使用中能为提供的功能。
支持的版本
| 项目 |
支持范围 |
| Minecraft |
1.8 至 26.2 |
| 服务端软件 |
Spigot, Paper, Folia |
| 代理端软件 |
Velocity, BungeeCord |
| Java |
17 或更高版本(见下方说明) |
Folia 的支持仅适用于 Folia 本身覆盖的 Minecraft 版本(1.19.4 及更高版本)。在旧版本上,会自动使用标准的 Bukkit 调度器,无需任何配置。
关于 Minecraft 版本号: Mojang 从 2026 年开始改用基于年份的版本号格式。2026 年发布的版本编号为 26.1、26.2 等,不再延续旧的 1.x 格式。采用旧格式的最后一个发布版本属于 1.21.x 系列。因此,上述支持范围涵盖了从 1.8 开始贯穿整个 1.x 时代,并延伸至新的 26.x 时代。
关于 Java: 该插件编译时目标版本为 Java 17,这意味着任何运行 Java 17 或更高版本的服务器都可以加载它。适合你服务器的 Java 版本取决于你所运行的 Minecraft 版本。运行 1.18 至 1.20.4 的服务器至少需要 Java 17。运行 1.20.5 至 1.21.x 的服务器至少需要 Java 21。运行 26.1 和 26.2 的服务器需要 Java 25,但由于 Java 在此方向上具有向后兼容性,Java 25 仍然可以加载为 Java 17 编译的插件。
启动方法
使用 Gradle 构建项目(./gradlew build)。你将得到三个 jar 文件:
paper/build/libs/OmniBans-Paper.jar 放入你运行的每个 Paper、Spigot 或 Folia 服务器的 plugins 文件夹中。
velocity/build/libs/OmniBans-Velocity.jar 放入你的 Velocity 代理端的 plugins 文件夹中。
bungee/build/libs/OmniBans-Bungee.jar 放入你的 BungeeCord 代理端的 plugins 文件夹中。
如果你只有一个服务器且没有代理端,则只需使用 Paper jar 文件即可。
默认情况下,OmniBans 将其所有数据存储在其自身文件夹内的一个小型 SQLite 文件中,这无需安装任何额外内容或进行任何设置,只要启动服务器即可立即工作。如果你只运行一个服务器,这是最佳选择。如果你运行多个服务器并希望封禁能在服务器之间同步,那么每个服务器和你的代理端都需要指向同一个 MySQL 数据库,请在 config.yml 的 storage 下(以及每个代理端 config.properties 的相应部分)进行设置。在这种情况下,你唯一需要自行安装的只是已创建好该数据库的 MySQL 或 MariaDB 服务器。
与玩家沟通
OmniBans 发送的所有消息,无论是封禁界面、聊天警告还是广播,都来自 messages.yml,你可以按照自己最熟悉的风格编写。你可以使用普通的 & 颜色代码(如 &c)、旧式的 section sign 代码、MiniMessage 标签(如 <red> 和 <gradient:#ff0000:#0000ff>)、以 &#ff00aa 形式编写的十六进制代码,甚至如果确实需要,可以使用原始聊天 JSON。OmniBans 会自动识别你的写法并正确渲染,无论使用 MiniMessage 自带的渐变标签还是手动编写一系列十六进制代码,渐变效果都能正常工作。
如果玩家恰好使用的是纯 Spigot 而非 Paper,OmniBans 仍能正确渲染你的格式。由于 Spigot 完全没有内置 Adventure 的文本系统,OmniBans 会在发送前悄悄地将你的消息转换为 Spigot 自己的聊天组件格式,这样玩家看到的颜色和样式完全一致。
命令
/ban, /tempban, /unban, /banip, /unbanip, /mute, /tempmute, /unmute, /kick, /warn, /note, /history, /check, /banlist, /mutelist, /alts, 以及 /omnibans reload, /omnibans version, /omnibans config, /omnibans messages。所有这些命令都支持完善的 Tab 补全功能。例如,输入 /ban Ste 并按 Tab 键会列出名字以该字母开头的在线玩家;/tempban 会提供合理的持续时间建议,如 1d 或 7d;原因可以从 config.yml 下 punishments.common-reasons 中的快速列表中选择。如果玩家实际上没有执行某条命令的权限,他们也不会看到任何 Tab 补全建议,因此从某种意义上说,管理命令对其他所有人也是不可见的。
/alts <player> 显示指定玩家的已知小号账号,并告知每个小号当前是否被封禁或静音,以及他们共享的 IP 地址是否被封禁或静音。如果你检查的玩家是操作员,或者通过 LuckPerms 拥有 * 权限,OmniBans 只会提示其享有豁免权,而不会显示有关他们的任何信息,因为管理账号不应以此方式进行交叉引用。
在游戏中编辑配置
/omnibans config 和 /omnibans messages 会将 config.yml 和 messages.yml 以游戏内菜单的形式打开,每个设置对应一个物品。像 redis.enabled 这样的开关只需点击即可切换,并根据当前状态显示为绿色或红色物品。其他类型(数字、文本或列表如 punishments.common-reasons)则会关闭菜单,并在聊天栏中要求你输入新值。此时输入 cancel 可取消操作而不做任何更改。列表应以逗号分隔的纯文本形式输入。如果你正在编辑多行消息模板,可以在希望换行的位置输入 \n。每处更改都会立即保存到磁盘并生效,无需随后再运行 /omnibans reload。
跨版本更新保持 config.yml 和 messages.yml 同步
每次 OmniBans 启动时,它都会悄悄地将你现有的 config.yml 和 messages.yml 与当前版本所期望的内容进行比对。如果新版 OmniBans 引入了此前不存在的设置项,它会使用默认值自动将其添加到你的文件中,而你原本已有的所有设置都保持原样,绝不会因这一过程而被覆盖。这意味着你可以更新 OmniBans 并保留旧配置文件,无需手动复制任何新设置。
只有当某个版本的 OmniBans 明确停止使用某项设置时,该设置才会从你的文件中被移除。发生这种情况时,系统会干净地移除该项,并在控制台打印一行日志,明确指出移除了什么内容以及来自哪个文件。以这种方式不会触碰任何其他内容:你自己添加的、OmniBans 从未知晓的设置(无论是否为默认值)将永远保持不变。在任何实际更改发生之前(无论是添加还是移除),系统在更改前的文件状态会被备份到一个同目录下的 .bak 文件中,以便在需要时可以一键恢复之前的状态。
有两点诚实的限制值得了解。首先,如果未来版本中某项设置只是被重命名而非简单地添加或删除,此系统不会自动将你旧的值迁移到新名称下,因为重命名属于不同于添加或删除的变更类型,而这正是本系统专门设计来处理的情形。若发生此类情况,本 README 会在相应更新时提供清晰的指引。其次,此机制仅在确实需要更改时才检查并重写文件;但在那次更新发生时,你在 config.yml 或 messages.yml 中手写的注释将不会保留下来。这是因为 Bukkit 读取和写入 YAML 文件的通用长期限制所致,并非 OmniBans 特有的问题。无论如何,你的设置及其值始终会被完美保留,受影响的仅是你周围的注释,且仅限于实际发生更改的更新。
整个上述机制仅适用于 config.yml 和 messages.yml。Velocity 和 BungeeCord 代理桥接使用的是 config.properties 文件,这是一种不同且更简单的格式,不受以上任何影响。
防止玩家受到意外处罚
你可以将这些权限之一授予特定玩家,以确保任何人——包括偶尔情绪不佳的信任度高的管理员——都不会误封禁、静音、踢出或警告他们:
omnibans.exempt.ban
omnibans.exempt.mute
omnibans.exempt.kick
omnibans.exempt.warn
omnibans.exempt.banip
这些权限默认情况下不会授予任何人。由你来决定谁获得这些权限。
接管 Essentials 和原版命令
Minecraft 本身自带了 /ban、/ban-ip、/kick、/pardon 和 /pardon-ip 命令,而 EssentialsX 历史上也提供了自己的 /mute 等命令。OmniBans 旨在成为服务器上实际处理 moderation 的核心,因此它接管了所有这些命令标签,包括两个拼写与其自身命令略有不同的命令(ban-ip 以及 pardon/pardon-ip),这样即使玩家在其他服务器养成的习惯或肌肉记忆触发了原版命令,最终仍会由 OmniBans 处理,而非其他插件。如果安装了 Essentials,OmniBans 会在启动时检测到这一点,并明确重新接管你们双方可能都想使用的每一个命令,无论哪一个先加载,同时会在控制台记录一行日志确认已执行此操作。
关于玩家隐私的注意事项
OmniBans 需要记住玩家连接的地址,以便封禁 IP 并检测多个账号是否共享同一地址,但它永远不会向任何人展示该地址——无论是在聊天消息、命令输出还是 Discord 消息中。如果你通过 /check 或 /alts 查询某位玩家,你会看到有多少个地址被记录,以及其中是否有任意一个当前被封禁或静音,但绝不会显示地址本身。唯一出现地址的情况是工作人员自己在如 /banip 这样的命令中输入了地址,这是他们自己的输入行为,而非 OmniBans 返回给他们的信息。
我们在此坦诚相告。在开发过程中,曾有几个地方疏忽导致地址在确认消息中回显给了工作人员(/banip 的成功消息、/unbanip 的成功与失败消息,以及 /check 的摘要行)。这些问题已全部修复,/unbanip 现在也支持直接使用玩家名称,从而你几乎无需再手动输入地址。我们选择公开说明此事,而不是悄悄打补丁后一言不发。
随后又发现了另一处同类性质的泄露:当你直接在 /banip 中输入裸 IP 地址而未关联任何玩家时,OmniBans 会将该字面意义上的地址作为处罚的显示名称存储,这会导致它在原本用于显示玩家名称的地方出现,例如全服封禁广播、Discord Webhook 以及 /banlist。该问题已在源头修复,针对裸 IP 的封禁不再保留其地址作为名称,所有显示处罚名称的地方现在都会 fallback 到通用标签,即便未来某些变更意外尝试暴露地址也不会再发生。此外,在我们处理这些问题期间,也将 /banlist 和 /mutelist 的默认权限收紧为仅限操作员可见,因为即使不包含地址,完整的封禁列表也不是每位玩家都需要查看的内容。
在 Discord 上通知你的管理员
OmniBans 拥有两种完全独立的 Discord 推送方式,你可以单独使用其中一种、两者都用,或者都不使用。
简单的方案是使用 Webhook,通过在 config.yml 中设置 discord.webhook-url 和 discord.enabled 来启用。Webhook 只是 Discord 为单个频道提供的一个单向 URL,完全不需要机器人。开启此功能后,每当发生封禁、IP 封禁、静音、IP 静音、踢出或警告时,OmniBans 都会向该频道发送一个纯文本嵌入消息(embed),其中包含玩家名称、执行操作的管理人员以及原因。Webhook 没有提及角色的概念,OmniBans 也不会尝试这样做;此外,Webhook 无法获取任何关于小号的信息,它仅发布这一种简单的消息。
更完整的方案是一个真正的 Discord 机器人,通过 discord-bot 部分进行配置。它触发与 Webhook 完全相同的事件,并增加第二种类型的消息:每当一名非操作员且不持有 LuckPerms 的 * 权限的玩家加入服务器,且被发现拥有已知的小号时(即触发游戏内管理员警告的相同情况),机器人就会发送通知。机器人发送的每个嵌入消息还会告知你该玩家的已知小号及其哪些小号已被封禁,这与游戏内 /alts 命令的方式相同,而普通的 Webhook 嵌入不包含这些信息;并且它可以可选地 ping 某个角色,以便你的管理团队能够注意到这些通知。在 config.yml 中设置如下:
discord-bot:
enabled: true
token: "your bot's token"
server-id: "your discord server's id"
channel-id: "the channel you want these messages posted in"
admin-role-id: "the role you want pinged, optional"
你需要将你自己的机器人邀请到你的服务器,并授予其在相应频道发送消息和嵌入内容的权限。与 OmniBans 中的其他所有功能一样,无论是 Webhook 还是机器人嵌入,都永远不会包含地址信息。
关于快速发出大量惩罚的说明
如果你曾在服务器控制台中看到在封禁后立即出现的提及 AsyncCatcher 和 player kick 的错误,并且在连续发生多次惩罚时伴随明显的卡顿,那是一个真实的 Bug,而非你操作层面的问题。OmniBans 在保存封禁或静音记录后执行的某些操作——包括踢出玩家和广播公告——原本是在后台线程上运行的,而不是在主服务器上运行,但 Minecraft 不允许对这类操作使用后台线程。即使出现这种情况,惩罚本身仍然会被正确应用,但重复出现的错误确实造成了额外的开销,也就是你可能注意到的轻微卡顿。此问题已修复,现在相关工作始终按照应有的方式在主线程上执行。
关于 Gradle 构建的简要说明
如果你的构建在 shadowJar 阶段失败,并出现提及 org.objectweb.asm.commons.Remapper 的奇怪错误,那是 Shadow 插件自身的包重定位步骤在某些版本的 Shadow 中遇到了问题,与 OmniBans 实际包含的代码无关。构建脚本目前已不再要求 Shadow 执行任何包的重新定位,因为正是这个重定位步骤导致了各种各样的持续失败。OmniBans 所需的所有依赖项仍会直接打包到每个 jar 文件中,只是保留了其原始包名而未进行重命名。这是一种完全正常的插件分发方式,仅当你的服务器上另一个插件恰好捆绑了相同库的冲突版本时才会产生影响。
仍在计划中的一些事项
/history、/banlist 和 /mutelist 命令目前输出到聊天栏而非打开菜单,虽然这样已经足够好用,但未来若能提供一个完善的界面会更好。此外,目前还没有针对诸如玩家封禁次数等数据的 PlaceholderAPI 扩展。如果有时间,这两项都将是非常受欢迎的补充功能。
项目所在处
OmniBans 的开发位于 github.com/Hihelloy-main/OmniBans。如果你遇到任何与本文档描述不符的问题,请前往此处反馈。本仓库不接受通过拉取请求(pull requests)进行的直接贡献,因此请勿提交 PR,但我们非常欢迎并认真处理问题和 Bug 报告。再次感谢使用 OmniBans。 <3
OmniBans
Welcome! OmniBans is a moderation suite for your Minecraft network. It runs as a plugin on your Paper, Spigot, or Folia server, and it comes with two small bridge plugins for Velocity and BungeeCord so a ban or mute you issue on one server takes effect everywhere on your network. Thanks for trying it out, and we hope it makes running your server a little easier. <3
If this is your first time setting it up, INSTALL.md walks through the whole process step by step. Everything below assumes it is already running and is more about what OmniBans can do for you day to day.
Supported versions
| What |
Supported range |
| Minecraft |
1.8 through 26.2 |
| Server software |
Spigot, Paper, Folia |
| Proxy software |
Velocity, BungeeCord |
| Java |
17 or newer (see note below) |
Folia support only applies to versions of Minecraft that Folia itself covers (1.19.4 and later). On older versions the standard Bukkit scheduler is used automatically, no configuration needed.
A note on Minecraft version numbers: Mojang switched to a year-based versioning format starting in 2026. Versions released in 2026 are numbered 26.1, 26.2, and so on, rather than continuing the old 1.x format. The last release in the old format was in the 1.21.x series. So the supported range above goes from 1.8 through the whole 1.x era and on into the new 26.x era.
A note on Java: The plugin is compiled targeting Java 17, meaning any server running Java 17 or newer can load it. The right Java version for your server depends on which Minecraft version you run. Servers on 1.18 through 1.20.4 need at least Java 17. Servers on 1.20.5 through 1.21.x need at least Java 21. Servers on 26.1 and 26.2 need Java 25, which can still load plugins compiled for Java 17 since Java is always backward compatible in that direction.
Getting it running
Build the project with Gradle (./gradlew build). You will end up with three jars:
paper/build/libs/OmniBans-Paper.jar goes into the plugins folder of every Paper, Spigot, or Folia server you run.
velocity/build/libs/OmniBans-Velocity.jar goes into your Velocity proxy's plugins folder.
bungee/build/libs/OmniBans-Bungee.jar goes into your BungeeCord proxy's plugins folder.
If you only have one server and no proxy, you only need the Paper jar.
By default OmniBans stores everything in a small SQLite file right inside its own folder, which needs nothing installed and nothing set up, it just works the moment you start the server. That is the right choice if you only run one server. If you run more than one server and want a ban to follow a player between them, every server and your proxy need to point at the same MySQL database instead, set under storage in config.yml (and the matching section of each proxy's config.properties). A MySQL or MariaDB server with that database already created is the only thing you would ever need to install yourself, and only for that network case.
Talking to your players
Every message OmniBans sends, whether it is a ban screen, a chat warning, or a broadcast, comes from messages.yml, and you can write it in whatever style you are most comfortable with. You can use plain ampersand color codes like &c, the old section sign codes, MiniMessage tags like <red> and <gradient:#ff0000:#0000ff>, hex codes written as &#ff00aa, or even raw chat JSON if you really want to. OmniBans figures out what you wrote and renders it correctly either way, and gradients work whether you use MiniMessage's own gradient tag or just hand write a run of hex codes.
If a player happens to be on plain Spigot rather than Paper, OmniBans still renders your formatting correctly. Spigot does not have any of Adventure's text system built in at all, so OmniBans quietly converts your message into Spigot's own chat component format before sending it, and the player sees exactly the same colors and styling either way.
Commands
/ban, /tempban, /unban, /banip, /unbanip, /mute, /tempmute, /unmute, /kick, /warn, /note, /history, /check, /banlist, /mutelist, /alts, and /omnibans reload, /omnibans version, /omnibans config, or /omnibans messages. Every one of them tab completes properly, so typing /ban Ste and pressing tab will offer you online players whose name starts with that, /tempban will offer you sensible duration suggestions like 1d or 7d, and reasons can be picked from a quick list you control yourself in config.yml under punishments.common-reasons. A player who does not actually hold the permission for a given command will not see it offer any tab suggestions either, so staff commands stay invisible in that sense to everyone else too.
/alts <player> shows you a player's known alt accounts, and tells you whether each alt is currently banned or muted, and whether the address they share is itself banned or muted. If the player you check is an operator, or holds the * permission through LuckPerms, OmniBans will simply tell you they are exempt rather than showing anything about them, since staff accounts should not be cross referenced this way.
Editing your configuration without leaving the game
/omnibans config and /omnibans messages open config.yml and messages.yml as an in game menu, one item per setting. A toggle like redis.enabled is just a click away from flipping, shown as a green or red item depending on its current state. Anything else, a number, a piece of text, or a list like punishments.common-reasons, closes the menu and asks you to type the new value in chat, where typing cancel backs out without changing anything. A list is typed as plain text separated by commas, and if you are editing a multi line message template you can type \n anywhere you want a line break. Every change saves to disk and takes effect immediately, no need to also run /omnibans reload afterward.
Keeping config.yml and messages.yml up to date across updates
Every time OmniBans starts, it quietly checks your existing config.yml and messages.yml against whatever the current version expects. If a newer version of OmniBans introduces a setting that simply was not there before, it gets added to your file automatically using its default value, and everything you already had set stays exactly as you left it, nothing existing is ever overwritten by this. This means you can update OmniBans and keep your old configuration files in place without ever needing to manually copy new settings over by hand.
A setting is only ever removed from your file if a version of OmniBans deliberately stopped using it, and when that happens it is removed cleanly and a line is printed to your console naming exactly what was removed and from which file. Nothing else is ever touched this way, a setting you added yourself that OmniBans has never heard of, default or not, is always left alone forever. Just before any actual change is made, whether something was added or removed, the file as it was right before that change is copied to a .bak file next to it, so the previous state is always one click away if you ever need it.
Two honest limitations worth knowing about. First, if a setting is ever renamed in a future version rather than simply added or removed, this system does not carry your old value over to the new name on its own, since a rename is a different kind of change than an addition or a removal, the kind this system was specifically built to handle. If that ever happens, this README will carry clear instructions for that particular update at the time. Second, this only checks and rewrites your file when something actually needs to change, but on the update where it does, any comments you had hand written into config.yml or messages.yml will not survive that rewrite, since that is a long standing limitation of how Bukkit reads and writes yaml files in general, not something specific to OmniBans. Your settings and their values are always preserved perfectly either way, only your own comments around them are at risk, and only on an update that actually changes something.
This entire system only applies to config.yml and messages.yml. The Velocity and BungeeCord proxy bridges use a config.properties file instead, a different and much simpler format, and that file is not affected by any of this.
Protecting players from accidental punishment
You can hand a player one of these permissions to make sure nobody, even a trusted moderator having a bad day, can ban, mute, kick, or warn them by mistake:
omnibans.exempt.ban
omnibans.exempt.mute
omnibans.exempt.kick
omnibans.exempt.warn
omnibans.exempt.banip
None of these are given to anyone by default. You decide who gets them.
Taking over from Essentials and vanilla commands
Minecraft itself ships with its own /ban, /ban-ip, /kick, /pardon, and /pardon-ip, and EssentialsX has historically provided its own /mute and friends too. OmniBans is built to be the one actually handling moderation on your server, so it claims all of these labels for itself, including the two spelled slightly differently than its own commands (ban-ip and pardon/pardon-ip), so a habit formed on another server or a muscle memory vanilla command still reaches OmniBans rather than something else. If Essentials is installed, OmniBans notices this during startup and explicitly re-claims every command the two of you would otherwise both want, regardless of which of you happened to load first, and logs a line to console confirming it did so.
A note about your players' privacy
OmniBans needs to remember which address a player connects from in order to ban an address and to notice when two accounts share one, but it will never show that address to anyone, in a chat message, in a command's output, or in a Discord message. If you ask /check or /alts about a player, you will see how many addresses are on record and whether any of them are currently banned or muted, but never the address itself. The only time an address ever appears anywhere is if a staff member types it themselves into a command like /banip, and that is their own input, not something OmniBans hands back to them.
We want to be upfront with you here. While building this, a couple of spots slipped through where an address was being shown back to staff in a confirmation message (/banip's success message, /unbanip's success and failure messages, and /check's summary line). Those have all been fixed, /unbanip now also accepts a player's name so you rarely need to type an address at all, and we are telling you about it rather than quietly patching it and saying nothing.
A second leak in the same spirit was found afterward. When you typed a bare address straight into /banip with no player attached to it, OmniBans was storing that literal address as the punishment's display name, which then surfaced in places meant for player names, the server wide ban broadcast, the Discord webhook, and /banlist. That has been fixed at the source, a bare address ban no longer keeps the address as its name at all, and every place that displays a punishment's name now falls back to a generic label instead of ever being able to show an address, even if some future change accidentally tried to. /banlist and /mutelist were also tightened to operators only by default while we were in there, since a full list of who is banned, even with addresses already kept out of it, is not something every player needs to see.
Telling your administrators on Discord
OmniBans has two completely separate ways to post to Discord, and you can use either one, both, or neither.
The simple one is a webhook, set through discord.webhook-url and discord.enabled in config.yml. A webhook is just a one way url Discord gives you for a single channel, no bot needed at all. With this turned on, OmniBans posts a plain embed to that channel every time a ban, ip ban, mute, ip mute, kick, or warn happens, naming the player, the staff member, and the reason. A webhook has no concept of mentioning a role and OmniBans does not attempt it, and a webhook never knows anything about alt accounts, it only ever posts that one simple kind of message.
The fuller one is an actual Discord bot, set through the discord-bot section. It fires for the exact same events as the webhook, plus a second kind of message: whenever a player who is not an operator and does not hold LuckPerms' * permission joins and turns out to have a known alt account, the same situation that triggers the in game staff warning. Every embed the bot sends also tells you the player's known alts and which of those alts are themselves banned, the same way /alts does in game, which the plain webhook embed does not include, and it can optionally ping a role so your staff actually notice it. Set this up in config.yml:
discord-bot:
enabled: true
token: "your bot's token"
server-id: "your discord server's id"
channel-id: "the channel you want these messages posted in"
admin-role-id: "the role you want pinged, optional"
You will need to invite your own bot to your server and give it permission to send messages and embeds in that channel. As with everything else in OmniBans, neither the webhook nor the bot embed ever contains an address.
A note on issuing a lot of punishments quickly
If you ever saw a server console error mentioning AsyncCatcher and player kick right after a ban, alongside a bit of noticeable lag when several punishments happened in quick succession, that was a real bug, not something on your end. A few things OmniBans does after saving a ban or mute, kicking the player and broadcasting the announcement, were running on a background thread instead of the server's main thread, which Minecraft does not allow for actions like that. The punishment itself was always still applied correctly even when this happened, but the repeated error was real overhead, which is exactly the slight lag you may have noticed. This has been fixed, that work now always happens on the main thread the way it is supposed to.
A quick word on the Gradle build
If your build fails during shadowJar with a strange error mentioning org.objectweb.asm.commons.Remapper, that is Shadow's package relocation step itself running into trouble with certain Shadow versions, not anything about the code OmniBans actually contains. The build no longer asks Shadow to relocate any package at all, since that relocation step was exactly what kept failing in different ways. Every dependency OmniBans needs still gets bundled straight into each jar, it just keeps its original package name rather than being renamed, which is a perfectly normal way to ship a plugin and only matters if another plugin on your server happens to bundle a conflicting version of the very same library.
A couple of things still on the list
/history, /banlist, and /mutelist print to chat rather than opening a menu, which works well enough but a proper interface would be nicer one day. There is also no PlaceholderAPI expansion yet for things like a player's ban count. Both would be welcome additions whenever there is time for them.
Where this lives
OmniBans is developed at github.com/Hihelloy-main/OmniBans. If you run into something that does not work the way this document says it should, that is the right place to say so. Direct contributions through pull requests are not accepted on this repository, so please do not open one, but issues and bug reports are always genuinely welcome and read. Thanks again for using OmniBans. <3
评论 0
登录后参与评分
还没有评论,来抢沙发吧