LPBSA
LuckPerms-Based Server Access 是一个 Velocity 插件,用于使用现有的 LuckPerms 权限和组来限制对后端服务器的访问。
LPBSA 不维护单独的白名单、UUID 列表或访问数据库。LuckPerms 作为唯一的事实来源(single source of truth)。
功能
- 限制单个 Velocity 后端服务器
- 基于权限和继承组的访问控制
ANY 和 ALL 需求模式
- 全局和每个服务器的绕过权限
- 支持 Velocity 强制主机和常规服务器转移
- 可配置的重定向、断开连接和转移拒绝行为
- 可复用的访问配置档案
- 完全可配置的 MiniMessage 消息
- 目标服务器 LuckPerms 上下文评估
- 原子化配置重载
- 权限更改在下次连接尝试时生效
- 无需单独的玩家的白名单或授权系统
要求
- Velocity
- Java 25
- 与 LuckPerms 5.5 兼容的 Velocity 安装
LPBSA 仅安装在 Velocity 上。Paper、Folia、Spigot 或其他后端服务器上不需要安装任何内容。
快速开始
限制名为 build 的 Velocity 后端:
servers:
build:
enabled: true
requirements:
mode: ANY
permissions:
- "lpbsa.server.build"
groups: []
为 Builder 组授予访问权限:
/lpv group builder permission set lpbsa.server.build true
现在,每当玩家被添加到 Builder 组时:
/lpv user Steve parent add builder
他们自动获得对 build 后端的访问权限。
没有单独的 LPBSA 授权命令。
强制主机
LPBSA 也保护通过 Velocity 强制主机选择的后端连接。
例如:
[forced-hosts]
"build.example.com" = ["build"]
通过该主机名连接的未授权玩家仍然会受到 build 访问规则的评估。
权限
| 权限 |
描述 |
lpbsa.server.<server> |
后端的默认访问权限 |
lpbsa.bypass |
绕过所有 LPBSA 限制 |
lpbsa.bypass.<server> |
绕过特定后端的限制 |
lpbsa.command.* |
管理 LPBSA 命令 |
还可以配置自定义访问权限节点。
命令
/lpbsa
/lpbsa help
/lpbsa reload
/lpbsa status
/lpbsa servers
/lpbsa check <player> <server>
/lpbsa test <server>
/lpbsa version
后端安全
LPBSA 保护经过 Velocity 的连接。
后端服务器端口不应直接暴露给玩家。如果代理和后端运行在同一台机器上,请将后端服务器绑定到环回地址,如 127.0.0.1。否则,请设置防火墙以阻止后端端口,使只有代理可以访问它们。
许可证
LPBSA 在 MIT 许可证下可用。
LPBSA 是一个独立项目,与 LuckPerms 无关或未得到其认可。
LPBSA
LuckPerms-Based Server Access is a Velocity plugin for restricting access to backend servers using existing LuckPerms permissions and groups.
LPBSA does not maintain a separate whitelist, UUID list, or access database. LuckPerms remains the single source of truth.
Features
- Restrict individual Velocity backend servers
- Permission-based and inherited-group access
ANY and ALL requirement modes
- Global and per-server bypass permissions
- Support for Velocity forced hosts and normal server transfers
- Configurable redirect, disconnect, and transfer-denial behavior
- Reusable access profiles
- Fully configurable MiniMessage messages
- Target-server LuckPerms context evaluation
- Atomic configuration reloads
- Permission changes apply on the next connection attempt
- No separate player whitelist or grant system
Requirements
- Velocity
- Java 25
- LuckPerms 5.5-compatible Velocity installation
LPBSA is installed only on Velocity. Nothing needs to be installed on Paper, Folia, Spigot, or other backend servers.
Quick Start
Restrict the Velocity backend named build:
servers:
build:
enabled: true
requirements:
mode: ANY
permissions:
- "lpbsa.server.build"
groups: []
Give your Builder group access:
/lpv group builder permission set lpbsa.server.build true
Now whenever a player is added to the Builder group:
/lpv user Steve parent add builder
they automatically gain access to the build backend.
There is no separate LPBSA grant command.
Forced Hosts
LPBSA also protects backend connections selected through Velocity forced hosts.
For example:
[forced-hosts]
"build.example.com" = ["build"]
An unauthorized player connecting through that hostname is still evaluated against the build access rule.
Permissions
| Permission |
Description |
lpbsa.server.<server> |
Default access permission for a backend |
lpbsa.bypass |
Bypass all LPBSA restrictions |
lpbsa.bypass.<server> |
Bypass a specific backend restriction |
lpbsa.command.* |
Administrative LPBSA commands |
Custom access permission nodes can also be configured.
Commands
/lpbsa
/lpbsa help
/lpbsa reload
/lpbsa status
/lpbsa servers
/lpbsa check <player> <server>
/lpbsa test <server>
/lpbsa version
Backend Security
LPBSA protects connections that pass through Velocity.
Backend server ports should not be exposed directly to players. If the proxy and backends run on the same machine, bind backend servers to loopback addresses such as 127.0.0.1. Otherwise, firewall backend ports so only the proxy can reach them.
License
LPBSA is available under the MIT License.
LPBSA is an independent project and is not affiliated with or endorsed by LuckPerms.
评论 0
登录后参与评分
还没有评论,来抢沙发吧