将每位玩家发送到你的 BungeeCord 或 Velocity 代理上最佳的枢纽,并在没有可用枢纽时让他们在 limbo(等待服务器)中等待,而不是将其踢出。
FlowGate Lite 会持续检查你的枢纽状态,并将每位新玩家发送到负载最轻的健康枢纽。当所有枢纽都宕机或满员时,玩家会在备用服务器上等待,一旦有枢纽空闲,他们便会自动前往。该插件仅在代理端运行,同一个 jar 文件适用于 BungeeCord、Waterfall 和 Velocity。
功能
- 健康检查。 在后台 ping 每个枢纽,如果某个枢纽停止响应则跳过它,直到其恢复在线。
- 最少玩家枢纽。 新玩家会被分配到玩家数量最少的健康枢纽,支持可选的权重设置和玩家人数上限。
- Limbo(等待服务器)。 当没有可用枢纽时,玩家会在备用服务器上等待,并显示“Waiting”标题;一旦有枢纽就绪,玩家会自动离开。
- 踢出回退。 从后端被踢出的玩家会被转移到另一个枢纽或 limbo 服务器,而不是直接断开连接。
- 枢纽与服务器命令。 提供
/hub、/lobby 以及你自定义的命令,例如 /survival。
- 后端请求。 检查来自游戏服务器的
Connect 请求(例如来自 FlowGate Bridge),并根据你的白名单进行验证。
- MOTD。 服务器列表文本和悬停提示行,支持使用
& 代码和十六进制颜色。
- 状态查看。
/flowgate status 显示每个服务器的健康状况和路由计数。
支持的平台
- Velocity: 3.4 及更高版本,包括 4.x(已在 3.4.0、3.5.1、4.3.1 和 4.3.2 上测试)。
- BungeeCord 和 Waterfall: 最新构建版本(已在 BungeeCord 2111 和 Waterfall 615 上测试)。
- Java: 17 或更高版本。Velocity 4 需要 Java 25。
- 在 Velocity 上: restricted-server 检查仅适用于 BungeeCord,且后端
Connect 检查需要在 velocity.toml 中设置 bungee-plugin-message-channel = false。
安装
- 从下方链接之一下载
FlowGate-Lite-1.0.8.jar。
- 将其放入代理的
plugins 文件夹中,然后重启代理。
- 在
config.yml 中填写你的枢纽和 limbo 服务器名称,然后运行 /flowgate reload。
完整设置指南:安装教程。
隐私
每天一次,FlowGate Lite 会向 kori.my 报告又有一个服务器正在运行它:包含匿名 ID、插件版本、平台类型以及确认其为代理的信息。不包含任何 IP 地址、服务器名称或玩家数据。你可以在 config.yml 中将 metrics.enabled: false 来关闭此功能。详情:隐私政策。
链接
免费使用,源代码托管于 GitHub。由 DarkZmaj 为 KORI Network 制作。
Sends every player to the best hub on your BungeeCord or Velocity proxy, and keeps them waiting in limbo instead of kicking them when no hub is free.
FlowGate Lite checks your hubs all the time and sends each new player to the least busy healthy one. When every hub is down or full, players wait on a limbo server and are moved to a hub by themselves as soon as one is free. It runs only on the proxy, and the same jar works on BungeeCord, Waterfall and Velocity.
Features
- Health checks. Pings every hub in the background and skips a hub that stops answering until it is back.
- Least busy hub. New players go to the healthy hub with the fewest players, with optional weights and a player cap.
- Limbo. When no hub is free, players wait on a fallback server with a "Waiting" title and leave by themselves when a hub is ready.
- Kick fallback. A player kicked from a backend goes to another hub or to limbo instead of being disconnected.
- Hub and server commands.
/hub, /lobby and your own commands such as /survival.
- Backend requests. Checks
Connect requests from game servers, for example from FlowGate Bridge, against your allow list.
- MOTD. Server list text and hover lines with
& codes and hex colours.
- Status.
/flowgate status shows every server's health and routing counters.
Supported platforms
- Velocity: 3.4 and newer, including 4.x (tested on 3.4.0, 3.5.1, 4.3.1 and 4.3.2).
- BungeeCord and Waterfall: current builds (tested on BungeeCord 2111 and Waterfall 615).
- Java: 17 or newer. Velocity 4 needs Java 25.
- On Velocity: restricted-server checks are BungeeCord-only, and backend
Connect checks need bungee-plugin-message-channel = false in velocity.toml.
Installation
- Download
FlowGate-Lite-1.0.8.jar from one of the links below.
- Put it in the proxy's
plugins folder and restart the proxy.
- Put your hub and limbo server names in
config.yml, then run /flowgate reload.
Full setup: Install guide.
Privacy
Once a day FlowGate Lite tells kori.my that one more server runs it: an anonymous ID, the plugin version, the platform and that it is a proxy. No IP addresses, server names or player data. Turn it off with metrics.enabled: false in config.yml. Details: Privacy Policy.
Links
Free to use, with the source code on GitHub. Made by DarkZmaj for KORI Network.
评论 0
登录后参与评分
还没有评论,来抢沙发吧