OmniPanel
一个面板。一个连接的系统。全面掌控你的 Minecraft 服务器。
由 Kingez341yt 创建并拥有
版权所有 © 2026 Kingez341yt。保留所有权利。
许可证:专有软件 — 保留所有权利
文档构建版本:18.9.114
开发者 API:4.8.0
权限服务 API:5.0.0
关于 OmniPanel
OmniPanel 是一款专为现代 Minecraft 服务器打造的一站式管理、审核、玩家管理和服务器实用插件。
与其堆叠用于员工工具、惩罚、等级、家园、套件、区域、玩家检查、维护、活动、认证和服务器管理的独立插件,OmniPanel 通过一个中央平台将这些系统连接起来。
该插件的设计围绕菜单、对话框、共享权限检查和一致的工作流程展开,而不是强制员工记住数十个命令。
无论你是运行 SMP、社区服务器、创作者服务器、私人服务器还是更大的网络,OmniPanel 都为你的员工提供了一个管理服务器的统一场所。
为什么选择 OmniPanel?
普通服务器很快可能会运行以下独立插件:
- 审核(Moderation)
- 惩罚(Punishments)
- 员工模式(Staff Mode)
- 玩家检查(Player inspection)
- 等级(Ranks)
- 家园(Homes)
- 套件(Kits)
- 区域(Regions)
- 活动(Events)
- 认证(Authentication)
- 维护(Maintenance)
- Discord 集成
- 玩家实用工具(Player utilities)
- 管理工具(Administrative tools)
这通常意味着独立的权限系统、不同的界面、重叠的命令、重复的数据,以及互不知晓的插件。
OmniPanel 的构建方式不同。
一个面板。
一个连接的权限系统。
一套审核工作流程。
一套玩家管理工具。
一个供其他插件集成的 API。
主面板
一切始于:
/panel
面板通过感知权限的界面提供对 OmniPanel 管理系统的访问。
功能包括:
- 基于部分的导航
- 功能级权限
- 搜索
- 分页
- 上下文感知菜单
- 玩家选择
- 确认屏幕
- Paper Dialog 集成
- 权限感知按钮
- 仅限员工的行动
- 在适当情况下向公开玩家显示菜单
- 后退和关闭导航
- 支持扩展以添加附加组件
打开 /panel 并不会自动授予对其内部所有内容的访问权限。
每个受保护的功能仍然会在服务器端进行检查。
面板可见性与访问控制
OmniPanel 使用集中的访问系统来控制受保护的面板功能。
管理员可以授予对以下内容的访问权限:
这使得能够向员工提供他们所需的确切内容。
例如:
- 助手可以检查玩家,但不能编辑物品栏。
- 审核员可以冻结、监禁、传送和管理玩家,而无需获得等级管理权限。
- 建造者可以获得区域和建造控制权限,但无惩罚权限。
- 开发人员可以获得诊断和技术工具。
- 所有者保留完全访问权限。
内置的 面板可见性与访问控制 编辑器允许授权员工:
- 选择玩家或等级
- 选择完全访问或自定义访问
- 浏览各个部分
- 启用或禁用单个功能
- 在应用更改之前审查更改
- 授予或撤销整个部分
在可用情况下,LuckPerms 集成仍具有权威性。
尊重显式权限授予、拒绝、上下文以及外部的 LuckPerms 更改。
玩家浏览器
通过 OmniPanel 浏览玩家,无需手动输入用户名。
玩家信息可以包括:
- 在线状态
- 平台
- 等级
- 最后上线时间
- 当前世界
- 游戏时长
- 家园
- 惩罚历史
- 员工备注
- 存在状态
玩家操作根据员工权限提供对其他工具的访问。
玩家操作
玩家操作组织成如下类别:
- 关怀与移动(Care & Movement)
- 审核与记录(Moderation & Records)
- 实用工具(Utilities)
- 高级(Advanced)
- 其他玩家工具(Additional Player Tools)
可用操作取决于员工成员的权限。
集成的工具包括:
- 传送
- 治疗
- 物品栏检查
- 末影箱检查
- 惩罚历史
- 员工备注
- 冻结
- 监禁
- 审核工具
- 实用工具操作
目标操作绑定到所选玩家,而不是静默回退到员工成员。
物品栏检查
OmniPanel 包含供员工使用的共享物品栏检查会话。
示例:
/invsee inventory <player>
查看和编辑是分开的权限。
物品栏系统支持:
- 只读检查
- 授权编辑
- 存储槽位
- 盔甲
- 副手
- 并发会话保护
- 物品栏事务守卫
- 离线玩家检查
- 离线编辑备份
- 离线编辑活跃期间的登录保护
只读会话无法将更改写回目标玩家。
真实玩家物品被视为物品,而非 GUI 按钮。
扩展末影箱
OmniPanel 包含一个扩展的末影箱系统,由其现有的存储数据库提供支持。
功能包括:
- 54 个可用的箱子槽位
- 员工检查
- 在允许的情况下个人
/echest 访问
- SQLite 持久化
- 备份
- 旧数据导入
- 原版同步
- 物理开合声音
- 盖子动画
- 共享查看者处理
- 损坏防护
无效的存储物品数据会失败关闭,而不是静默地将存储物品替换为空槽位。
惩罚系统
OmniPanel 包含供员工审核的完整惩罚工作流程。
支持的行动包括:
- 警告
- 临时警告
- 静音
- 临时静音
- 封禁
- 临时封禁
- IP 封禁
- 临时 IP 封禁
- 踢出
- 冻结
- 监禁
- 撤销
- 员工备注
- 惩罚记录
临时惩罚需要有效的有限持续时间,并遵守配置的限值。
惩罚使用权威后端,以便 GUI 操作、API 提交、记录和执法保持连接。
惩罚记录
惩罚历史可以包括:
- 执行人员
- 目标
- 案例
- 来源
- 行为
- 原因
- 持续时间
- 时间戳
- 结果
- 可用证据
历史记录使用紧凑摘要,完整详情可通过现有的记录界面查看。
警告、踢出、撤销以及过期的临时处罚不会错误地显示为永久活跃制裁。
处罚预设
OmniPanel 包含针对已审核的 Moderation(管理)场景的可搜索处罚预设,例如:
- 欺诈
- 网络钓鱼
- 恶意链接
- 规避
- Bot(机器人)攻击
- 漏洞利用
- 骚扰
- 垃圾信息
自定义服务器预设仍受支持且保持权威性。
正常的 Minecraft 行为,如合法交易、赠品活动或常规 PvP,不会被自动视为违规。
持续时间构建器
临时处罚支持标准的持续时间单位,包括:
在应用临时处罚之前会处理持续时间验证。
AutoMod(自动管理)
OmniPanel 包含内置的聊天管理和证据处理功能。
功能包括:
- 屏蔽词检测
- 严格词列表
- 单词边界匹配
- 当前消息证据
- 垃圾信息检测
- 管理警报
- 可配置的信心要求
- 保存的证据
- 工作人员审核流程
- 原子化词列表更新
命令包括:
/automod words add
/automod words remove
/automod words list
以及:
/automod strictwords add
/automod strictwords remove
/automod strictwords list
屏蔽词检查使用的是实际的当前消息内容,而不是先前消息中的过时内容。
AI 管理证据
当配置了 AI 辅助管理时,OmniPanel 将 AI 输出视为供审核的证据,而非自动真理。
管理上下文考虑到了正常的 Minecraft 活动,包括:
自动决策需要满足以下条件:
- 已识别的分类
- 来自真实消息的证据
- 逐字匹配的引用
- 上下文支持
- 配置的置信度阈值
默认的证据置信度阈值为:
0.95
高影响或不确定的案件默认仍以审核为导向。
证据记录可以包含:
- 原始消息
- 匹配引用
- SHA-256 哈希
- 捕获时间
- 来源
- 模型置信度(如果可用)
AI 置信度是一种 safeguards(保障措施),而非确凿证据。
Staff Mode(员工模式)
OmniPanel 包含内置的 Staff Mode(员工模式),并具备安全的库存恢复功能。
功能包括:
- 员工库存备份
- 员工工具
- Vanish(隐身)支持
- 加入/退出恢复
- 库存恢复
- 飞行状态恢复
- 碰撞体状态恢复
- 拾取状态恢复
- 保护状态恢复
- 断开连接或关机后的恢复
- 持久化工具标识符
- 受保护的工具移动
- 员工模式标题
- 在线行动栏
如果无法备份员工库存,进入 Staff Mode 时会安全失败。
员工工具
可用的管理工具包括:
- Sentinel Blade(哨兵之刃)
- Excavator Pickaxe(挖掘机镐)
- Timber Axe(伐木斧)
- Justice Hammer(正义之锤)
可以单独授予工具,而不必要求访问所有管理工具。
与处罚相关的工具仍需相应的处罚权限。
发放员工工具不会覆盖已占用的库存槽位。
Staff Chat(员工聊天)
Staff Chat 使用相同的访问系统来:
默认玩家和 Member(成员)玩家不会自动接收 Staff Chat 消息。
Staff 消息会在正常公共聊天审计或 Discord 转发之前进行路由。
如果在待发送的 Staff Chat 消息发出之前撤销了访问权限,该消息将被取消,而不是泄露到公共聊天中。
Emergency Staff Teleport(紧急员工传送)
OmniPanel 包含:
/stafftp [message]
这允许授权的工作人员发送私人的紧急传送邀请。
工作人员可以使用以下方式响应:
- 可点击的 Accept(接受)
- 可点击的 Deny(拒绝)
/stafftp accept
/stafftp deny
/tpaccept
/tpdeny
紧急员工传送请求始终需要明确接受,即使启用了普通 TPA 自动接受功能。
请求是会话绑定的,会正确过期,并且在重新连接后无法重用。
Public Teleport Requests(公开传送请求)
普通的玩家传送命令仍然公开可用:
/tpa
/tpahere
/tpaccept
/tpdeny
/tpcancel
/tpauto
玩家可以配置:
紧急员工请求与普通自动接受行为保持分离。
Homes(家园)
OmniPanel 包含公开的家园系统。
命令包括:
/home
/homes
/sethome
/delhome
/unsethome
功能包括:
- 命名家园
- 传送
- GUI 访问
- 安全删除
- 区域检查
- 原子化持久化
- 基于排名的家园数量限制
- 别名感知的排名处理
当存在多个活跃排名时,OmniPanel 会使用最高的适用家园配额,而不是将配额相加。
默认家园限制
| Rank(排名) |
Homes(家园数) |
| Default(默认) |
2 |
| Member, Helper(成员,助手) |
3 |
| VIP, Moderator(VIP,管理员) |
4 |
| MVP, YouTuber, Builder, Admin(MVP,YouTuber,建筑师,管理员) |
5 |
| Hero, Developer, Manager(英雄,开发者,经理) |
6 |
| Champion, Legendary, Executive, CEO, Co-Owner, Owner(冠军,传奇,高管,CEO,联合创始人,所有者) |
7 |
现有的自定义限制仍受支持。
Random Teleport(随机传送)
/rtp 作为普通玩家命令仍然可用。
默认冷却时间:
60 seconds
现有的显式配置的冷却时间保持不变。
可用的目的地包括:
- Overworld(主世界)
- Nether(下界)
- End(末地)
- Close(关闭)
管理 RTP 控制包括:
- 冷却时间
- 倒计时
- 目标世界
- 搜索半径
- 尝试次数
- 世界边界处理
- 安全过滤器
- 受保护区域缓冲区
- No-RTP 区域
- 清除冷却时间
- 测试
仅在成功传送后开始计算冷却时间。
Personal Settings(个人设置)
玩家可以打开:
/settings
个人设置菜单与 OmniPanel 的管理设置分开。
可用选项包括:
- 接收 TPA 请求
- 自动接受 TPA
- 玩家可见性
- 碰撞检测
- 物品拾取
- 个人时间
- 个人天气
- 设置音效
- 敌对生物自然生成偏好
- 和平生物自然生成偏好
- 整理我的物品
- 我的坐标
- 清空我的背包
- 重置
个人时间和天气仅影响玩家的视野,不会改变世界的全局状态。
更安全的背包清空
清空背包需要受保护的确认机制。
该确认与以下因素绑定:
以下操作无法意外触发清空确认:
- 按 Escape
- 取消
- Shift 点击
- 双击
- 数字键
- 丢弃点击
- 底部背包栏点击
- Replay Mod 的确认
- 过期的确认
如果在确认前背包发生变化,旧的请求将失效。
个人生物生成偏好
玩家可以控制自己周围附近的敌对和平生物的自然生成。
该系统仅对选择退出的玩家本地生效,且可配置半径范围。
它不会:
- 更改全局游戏规则(gamerule)
- 删除现有生物
- 影响刷怪笼
- 影响生成蛋
- 影响繁殖
- 影响命令生成的生物
- 创建仅客户端可见的生物
在共享区域中,允许生成的附近玩家优先处理。
等级管理器
OmniPanel 包含深度集成的 LuckPerms 功能以进行等级管理。
功能包括:
- 主等级分配
- 附加等级
- 晋升
- 临时等级
- 永久等级
- 持续时间选择
- 等级显示
- TAB 列表同步
- 聊天同步
- 名称标签同步
- 等级别名
- 离线分配
- 序列化等级写入
- 失败回滚
正常的主等级分配会替换玩家之前的主等级。
附加等级通过 Multi Ranks 单独管理。
不相关的组和直接的玩家权限将被保留。
应用等级给所有人
授权工作人员可以批量应用选定的等级。
流程允许工作人员选择:
在应用之前,OmniPanel 会显示操作计数并要求确认。
受保护的和所有者级别的账户将被跳过。
权限:
omnipanel.access.ranks.apply-to-everyone
等级徽章
OmniPanel 包含一个生成的等级资源包贡献,其中包含自定义等级徽章。
当前等级徽章包括:
- Owner(所有者)
- Co-Owner(联合所有者)
- CEO(首席执行官)
- Executive(高管)
- Manager(经理)
- Admin(管理员)
- Builder(建造者)
- Developer(开发者)
- Moderator(版主)
- Helper(助手)
- MVP(最具价值玩家)
- VIP(贵宾)
- YouTuber(油管博主)
- Hero(英雄)
- Champion(冠军)
- Legendary(传奇)
- Member(成员)
- Default(默认)
还包括以下存在状态徽章:
徽章使用专用字体:
omnipanel:ranks
不会替换正常的 Minecraft 字体。
当未接受资源包时,仍可使用文本回退。
ResourcePackManager 集成
OmniPanel 将其生成的等级资产贡献到现有的 ResourcePackManager 工作流中。
ResourcePackManager 仍然负责:
OmniPanel 不会通过发送另一个独立资源包来与 ResourcePackManager 竞争。
如果使用徽章系统,请保持您正常的已组合 ResourcePackManager 配置。
名称与聊天样式
OmniPanel 包含可配置的名称和聊天样式。
当前样式集合包含:
13 页共 468 种可选样式。
包含的集合有:
- Smooth Signatures(平滑签名)
- Silk Motion(丝绸动态)
现有的配置文件 ID 和保存的玩家选择保持兼容。
支持的设置包括:
名称、聊天和 TAB 样式共享相同的渲染器。
Minecraft 团队颜色在需要的地方仍使用 Minecraft 原生的 16 色限制,而兼容的组件显示可以保留更丰富的 RGB 和渐变样式。
AFK 与存在状态
OmniPanel 包含一个与等级显示集成的 AFK 和存在状态系统。
AFK 保护抵抗被动移动,例如:
实际的玩家移动、/afk 命令或成功的传送将清除 AFK 状态。
仅相机移动不算作返回。
骑乘状态下进入 AFK 时会解除骑乘,且处于 AFK 状态的玩家不能被骑乘。
AFK 移动保护不提供伤害免疫。
套装
OmniPanel 包含基于 GUI 的套装系统。
套装功能包括:
- 创建和编辑
- 冷却时间
- 权限
- 预览
- 搜索
- 分类
- 安全的物品交付
- 溢出处理
- 交易失败时回滚
- 游戏时长奖励
领取套装会保留现有的背包内容,并在可能时合并兼容的物品堆叠。
部分填充的背包不会自动被视为已满。
游戏时长套装奖励
套装可以选择在游戏时长达到配置的阈值后奖励玩家。
通过“管理套装”或以下命令进行配置:
/kit playtime <kit> <minutes|off>
奖励按 UUID 和套装阈值存储。
冷却时间重置不会导致再次授予相同的游戏时长奖励。
Kit API 暴露了以下字段:
playtimeMinutes
捐赠者实用工具
VIP、MVP、Hero、Champion 和 Legendary 等级可以获得以下实用工具的默认访问权限:
/echest
/craft
/anvil
每个实用工具都有各自的:
现有的显式授予和拒绝仍然具有权威性。
/echest 使用 OmniPanel 现有的扩展末影箱存储,而不是创建第二个存储后端。
区域保护
OmniPanel 包含其原生的区域系统。
区域可以控制服务器行为,例如:
- 建造
- 破坏
- 交互
- PvP
- 水
- 熔岩
- 桶的使用
- 受保护边界
- 区域所有权
- 工作人员绕过
- 事件使用
可以使用 WorldEdit 和 FAWE 的选择来创建或调整 OmniPanel 区域的大小。
选择必须是完整的,并且属于已加载的世界。
更改尊重配置的体积限制。
失败的区域写入会自动回滚。
WorldEdit 选择区域集成
已授权的集成可以使用玩家的 WorldEdit 选择区域进行原生的 OmniPanel 区域操作。
仅凭 WorldEdit 选择区域本身无法提供 OmniPanel 的保护功能。
必须先将选择区域保存为 OmniPanel 区域。
服务器规则
OmniPanel 包含一个可编辑的规则工作室(Rules Studio)。
授权工作人员可以:
可配置选项包括:
即使规则列表为空,仍可对其进行编辑。
维护模式
维护控制可通过 OmniPanel 设置使用。
功能包括:
- 启用/禁用
- 自定义文本
- 占位符
- 转义换行符
- 后备控制
编辑维护文本不会自动启用维护模式。
监禁
OmniPanel 的监禁系统可以控制:
监禁配置的访问权限与执行监禁操作的权限是分开的。
允许使用的命令列表会在所有狱警之间同步,包括故意设置为空的列表。
监禁通知会保留记录的狱警身份和惩罚时长。
监控与通知
授权工作人员可以使用现有的监控服务来监视选定玩家的活动并接收通知。
监控访问权限和通知访问权限分别由权限控制。
管理员日志
管理员日志记录重要的管理和 moderation 活动。
记录可能包含:
- 执行者
- 目标
- 案件
- 操作
- 原因
- 持续时间
- 来源
- 结果
类别包括:
游戏模式变更的记录与提交的命令分开存储。
涉及凭证的命令不包括在命令日志中。
功能包括:
- 过滤
- 分页
- 刷新
- 详细记录
- 实时惩罚警报
- 选定命令追踪
- 游戏模式追踪
禁用记录功能会保留现有记录,并且不会禁用安全执行。
管理员命令审批
个别命令可选择性地需要管理员审批。
管理员可以:
批准仅允许在同一会话和世界条件下对完全相同的命令重试一次。
批准不会:
- 以控制台身份运行命令
- 授予缺失的权限
- 绕过等级检查
- 绕过世界限制
- 绕过参数验证
请求过期后不可重用,且不能用于更改后的参数。
命令中心
命令中心提供注册服务器命令的集中视图。
功能包括:
- 命令浏览
- 搜索
- 别名
- 插件/提供者分组
- 描述
- 用法
- 权限
- 等级访问
- 状态
- 活动/历史
组操作包括:
- 全部启用
- 全部禁用
- 全部显示
- 全部隐藏
- 重置组规则
公共游戏玩法和恢复命令受到保护,免受不恰当的命令中心限制。
Java 版与基岩版支持
OmniPanel 支持混合 Java 版和基岩版环境。
支持的集成包括:
功能包括:
- 感知平台的玩家处理
- 基岩版惩罚支持
- 真实的在线 UUID 处理
- 感知基岩版的认证
- 基岩版账户恢复
- 保留前缀的身份标识
基岩版玩家保留其实际的在线 UUID,而不是获得虚构的离线 UUID。
认证与恢复
OmniPanel 包含账户认证和可信控制台恢复功能。
恢复命令:
forcelogin <player-or-known-UUID> [--reset]
forceregister <player-name-or-known-UUID> [--replace]
恢复支持:
- 在线玩家
- 已知的离线账户
- UUID 查找
- 基岩版前缀处理
- 离线账户创建
- 凭证替换
- 解锁前的保存行为
- 恢复会话消耗
- 重新注册流程
现有凭证在被覆盖之前需要 --replace。
凭证在会话解锁前会被保存。
仅存储加盐密码哈希值。
根据服务器配置,恢复功能仅限于受信任的控制台使用。
DiscordSRV 集成
OmniPanel 与服务器的现有 DiscordSRV 安装集成。
它不会创建另一个独立的 Discord 机器人系统。
功能包括:
- 多个公会/频道目标
- 公共路由
- 私有审计路由
- 工作人员路由
- 惩罚路由
- 权限检查
- 队列处理
- 投递错误日志
- 路由测试
- 目标去重
私有路由不会静默回退到公共 Discord 频道。
Discord 账户链接
支持的命令包括:
/linkdiscord
/unlinkdiscord
以及作为别名可用的:
discordlink
在支持的情况下,OmniPanel 使用 DiscordSRV 现有的 AccountLinkManager。
这使得 OmniPanel 可以复用 DiscordSRV 的功能,用于:
- 链接代码
- 链接状态
- 取消链接
- 反向查找
- 角色同步身份
当原生 DiscordSRV 链接可用时,OmniPanel 不会创建第二个竞争的链接代码数据库。
欢迎消息
OmniPanel 支持基于位置的 configurable 欢迎消息。
功能包括:
- 基于世界的欢迎
- 基于区域的欢迎
- 丰富颜色
- 样式化玩家名称
- PlaceholderAPI 替换
- 冷却时间
- 感知认证的延迟消息
- 组件动作栏
对于同一目的地,可以抑制重复的问候,但不会阻止其他区域或世界显示各自的欢迎消息。
事件系统
OmniPanel 保留其现有的事件框架,用于配置好的服务器事件。
该系统支持:
- 事件模板
- 位置
- 计时器
- 奖励
- 角色
- 开关
- 工作人员控制
- 确认流程
- 事件状态
- 安全关机处理
现有的事件模板和配置的事件数据仍受支持。
公共命令
以下游戏玩法命令默认保持公开,不需要面板访问权限:
/rtp
/home
/homes
/sethome
/delhome
/unsethome
/tpa
/tpahere
/tpaccept
/tpdeny
/tpcancel
/tpauto
/settings
正常游戏限制(如冷却时间、家园数量上限、保护规则和服务器配置)仍然生效。
开发者 API
OmniPanel 提供了一个公开的开发者 API,供需要与 OmniPanel 集成但不访问内部实现类的插件使用。
当前 API 版本
开发者 API: 4.8.0
权限服务 API: 5.0.0
该 API 扩展了 OmniPanel 的现有系统,而非创建重复的后端。
插件可以与以下现有系统配合使用:
- 惩罚后端
- 等级后端
- 区域后端
- Kit 后端
- 权限系统
- 玩家操作
- 在线状态系统
- 事件系统
这些系统由 OmniPanel 自身使用。
可用的 API 接口
OmniPanel 提供了多种集成接口。
OmniPanelService
用于基于服务的插件集成。
功能包括:
- 插件注册
- 就绪检查
- 能力发现
- 状态
- 心跳
- 断开连接处理程序
- 菜单访问
- 扩展注册
OmniPanelDeveloperAPI
提供经过身份验证/密钥认证的集成辅助工具。
OmniPanelAPI
提供对现有运行时功能的访问,包括惩罚集成。
OmniPanelRuntimeAPI
提供面向运行时的集成方法。
区域 API
可用或已扩展的区域辅助方法包括:
getWorldEditSelectionSnapshot(key, player)
createNativeRegionFromSelection(key, player, name, lobby)
resizeNativeRegionFromSelection(key, player, regionId)
deleteNativeRegion(key, player, regionId)
getNativeRegionIds(key, world)
checkBuildAccess(key, player, location, action)
getPlayerNameStyleSnapshot(key, player)
refreshPlayerNameStyle(key, player)
该服务还提供:
checkBuildAccessAsync(...)
建造权限查询使用与实际游戏玩法相同的规则,包括:
- 区域
- 世界
- 绕过权限
- 监狱限制
- 放置检查
- 破坏检查
- 交互检查
异步建造权限检查会捕获位置并在服务器线程上调度权威检查。
扩展 API
插件可以集成到现有的 OmniPanel 系统中,包括:
- 面板按钮
- 面板部分
- 回调处理程序
- 命名空间注册清理
- 注册结果详情
- 自定义玩家操作
- 区域提供者
- 区域标志
- 外部区域详情
- 支持的区域变更
- 等级权限贡献
- 等级层级快照
- 等级权重快照
- 玩家权限快照
- 权限刷新请求
- 等级同步诊断
- AutoMod 诊断
- 身份验证诊断
- 玩家在线状态
- AFK 状态
- LIVE 状态
- Kit 就绪状态
- Kit 元数据
- Kit 预览
- Kit 领取
- 事件就绪状态
- 事件模板
- 活动事件 ID
- 占位符解析
- 权限查询
在需要兼容性的地方,现有的 API 签名仍然可用。
惩罚 API
插件可以打开 OmniPanel 的惩罚界面:
OmniPanelAPI.openPunishmentTarget(
staff,
"Target",
"tempipban"
);
打开界面后,直到完成正常的 OmniPanel 确认流程,惩罚才会生效。
插件还可以通过权威的惩罚后端直接提交:
OmniPanelAPI.submitPunishment(
staff,
"Target",
"tempipban",
"1d",
"Verified network ban evasion; staff reviewed evidence",
"my_plugin"
).thenAccept(result -> {
// 检查结果状态和权威应用值。
});
可以使用以下代码读取授权历史记录:
var records =
OmniPanelAPI.getPunishmentHistory(
staff,
"Target",
20
);
可能的提交状态包括:
APPLIED
REJECTED
DENIED
INVALID_INPUT
INVALID_DURATION
OWNER_APPROVAL_REQUIRED
UNAVAILABLE
FAILED
返回的 applied 值是权威的。
Future 完成并不自动意味着惩罚成功。
惩罚 API 安全性
直接提交惩罚故意不显示 OmniPanel 的正常确认界面。
调用插件负责自己的确认和证据审查流程。
OmniPanel 仍强制执行:
- 员工授权
- 玩家会话有效性
- 所有者保护
- 持续时间限制
- 命令审批策略
- 队列有效性
取消、过期或已完成排队的工作将被跳过。
惩罚历史记录有界,且不暴露存储的 IP 地址。
带密钥的 API 方法会验证 API 密钥以及执行玩家的身份验证。
API 安全性
OmniPanel API 密钥不会:
- 授予员工权限
- 冒充控制台
- 绕过操作权限
- 绕过区域权限
区域变更仍要求执行玩家具有相应的权限。
服务器状态和 UI 操作必须遵循文档中规定的服务器线程要求。
文档中说明的快照是不可变的。
无效或禁用的密钥会在不授予访问权限的情况下失败。
服务 API 在适当的地方使用兼容性友好的默认方法,以免不必要地破坏现有实现。
PlaceholderAPI
OmniPanel 支持 PlaceholderAPI 集成。
可用的占位符取决于已安装的版本和启用的系统。
典型的 OmniPanel 信息包括:
- 等级
- 前缀
- 后缀
- 在线状态
- 员工状态
- Ping 延迟
- 世界
- 家园
- 警告
- 静音状态
- 冻结状态
- 游戏时长
这使得 OmniPanel 信息可以被兼容的以下组件使用:
- TAB 插件
- 计分板
- 聊天系统
- 全息图
- 其他 PlaceholderAPI 消费者
权限
OmniPanel 是基于权限驱动的。
示例如下:
omnipanel.use
omnipanel.panel
omnipanel.playerbrowser
omnipanel.playeractions
omnipanel.punish
omnipanel.warn
omnipanel.mute
omnipanel.ban
omnipanel.events
omnipanel.kits
omnipanel.regions
omnipanel.ranks
omnipanel.staff
omnipanel.stafftp
omnipanel.admin
omnipanel.owner
功能级别的权限也广泛用于面板可见性与访问控制中。
明确的 LuckPerms 授权与拒绝具有最高优先级。
可选集成
OmniPanel 可以集成以下插件:
- LuckPerms
- PlaceholderAPI
- Vault
- WorldEdit
- FAWE
- DiscordSRV
- Geyser
- Floodgate
- TAB
- Multiverse-Core
- ResourcePackManager
支持情况取决于所使用的功能以及服务器上安装的版本。
兼容性
OmniPanel 当前的构建系统面向现代 Minecraft 服务器软件。
当前构建覆盖范围包括:
- Paper 1.21.11 基础 API 编译
- Paper 26.2 配置档
- Paper 26.3 配置档
- 支持的 Spigot 回退路径
- Purpur 兼容的 Paper API 路径
在可用情况下使用原生 Paper Dialog 功能。
Spigot 未提供 Paper 的原生 Dialog API,因此在可能的情况下使用支持的回退界面。
生产环境字节码保持为:
Java release 21
Class version 65
构建过程在需要时会使用较新的 JDK 来读取较新的 Paper API。
请运行你所部署的 Minecraft 服务器软件所需的 Java 版本。
构建质量
当前的 OmniPanel 源代码已重构为可重复构建的流程,不再依赖构建后的二进制补丁。
生产环境的 JAR 包直接从源代码编译而成。
生产版本不捆绑以下内容:
- 测试夹具
- Mock 类
- 恢复探针
- 服务器 API 依赖项
当前 18.9.114 版本的验证包括:
- 0 个 Java 编译错误
- 368 个 JUnit 测试通过
- 26 个辅助回归检查通过
- 465 个生产类通过 JVM 验证
- 干净的提取源代码重新构建出字节完全相同的 JAR 包
- Paper 26.2 定向回归套件通过
- Paper 26.3 定向回归套件通过
- 共享 Spigot API 链接检查通过
- 描述符和 YAML 验证
- CRC 验证
- JAR 完整性检查
- 重复类/资源检查
- 测试/存根泄漏检查
这些检查不能替代真实的实时服务器测试。
资源包、Discord 推送、Java/基岩版行为、AI 响应、插件组合、物品栏和游戏内集成仍应在实际使用的服务器配置上进行验证。
安装
- 下载 OmniPanel。
- 将 JAR 文件放入服务器的
plugins 文件夹中。
- 安装你的服务器所使用的所有可选集成插件。
- 启动或完全重启服务器。
- 配置管理员权限。
- 打开:
/panel
更新 OmniPanel 时请勿使用热重载。
在安装重大更新之前,请备份现有的:
许可证与所有权
Copyright © 2026 Kingez341yt. All rights reserved.
OmniPanel 是专有软件。原始的 OmniPanel 源代码、编译构建、文档及原始项目资产均归属于 Kingez341yt。第三方库、集成及其他材料保留其各自的版权和许可证。
使 OmniPanel 可供查看或下载本身并不授予复制、修改、重新品牌化、再分发、转售或发布其专有源代码衍生版本的许可。
任何此类许可必须由 Kingez341yt 以书面形式或在单独的附带许可证中明确授予。
服务器运营商应遵循其官方 OmniPanel 发行版提供的条款。
移除或更改版权声明不会转移原始代码的所有权。
下次更新:全项目严格许可
计划在未来的 OmniPanel 更新中引入严格的、全项目范围的许可和归属覆盖,包括:
- 一个专用的、版本控制的
LICENSE 文件,包含清晰的专有条款。
- 在每一个原始 Java 源文件(
.java)中保持一致的 Copyright © 2026 Kingez341yt 和许可证声明。
- 在适用的项目元数据、构建文件、文档和原始资源中体现 Kingez341yt 的所有权/归属。
- 自动化源代码检查,在构建/发布前标记缺失或修改的许可证头部。
- 发布完整性检查,例如已发布的校验和或签名制品(如已实施)。
- 保留所有第三方代码和依赖项所需的 notices 和许可证。
开发者与再分发通知
未经授权修改、移除归属、复制或再分发可能违反适用的许可证。
许可证头部检查和发布验证可以帮助在检查相关文件时识别变更。
ChatGPT 不会自动监控私有代码库或检测在其他地方进行的编辑。
许可证更新状态
状态:计划在下一次更新中实施。
目前,README 尚未实现全源码头部的自动化检查。
一旦实施,这些检查将通过实际的源代码检查和发布验证来帮助识别缺失的归属通知和修改。
官方项目所有者: Kingez341yt
版权: © 2026 Kingez341yt
许可证类型: 专有 — 保留所有权利
即将推出的更新: 严格的源代码许可与项目归属
适用场景
OmniPanel 可用于:
- 生存服务器
- SMP 服务器
- 社区服务器
- 创作者服务器
- 活动服务器
- 角色扮演服务器
- 私人社区
- 管理员密集的服务器
- 成长中的网络集群
OmniPanel
OmniPanel 基于一个理念构建:
服务器管理应该像一个连贯的系统,而不是一堆互不相关的插件。
审核、等级、玩家工具、权限、家园、套装、区域、管理员工具、Discord 集成、认证和开发者集成都在同一个平台上协同工作,同时保持权限控制和可扩展性。
如果你希望有一个地方来运行和管理现代 Minecraft 服务器的运营层面,那么 OmniPanel 就是为此而生的。
由 Kingez341yt 开发与拥有。
© 2026 Kingez341yt. All rights reserved.
OmniPanel
One panel. One connected system. Complete control over your Minecraft server.
Created and owned by Kingez341yt
Copyright © 2026 Kingez341yt. All rights reserved.
License: Proprietary — All Rights Reserved
Documented Build: 18.9.114
Developer API: 4.8.0
Permission Service API: 5.0.0
About OmniPanel
OmniPanel is an all-in-one administration, moderation, player-management, and server-utility plugin built for modern Minecraft servers.
Instead of stacking separate plugins for staff tools, punishments, ranks, homes, kits, regions, player inspection, maintenance, events, authentication, and server management, OmniPanel connects those systems through one central platform.
The plugin is designed around menus, dialogs, shared permission checks, and consistent workflows rather than forcing staff to remember dozens of commands.
Whether you're running an SMP, community server, creator server, private server, or larger network, OmniPanel gives your staff one place to manage the server.
Why OmniPanel?
A normal server can quickly end up running separate plugins for:
- Moderation
- Punishments
- Staff Mode
- Player inspection
- Ranks
- Homes
- Kits
- Regions
- Events
- Authentication
- Maintenance
- Discord integration
- Player utilities
- Administrative tools
That usually means separate permission systems, different interfaces, overlapping commands, duplicate data, and plugins that do not know about each other.
OmniPanel is built differently.
One panel.
One connected permission system.
One moderation workflow.
One set of player-management tools.
One API for other plugins to integrate with.
Main Panel
Everything starts with:
/panel
The panel provides access to OmniPanel's administrative systems through a permission-aware interface.
Features include:
- Section-based navigation
- Feature-level permissions
- Search
- Pagination
- Context-aware menus
- Player selection
- Confirmation screens
- Paper Dialog integration
- Permission-aware buttons
- Staff-only actions
- Public-player menus where appropriate
- Back and Close navigation
- Extension support for add-ons
Opening /panel does not automatically give access to everything inside it.
Every protected feature is still checked server-side.
Panel Visibility & Access
OmniPanel uses a centralized access system for protected panel features.
Administrators can grant access to:
- Entire sections
- Individual features
- Specific staff members
- Specific ranks
This makes it possible to give staff exactly what they need.
For example:
- Helpers can inspect players without editing inventories.
- Moderators can freeze, jail, teleport, and moderate players without receiving rank-management access.
- Builders can receive region and building controls without punishment permissions.
- Developers can receive diagnostics and technical tools.
- Owners can retain complete access.
The built-in Panel Visibility & Access editor allows authorized staff to:
- Select a player or rank
- Choose full or custom access
- Browse sections
- Enable or disable individual features
- Review changes before applying them
- Grant or revoke complete sections
LuckPerms integration remains authoritative where available.
Explicit permission grants, denials, contexts, and external LuckPerms changes are respected.
Player Browser
Browse players through OmniPanel without needing to type usernames manually.
Player information can include:
- Online status
- Platform
- Rank
- Last seen
- Current world
- Playtime
- Homes
- Punishment history
- Staff notes
- Presence state
Player Actions provide access to additional tools depending on staff permissions.
Player Actions
Player Actions are organized into categories such as:
- Care & Movement
- Moderation & Records
- Utilities
- Advanced
- Additional Player Tools
Available actions depend on the staff member's permissions.
Integrated tools include:
- Teleportation
- Healing
- Inventory inspection
- Ender Storage inspection
- Punishment history
- Staff notes
- Freeze
- Jail
- Moderation tools
- Utility actions
Target actions remain bound to the selected player rather than silently falling back to the staff member.
Inventory Inspection
OmniPanel includes shared inventory-inspection sessions for staff.
Example:
/invsee inventory <player>
Viewing and editing are separate permissions.
The inventory system supports:
- Read-only inspection
- Authorized editing
- Storage slots
- Armour
- Offhand
- Concurrent-session protection
- Inventory transaction guards
- Offline player inspection
- Offline editing backups
- Login protection while an offline edit is active
Read-only sessions cannot write changes back to the target player.
Real player items are treated as items, not as GUI buttons.
Expanded Ender Storage
OmniPanel includes an expanded Ender Storage system backed by its existing storage database.
Features include:
- 54 usable chest slots
- Staff inspection
- Personal
/echest access where permitted
- SQLite persistence
- Backups
- Legacy-data imports
- Vanilla synchronization
- Physical opening and closing sounds
- Lid animation
- Shared-viewer handling
- Corruption safeguards
Invalid stored item data fails closed instead of silently replacing stored items with empty slots.
Punishment System
OmniPanel includes a full punishment workflow for staff moderation.
Supported actions include:
- Warnings
- Temporary warnings
- Mutes
- Temporary mutes
- Bans
- Temporary bans
- IP bans
- Temporary IP bans
- Kicks
- Freeze
- Jail
- Reversals
- Staff notes
- Punishment records
Temporary punishments require valid finite durations and respect configured limits.
Punishments use the authoritative backend so GUI actions, API submissions, records, and enforcement stay connected.
Punishment Records
Punishment history can include:
- Staff actor
- Target
- Case
- Source
- Action
- Reason
- Duration
- Timestamp
- Result
- Available evidence
History uses compact summaries with full details available through the existing record interface.
Warnings, kicks, reversals, and expired temporary punishments are not incorrectly shown as permanent active sanctions.
Punishment Presets
OmniPanel includes searchable punishment presets for reviewed moderation situations such as:
- Fraud
- Phishing
- Malicious links
- Evasion
- Bot raids
- Exploits
- Harassment
- Spam
Custom server presets remain supported and remain authoritative.
Normal Minecraft behaviour such as legitimate trading, giveaways, or regular PvP is not automatically treated as a violation.
Duration Builder
Temporary punishments support normal duration units including:
- Seconds
- Minutes
- Hours
- Days
- Weeks
- Months
- Years
Duration validation is handled before temporary punishments are applied.
AutoMod
OmniPanel includes built-in chat moderation and evidence handling.
Features include:
- Blocked-word detection
- Strict-word lists
- Word-boundary matching
- Current-message evidence
- Spam detection
- Moderation alerts
- Configurable confidence requirements
- Saved evidence
- Staff review flows
- Atomic word-list updates
Commands include:
/automod words add
/automod words remove
/automod words list
And:
/automod strictwords add
/automod strictwords remove
/automod strictwords list
Blocked-word checks use the actual current message rather than stale content from previous messages.
AI Moderation Evidence
Where AI-assisted moderation is configured, OmniPanel treats AI output as evidence for review rather than automatic truth.
The moderation context accounts for normal Minecraft activity including:
- PvP
- Trading
- Economy activity
Automatic decisions require:
- A recognized category
- Evidence from the real message
- A verbatim matching quote
- Contextual support
- The configured confidence threshold
The default evidence confidence threshold is:
0.95
High-impact or uncertain cases remain review-oriented by default.
Evidence records can contain:
- Original message
- Matching quote
- SHA-256
- Capture time
- Source
- Model confidence where available
AI confidence is a safeguard, not proof.
Staff Mode
OmniPanel includes a built-in Staff Mode with safe inventory recovery.
Features include:
- Staff inventory backup
- Staff tools
- Vanish support
- Join/quit recovery
- Inventory restoration
- Flight-state restoration
- Collision restoration
- Pickup-state restoration
- Protection-state restoration
- Recovery after disconnect or shutdown
- Persistent tool identifiers
- Protected tool movement
- Staff Mode title
- On-duty action bar
Entering Staff Mode fails safely if the staff inventory cannot be backed up.
Staff Tools
Available administrative tools include:
- Sentinel Blade
- Excavator Pickaxe
- Timber Axe
- Justice Hammer
Tools can be granted individually instead of requiring access to every administrative tool.
Punishment-related tools still require the corresponding punishment permissions.
Issuing a staff tool does not overwrite occupied inventory slots.
Staff Chat
Staff Chat uses the same access system for:
- Toggling
- Sending
- Receiving
- Visibility
- Execution
Default and Member players do not receive Staff Chat automatically.
Staff messages are routed before normal public chat auditing or Discord forwarding.
If access is revoked before a pending Staff Chat message is sent, the message is cancelled instead of leaking into public chat.
Emergency Staff Teleport
OmniPanel includes:
/stafftp [message]
This allows authorized staff to send a private emergency teleport invitation.
Staff can respond using:
- Clickable Accept
- Clickable Deny
/stafftp accept
/stafftp deny
/tpaccept
/tpdeny
Emergency staff teleport requests always require explicit acceptance, even if normal TPA auto-accept is enabled.
Requests are session-bound, expire properly, and cannot be reused after reconnecting.
Public Teleport Requests
Normal player teleport commands remain public:
/tpa
/tpahere
/tpaccept
/tpdeny
/tpcancel
/tpauto
Players can configure:
- Whether they receive teleport requests
- Whether normal requests auto-accept
Emergency staff requests remain separate from normal auto-accept behaviour.
Homes
OmniPanel includes a public homes system.
Commands include:
/home
/homes
/sethome
/delhome
/unsethome
Features include:
- Named homes
- Teleportation
- GUI access
- Safe deletion
- Region checks
- Atomic persistence
- Rank-based home limits
- Alias-aware rank handling
When multiple active ranks are present, OmniPanel uses the highest applicable home allowance instead of adding allowances together.
Default Home Limits
| Rank |
Homes |
| Default |
2 |
| Member, Helper |
3 |
| VIP, Moderator |
4 |
| MVP, YouTuber, Builder, Admin |
5 |
| Hero, Developer, Manager |
6 |
| Champion, Legendary, Executive, CEO, Co-Owner, Owner |
7 |
Existing custom limits remain supported.
Random Teleport
/rtp remains available as a normal player command.
Default cooldown:
60 seconds
Existing explicitly configured cooldowns are preserved.
Available destinations include:
- Overworld
- Nether
- End
- Close
Administrative RTP controls include:
- Cooldown
- Countdown
- Target worlds
- Search radius
- Attempts
- World-border handling
- Safety filters
- Protected-region buffer
- No-RTP zones
- Cooldown clearing
- Testing
The cooldown starts only after a successful teleport.
Personal Settings
Players can open:
/settings
The personal settings menu is separate from OmniPanel's administrative settings.
Available options include:
- Receive TPA requests
- TPA auto-accept
- Player visibility
- Collision
- Item pickup
- Personal time
- Personal weather
- Settings sounds
- Hostile natural-spawn preference
- Peaceful natural-spawn preference
- Stack My Items
- My Coordinates
- Clear My Inventory
- Reset
Personal time and weather only affect the player's view and do not alter the world's global state.
Safer Inventory Clearing
Inventory clearing requires a protected confirmation.
The confirmation is tied to:
- Player
- Target
- Inventory state
- Session
The following cannot accidentally confirm a clear:
- Escape
- Cancel
- Shift-click
- Double-click
- Number keys
- Drop clicks
- Bottom-inventory clicks
- Replayed confirmations
- Expired confirmations
If the inventory changes before confirmation, the old request becomes invalid.
Personal Mob-Spawn Preferences
Players can control nearby natural hostile and peaceful mob spawning around themselves.
The system is local to the opted-out player and configurable by radius.
It does not:
- Change a global gamerule
- Delete existing mobs
- Affect spawners
- Affect spawn eggs
- Affect breeding
- Affect command-spawned mobs
- Create separate client-only mobs
Nearby players who allow spawning take priority in shared areas.
Rank Manager
OmniPanel includes deep LuckPerms integration for rank management.
Features include:
- Main-rank assignment
- Additional ranks
- Promotions
- Temporary ranks
- Permanent ranks
- Duration selection
- Rank display
- TAB synchronization
- Chat synchronization
- Name-tag synchronization
- Rank aliases
- Offline assignments
- Serialized rank writes
- Failure rollback
Normal rank assignment replaces the player's previous main rank.
Additional ranks are managed separately through Multi Ranks.
Unrelated groups and direct player permissions are preserved.
Apply Rank to Everyone
Authorized staff can bulk-apply a selected rank.
The flow allows staff to choose:
- Online players only
- All known players
Before applying, OmniPanel displays the operation count and requires confirmation.
Protected and owner-level accounts are skipped.
Permission:
omnipanel.access.ranks.apply-to-everyone
Rank Badges
OmniPanel includes a generated rank-resource-pack contribution containing custom rank badges.
Current rank badges include:
- Owner
- Co-Owner
- CEO
- Executive
- Manager
- Admin
- Builder
- Developer
- Moderator
- Helper
- MVP
- VIP
- YouTuber
- Hero
- Champion
- Legendary
- Member
- Default
Presence badges are also included for:
The badges use the dedicated font:
omnipanel:ranks
The normal Minecraft font is not replaced.
Text fallback remains available when the resource pack is not accepted.
ResourcePackManager Integration
OmniPanel contributes its generated rank assets to the existing ResourcePackManager workflow.
ResourcePackManager remains responsible for:
- Combining packs
- Hosting
- Prompting players
- Delivering the final pack
OmniPanel does not compete with ResourcePackManager by sending another standalone pack.
If using the badge system, keep your normal combined ResourcePackManager setup configured.
Name & Chat Styles
OmniPanel includes configurable name and chat styling.
The current style collection contains:
468 selectable styles across 13 pages.
Included collections include:
- Smooth Signatures
- Silk Motion
Existing profile IDs and saved player selections remain compatible.
Supported settings include:
- Animation enablement
- Speed
- Frame timing
Name, chat, and TAB styling share the same renderer.
Minecraft team colours still use Minecraft's native 16-colour limit where required, while compatible component displays can retain richer RGB and gradient styling.
AFK & Presence
OmniPanel includes an AFK and presence system integrated with rank display.
AFK protection resists passive movement such as:
- Water
- Wind charges
- Knockback
- Ordinary velocity
- Player collision
- Mob collision
AFK is cleared by actual player movement, /afk, or successful teleportation.
Camera movement alone does not count as returning.
Mounted players are dismounted when entering AFK, and AFK players cannot be mounted.
AFK movement protection does not provide damage immunity.
Kits
OmniPanel includes a GUI-driven kit system.
Kit features include:
- Creation and editing
- Cooldowns
- Permissions
- Preview
- Search
- Categories
- Safe item delivery
- Overflow handling
- Rollback on failed transactions
- Playtime rewards
Kit claims preserve existing inventory contents and merge compatible stacks where possible.
A partially filled inventory is not automatically treated as full.
Playtime Kit Rewards
Kits can optionally reward players after reaching configured playtime thresholds.
Configure through Manage Kit or:
/kit playtime <kit> <minutes|off>
Rewards are stored per UUID and kit threshold.
Cooldown resets do not cause the same playtime reward to be granted again.
The Kit API exposes:
playtimeMinutes
Donor Utilities
VIP, MVP, Hero, Champion, and Legendary can receive default access to utilities such as:
/echest
/craft
/anvil
Each utility has its own:
- Permission
- Configuration switch
Existing explicit grants and denials remain authoritative.
/echest uses OmniPanel's existing expanded Ender Storage rather than creating a second storage backend.
Region Protection
OmniPanel includes its own native region system.
Regions can control server behaviour such as:
- Building
- Breaking
- Interaction
- PvP
- Water
- Lava
- Buckets
- Protected boundaries
- Region ownership
- Staff bypass
- Event usage
WorldEdit and FAWE selections can be used to create or resize OmniPanel regions.
Selections must be complete and belong to loaded worlds.
Changes respect configured volume limits.
Failed region writes roll back automatically.
WorldEdit Selection Integration
Authorized integrations can use a player's WorldEdit selection for native OmniPanel region operations.
A WorldEdit selection by itself does not provide OmniPanel protection.
The selection must first be saved as an OmniPanel region.
Server Rules
OmniPanel includes an editable Rules Studio.
Authorized staff can:
- Add rules
- Edit rules
- Delete rules
- Reorder rules
Configurable options include:
- Title
- Introduction
- Page size
An empty rules list can still be edited.
Maintenance Mode
Maintenance controls are available through OmniPanel Settings.
Features include:
- Enable/disable
- Custom text
- Placeholders
- Escaped newlines
- Fallback controls
Editing maintenance text does not automatically enable maintenance mode.
Jail
OmniPanel's jail system can control:
- Commands
- Chat
- Building
- Interaction
- Items
- PvP
Jail configuration access is separate from the ability to jail a player.
Allowed-command lists are synchronized across jail guards, including intentionally empty lists.
Jail notices retain the recorded jailer and punishment duration.
Watch & Notify
Authorized staff can use the existing watch service to monitor selected player activity and receive notifications.
Watch access and notification access remain separately permission-controlled.
Owner Log
Owner Log records important administrative and moderation activity.
Records can include:
- Actor
- Target
- Case
- Action
- Reason
- Duration
- Source
- Result
Categories include:
- Punishments
- Commands
- Game-mode changes
Game-mode changes are recorded separately from submitted commands.
Credential-related commands are excluded from command logging.
Features include:
- Filtering
- Pagination
- Refresh
- Detailed records
- Live punishment alerts
- Selected-command tracking
- Game-mode tracking
Disabling recording keeps existing records and does not disable security enforcement.
Owner Command Approval
Individual commands can optionally require owner approval.
Owners can:
Approval only allows one retry of the exact command under the same session and world conditions.
Approval does not:
- Run the command as console
- Grant missing permissions
- Bypass rank checks
- Bypass world restrictions
- Bypass argument validation
Requests expire and cannot be reused with changed arguments.
Command Hub
Command Hub provides a central view of registered server commands.
Features include:
- Command browsing
- Search
- Aliases
- Plugin/provider grouping
- Descriptions
- Usage
- Permissions
- Rank access
- State
- Activity/history
Group operations include:
- Enable All
- Disable All
- Show All
- Hide All
- Reset Group Rules
Public gameplay and recovery commands are protected from inappropriate Command Hub restrictions.
Java & Bedrock Support
OmniPanel supports mixed Java and Bedrock environments.
Supported integrations include:
Features include:
- Platform-aware player handling
- Bedrock punishment support
- Real online UUID handling
- Bedrock-aware authentication
- Bedrock account recovery
- Prefix-preserving identities
Bedrock players keep their actual online UUID rather than receiving an invented offline UUID.
Authentication & Recovery
OmniPanel includes account authentication and trusted-console recovery.
Recovery commands:
forcelogin <player-or-known-UUID> [--reset]
forceregister <player-name-or-known-UUID> [--replace]
Recovery supports:
- Online players
- Known offline accounts
- UUID lookup
- Bedrock prefix handling
- Offline account creation
- Credential replacement
- Save-before-unlock behaviour
- Recovery-session consumption
- Re-registration flows
Existing credentials require --replace before they are overwritten.
Credentials are saved before the session unlocks.
Only salted password hashes are stored.
Recovery remains restricted to trusted console usage according to server configuration.
DiscordSRV Integration
OmniPanel integrates with the server's existing DiscordSRV installation.
It does not create another independent Discord bot system.
Features include:
- Multiple guild/channel destinations
- Public routes
- Private audit routes
- Staff routes
- Punishment routes
- Permission checking
- Queue handling
- Delivery-error logging
- Route testing
- Destination deduplication
Private routes do not silently fall back to public Discord channels.
Discord Account Linking
Supported commands include:
/linkdiscord
/unlinkdiscord
With:
discordlink
Remaining available as an alias.
Where supported, OmniPanel uses DiscordSRV's existing AccountLinkManager.
This allows OmniPanel to reuse DiscordSRV for:
- Link codes
- Link status
- Unlinking
- Reverse lookup
- Role-sync identity
OmniPanel does not create a second competing link-code database when native DiscordSRV linking is available.
Welcome Messages
OmniPanel supports configurable welcome messages based on location.
Features include:
- World-based welcomes
- Region-based welcomes
- Rich colours
- Styled player names
- PlaceholderAPI replacements
- Cooldowns
- Authentication-aware delayed messages
- Component action bars
Repeated greetings can be suppressed for the same destination without preventing a different region or world from showing its own welcome.
Event System
OmniPanel retains its existing event framework for configured server events.
The system supports:
- Event templates
- Locations
- Timers
- Rewards
- Roles
- Toggles
- Staff controls
- Confirmation flows
- Event state
- Safe shutdown handling
Existing event templates and configured event data remain supported.
Public Commands
The following gameplay commands remain public by default and do not require panel access:
/rtp
/home
/homes
/sethome
/delhome
/unsethome
/tpa
/tpahere
/tpaccept
/tpdeny
/tpcancel
/tpauto
/settings
Normal gameplay restrictions such as cooldowns, home limits, protection rules, and server configuration still apply.
Developer API
OmniPanel includes a public developer API for plugins that need to integrate with OmniPanel without accessing internal implementation classes.
Current API Versions
Developer API: 4.8.0
Permission Service API: 5.0.0
The API extends OmniPanel's existing systems instead of creating duplicate backends.
An add-on can work with the same:
- Punishment backend
- Rank backend
- Region backend
- Kit backend
- Permission system
- Player Actions
- Presence system
- Event system
Used by OmniPanel itself.
Available API Surfaces
OmniPanel provides several integration surfaces.
OmniPanelService
Used for service-based add-on integration.
Capabilities include:
- Add-on registration
- Readiness checks
- Capability discovery
- Status
- Heartbeat
- Disconnect handlers
- Menu access
- Extension registration
OmniPanelDeveloperAPI
Provides authenticated/keyed integration helpers.
OmniPanelAPI
Provides access to existing runtime functionality including punishment integration.
OmniPanelRuntimeAPI
Provides runtime-facing integration methods.
Region API
Available or expanded region helpers include:
getWorldEditSelectionSnapshot(key, player)
createNativeRegionFromSelection(key, player, name, lobby)
resizeNativeRegionFromSelection(key, player, regionId)
deleteNativeRegion(key, player, regionId)
getNativeRegionIds(key, world)
checkBuildAccess(key, player, location, action)
getPlayerNameStyleSnapshot(key, player)
refreshPlayerNameStyle(key, player)
The service also provides:
checkBuildAccessAsync(...)
Build-access queries use the same rules as actual gameplay, including:
- Regions
- Worlds
- Bypass permissions
- Jail restrictions
- Place checks
- Break checks
- Interaction checks
Async build-access checks capture the location and schedule the authoritative check on the server thread.
Extension API
Add-ons can integrate with existing OmniPanel systems including:
- Panel buttons
- Panel sections
- Callback handlers
- Namespaced registration cleanup
- Registration-result details
- Custom Player Actions
- Region providers
- Region flags
- External region details
- Supported region mutations
- Rank permission contributions
- Rank hierarchy snapshots
- Rank weight snapshots
- Player permission snapshots
- Permission refresh requests
- Rank synchronization diagnostics
- AutoMod diagnostics
- Authentication diagnostics
- Player presence
- AFK state
- LIVE state
- Kit readiness
- Kit metadata
- Kit previews
- Kit claims
- Event readiness
- Event templates
- Active event IDs
- Placeholder resolution
- Permission queries
Existing API signatures remain available where compatibility is required.
Punishment API
Add-ons can open OmniPanel's punishment interface:
OmniPanelAPI.openPunishmentTarget(
staff,
"Target",
"tempipban"
);
Opening the interface does not apply the punishment until the normal OmniPanel confirmation is completed.
Add-ons can also submit directly through the authoritative punishment backend:
OmniPanelAPI.submitPunishment(
staff,
"Target",
"tempipban",
"1d",
"Verified network ban evasion; staff reviewed evidence",
"my_plugin"
).thenAccept(result -> {
// Inspect the result status and authoritative applied value.
});
Authorized history can be read with:
var records =
OmniPanelAPI.getPunishmentHistory(
staff,
"Target",
20
);
Possible submission statuses include:
APPLIED
REJECTED
DENIED
INVALID_INPUT
INVALID_DURATION
OWNER_APPROVAL_REQUIRED
UNAVAILABLE
FAILED
The returned applied value is authoritative.
A completed future does not automatically mean that a punishment succeeded.
Punishment API Safety
Direct punishment submission intentionally does not display OmniPanel's normal confirmation interface.
The calling add-on is responsible for its own confirmation and evidence-review process.
OmniPanel still enforces:
- Staff authorization
- Player session validity
- Owner protection
- Duration limits
- Command-approval policy
- Queue validity
Cancelled, expired, or already-completed queued work is skipped.
Punishment history is bounded and does not expose stored IP addresses.
Keyed API methods validate the API key as well as the acting player's authorization.
API Security
An OmniPanel API key does not:
- Grant staff permissions
- Impersonate console
- Bypass action permissions
- Bypass region permissions
Region mutations still require the acting player to have the appropriate permission.
Server-state and UI operations must follow the documented server-thread requirements.
Snapshots are immutable where documented.
Invalid or disabled keys fail without granting access.
The service API uses compatibility-friendly default methods where appropriate so existing implementations are not broken unnecessarily.
PlaceholderAPI
OmniPanel supports PlaceholderAPI integration.
Available placeholders depend on the installed version and enabled systems.
Typical OmniPanel information includes:
- Rank
- Prefix
- Suffix
- Online state
- Staff state
- Ping
- World
- Homes
- Warnings
- Mute state
- Freeze state
- Playtime
This allows OmniPanel information to be used by compatible:
- TAB plugins
- Scoreboards
- Chat systems
- Holograms
- Other PlaceholderAPI consumers
Permissions
OmniPanel is permission-driven.
Examples include:
omnipanel.use
omnipanel.panel
omnipanel.playerbrowser
omnipanel.playeractions
omnipanel.punish
omnipanel.warn
omnipanel.mute
omnipanel.ban
omnipanel.events
omnipanel.kits
omnipanel.regions
omnipanel.ranks
omnipanel.staff
omnipanel.stafftp
omnipanel.admin
omnipanel.owner
Feature-level permissions are also used throughout Panel Visibility & Access.
Explicit LuckPerms grants and denials remain authoritative.
Optional Integrations
OmniPanel can integrate with:
- LuckPerms
- PlaceholderAPI
- Vault
- WorldEdit
- FAWE
- DiscordSRV
- Geyser
- Floodgate
- TAB
- Multiverse-Core
- ResourcePackManager
Support depends on the feature being used and the versions installed on the server.
Compatibility
OmniPanel's current build system targets modern Minecraft server software.
Current build coverage includes:
- Paper 1.21.11 baseline API compilation
- Paper 26.2 profile
- Paper 26.3 profile
- Supported Spigot fallback paths
- Purpur-compatible Paper API paths
Native Paper Dialog functionality is used where available.
Spigot does not provide Paper's native Dialog API, so supported fallback interfaces are used where possible.
Production bytecode remains:
Java release 21
Class version 65
The build process uses a newer JDK where required to read newer Paper APIs.
Run the Java version required by the Minecraft server software you deploy.
Build Quality
The current OmniPanel source has been reconstructed into a repeatable build instead of relying on post-build binary patching.
The production JAR is compiled directly from source.
Production releases do not bundle:
- Test fixtures
- Mock classes
- Recovery probes
- Server API dependencies
Current 18.9.114 verification includes:
- 0 Java compilation errors
- 368 JUnit tests passing
- 26 helper regression checks passing
- 465 production classes passing JVM verification
- Clean extracted source rebuilding into a byte-identical JAR
- Paper 26.2 targeted regression suite passing
- Paper 26.3 targeted regression suite passing
- Shared Spigot API linkage checks passing
- Descriptor and YAML validation
- CRC validation
- JAR integrity checks
- Duplicate class/resource checks
- Test/stub leakage checks
These checks do not replace real live-server testing.
Resource packs, Discord delivery, Java/Bedrock behaviour, AI responses, plugin combinations, inventories, and gameplay integrations should still be verified on the actual server configuration being used.
Installation
- Download OmniPanel.
- Place the JAR inside your server's
plugins folder.
- Install any optional integrations your server uses.
- Start or fully restart the server.
- Configure staff permissions.
- Open:
/panel
Do not use hot reloads when updating OmniPanel.
Back up your existing:
- Configuration
- Player data
- Databases
- Resource-pack configuration
Before installing a major update.
License & Ownership
Copyright © 2026 Kingez341yt. All rights reserved.
OmniPanel is proprietary software. The original OmniPanel source code, compiled builds, documentation, and original project assets are attributed to Kingez341yt. Third-party libraries, integrations, and other material retain their own copyrights and licenses.
Making OmniPanel available to view or download does not by itself grant permission to copy, modify, rebrand, redistribute, resell, or publish derivative versions of its proprietary source code.
Any such permission must be expressly granted by Kingez341yt in writing or under a separate accompanying license.
Server operators should follow the terms provided with their official OmniPanel release.
Removing or changing a copyright notice does not transfer ownership of the original code.
Next Update: Strict Licensing Across the Project
A future OmniPanel update is planned to introduce strict, project-wide license and attribution coverage, including:
- A dedicated, version-controlled
LICENSE file with clear proprietary terms.
- A consistent Copyright © 2026 Kingez341yt and license notice in every original Java source file (
.java).
- Kingez341yt ownership/attribution in applicable project metadata, build files, documentation, and original resources where appropriate.
- Automated source checks that flag missing or modified license headers before builds/releases.
- Release integrity checks, such as published checksums or signed artifacts, where implemented.
- Preservation of required notices and licenses for all third-party code and dependencies.
Developer and Redistribution Notice
Unauthorized modification, removal of attribution, copying, or redistribution may breach the applicable license.
License-header checks and release verification can help identify changes when the relevant files are inspected.
ChatGPT does not automatically monitor private codebases or detect edits made elsewhere.
Licensing Update Status
Status: Planned for the next update.
The source-wide headers and automated checks are not yet implemented by this README.
Once implemented, these checks will help identify missing attribution notices and modifications through actual source inspection and release verification.
Official Project Owner: Kingez341yt
Copyright: © 2026 Kingez341yt
License Type: Proprietary — All Rights Reserved
Upcoming Update: Strict Source Licensing & Project Attribution
Built For
OmniPanel can be used on:
- Survival servers
- SMPs
- Community servers
- Creator servers
- Event servers
- Roleplay servers
- Private communities
- Staff-heavy servers
- Growing networks
OmniPanel
OmniPanel is built around one idea:
Server administration should feel like one connected system, not a pile of unrelated plugins.
Moderation, ranks, player tools, permissions, homes, kits, regions, staff utilities, Discord integration, authentication, and developer integrations all work through the same platform while remaining permission-controlled and extensible.
If you want one place to run and manage the operational side of a modern Minecraft server, that is what OmniPanel is built for.
Developed and owned by Kingez341yt.
© 2026 Kingez341yt. All rights reserved.
评论 0
登录后参与评分
还没有评论,来抢沙发吧