NimbusNetwork
NimbusNetwork 显示 Velocity + Paper 网络的实时网络状态、玩家数量、最大玩家数、回退目标和缓存健康状况。
NimbusNetworkCore 在每个 Velocity 代理上运行。
NimbusNetwork 在需要 PlaceholderAPI 占位符或后端白名单/最大玩家数报告的 Paper 服务器上运行。
- 同步模式可以是
LOCAL 或 MYSQL。
要求
- Java 21
- Velocity 3.5+
- Paper 1.21+
- 在使用占位符的每个 Paper 服务器上安装 PlaceholderAPI
安装
Velocity
- 将
NimbusNetworkCore-1.7.3.jar 放入每个 Velocity 代理的 plugins 文件夹中。
- 重启一次 Velocity。
- 编辑
plugins/nimbusnetworkcore/config.yml。
- 在
servers 下添加你要跟踪的所有后端服务器。
示例:
proxy-id: "proxy-1"
sync:
mode: "LOCAL"
servers:
lobby:
display-name: "Lobby"
whitelisted: false
use-paper-whitelist-report: true
max-players-override: -1
earth:
display-name: "smp"
whitelisted: false
use-paper-whitelist-report: true
max-players-override: -1
在每个 Velocity 代理上使用唯一的 proxy-id。
Paper
- 将
NimbusNetwork-1.7.3.jar 放入每个需要占位符的 Paper 服务器的 plugins 文件夹中。
- 确保已安装 PlaceholderAPI。
- 重启一次 Paper。
- 编辑
plugins/NimbusNetwork/config.yml。
- 将
backend-server-name 设置为 Velocity 中使用的确切服务器名称。
示例:
backend-server-name: "lobby"
backend-reporting:
enabled: true
report-whitelist: true
report-max-players: true
后端报告让 Velocity 知道 Paper 服务器是否处于白名单状态以及 Bukkit 使用的最大玩家数。这很有用,因为普通的 Velocity ping 无法可靠地暴露 Paper 白名单状态。
Paper 后端必须仅通过受信任的 Velocity 代理接受连接。Velocity 会在客户端消息转发之前消耗 NimbusNetwork 通道,但直接客户端访问后端会绕过该保护。
同步模式
Local
LOCAL 是默认模式,不需要数据库。
sync:
mode: "LOCAL"
用于单代理网络,或者当每个代理可以直接ping通相同后端服务器时使用。
MySQL
MYSQL 在多个 Velocity 代理之间共享快照。
sync:
mode: "MYSQL"
mysql:
host: "127.0.0.1"
port: 3306
database: "nimbus"
username: "user"
password: "password"
table-prefix: "nimbus_"
ssl-mode: "VERIFY_IDENTITY"
allow-public-key-retrieval: false
connect-timeout-millis: 5000
socket-timeout-millis: 5000
maximum-pool-size: 2
插件会自动创建和更新其快照表。
数据库工作在专用工作线程上运行,并使用有界的 HikariCP 连接池。MySQL 同步在连接失败后会自动重试。VERIFY_IDENTITY 是安全的默认值,并且需要针对配置的数据库主机名有效的证书。仅在无需 TLS 的可信本地连接时显式使用 DISABLED。
占位符
网络占位符:
%nimbus_total%
%nimbus_max%
%nimbus_network_max%
%nimbus_server_count%
%nimbus_proxy_count%
%nimbus_cache_age%
%nimbus_cache_stale%
服务器占位符:
%nimbus_players_lobby%
%nimbus_status_lobby%
%nimbus_max_lobby%
回退占位符:
%nimbus_fallback_main%
%nimbus_fallback_status_main%
将 lobby 和 main 替换为你配置的服务器或回退组名称。
计分板或全息图行示例:
Status: %nimbus_status_lobby%
Players: %nimbus_players_lobby%/%nimbus_max_lobby%
Network: %nimbus_total%/%nimbus_max%
命令
权限:
nimbusnetwork.admin
Velocity 命令:
/nimbusnetwork debug
/nimbusnetwork debug sync
/nimbusnetwork debug proxies
/nimbusnetwork debug server <server>
/nimbusnetwork debug fallback <group>
/nimbusnetwork refresh
Velocity 别名:
/nnc
Paper 命令:
/nimbusnetwork
/nimbusnetwork <server>
/nimbusnetwork debug <server>
/nimbusnetwork refresh
Paper 别名:
/nph
示例:
/nph lobby
/nph debug earth
两个命令均显示所选服务器的状态、玩家数量、最大玩家数、可达性、白名单状态和最后更新时间。
状态
状态按以下顺序解析:
OFFLINE 服务器未响应 Velocity ping
WHITELISTED Paper 后端报告或 Velocity 配置表明白名单已开启
FULL 玩家数量达到或超过最大玩家数
ONLINE 服务器可达且可用
如果 Paper 服务器没有在线玩家,来自该后端的插件消息将无法发送,直到有玩家加入。当没有最新的 Paper 白名单报告可用时,将使用 Velocity 配置中的 whitelisted 值作为回退。
NimbusNetwork
NimbusNetwork shows live network status, player counts, max players, fallback targets, and cache health for Velocity + Paper networks.
NimbusNetworkCore runs on each Velocity proxy.
NimbusNetwork runs on Paper servers that need PlaceholderAPI placeholders or backend whitelist/max-player reporting.
- Sync can be
LOCAL or MYSQL.
Requirements
- Java 21
- Velocity 3.5+
- Paper 1.21+
- PlaceholderAPI on each Paper server using the placeholders
Installation
Velocity
- Put
NimbusNetworkCore-1.7.3.jar in the plugins folder of every Velocity proxy.
- Restart Velocity once.
- Edit
plugins/nimbusnetworkcore/config.yml.
- Add every backend server you want tracked under
servers.
Example:
proxy-id: "proxy-1"
sync:
mode: "LOCAL"
servers:
lobby:
display-name: "Lobby"
whitelisted: false
use-paper-whitelist-report: true
max-players-override: -1
earth:
display-name: "smp"
whitelisted: false
use-paper-whitelist-report: true
max-players-override: -1
Use a unique proxy-id on each Velocity proxy.
Paper
- Put
NimbusNetwork-1.7.3.jar in the plugins folder of each Paper server that needs placeholders.
- Make sure PlaceholderAPI is installed.
- Restart Paper once.
- Edit
plugins/NimbusNetwork/config.yml.
- Set
backend-server-name to the exact server name used in Velocity.
Example:
backend-server-name: "lobby"
backend-reporting:
enabled: true
report-whitelist: true
report-max-players: true
Backend reporting lets Velocity know when the Paper server is whitelisted and what max player count Bukkit is using. This is useful because a normal Velocity ping does not reliably expose Paper whitelist state.
Paper backends must only accept connections through trusted Velocity proxies. Velocity consumes the NimbusNetwork channel
before client messages can be forwarded, but direct client access to a backend bypasses that protection.
Sync Modes
Local
LOCAL is the default mode and needs no database.
sync:
mode: "LOCAL"
Use this for a single-proxy network, or when each proxy can ping the same backend servers directly.
MySQL
MYSQL shares snapshots between multiple Velocity proxies.
sync:
mode: "MYSQL"
mysql:
host: "127.0.0.1"
port: 3306
database: "nimbus"
username: "user"
password: "password"
table-prefix: "nimbus_"
ssl-mode: "VERIFY_IDENTITY"
allow-public-key-retrieval: false
connect-timeout-millis: 5000
socket-timeout-millis: 5000
maximum-pool-size: 2
The plugin creates and updates its snapshot table automatically.
Database work runs on a dedicated worker and uses a bounded HikariCP connection pool. MySQL sync retries automatically
after connection failures. VERIFY_IDENTITY is the secure default and requires a
certificate valid for the configured database hostname. Use DISABLED explicitly only for a trusted local connection
without TLS.
Placeholders
Network placeholders:
%nimbus_total%
%nimbus_max%
%nimbus_network_max%
%nimbus_server_count%
%nimbus_proxy_count%
%nimbus_cache_age%
%nimbus_cache_stale%
Server placeholders:
%nimbus_players_lobby%
%nimbus_status_lobby%
%nimbus_max_lobby%
Fallback placeholders:
%nimbus_fallback_main%
%nimbus_fallback_status_main%
Replace lobby and main with your configured server or fallback group names.
Example scoreboard or hologram lines:
Status: %nimbus_status_lobby%
Players: %nimbus_players_lobby%/%nimbus_max_lobby%
Network: %nimbus_total%/%nimbus_max%
Commands
Permission:
nimbusnetwork.admin
Velocity commands:
/nimbusnetwork debug
/nimbusnetwork debug sync
/nimbusnetwork debug proxies
/nimbusnetwork debug server <server>
/nimbusnetwork debug fallback <group>
/nimbusnetwork refresh
Velocity alias:
/nnc
Paper commands:
/nimbusnetwork
/nimbusnetwork <server>
/nimbusnetwork debug <server>
/nimbusnetwork refresh
Paper alias:
/nph
Examples:
/nph lobby
/nph debug earth
Both commands show status, player count, max players, reachability, whitelist state, and last update age for the selected server.
Statuses
Statuses are resolved in this order:
OFFLINE server did not respond to Velocity ping
WHITELISTED Paper backend report or Velocity config says whitelist is on
FULL players are at or above max players
ONLINE server is reachable and available
If a Paper server has no players online, plugin messages from that backend cannot be sent until a player joins. The Velocity config value whitelisted is used as the fallback when no fresh Paper whitelist report is available.
评论 0
登录后参与评分
还没有评论,来抢沙发吧