ApolloPlayerTransfer
别再让代理重启时流失你的 Lunar Client 玩家。
在现代 Velocity 网络中,当代理关闭(重启、维护或扩容)时,玩家会被自动转移到其他代理而毫无察觉……但仅适用于较新的客户端。
Velocity 的原生传输依赖于 Minecraft 1.20.5 引入的一个数据包。所有运行旧版本(包括大量 Lunar Client 用户)的玩家无法识别该数据包,因此会被直接断开连接,而不是被转移。
ApolloPlayerTransfer 填补了这一空白。 它不是“又一个传输插件”:它是为 Apollo 兼容的旧版玩家 带来传输功能的扩展,这样代理重启就不再导致他们掉线。
具体问题所在
想象一个拥有多个 Velocity 代理的网络。其中一个需要重启或替换:
| 玩家类型 |
无此插件 |
有此插件 |
| 1.20.5+ 客户端(任何客户端) |
✅ 原生传输,无中断 |
✅ 原生传输(不变) |
| 旧版客户端 + Lunar Client (Apollo) |
❌ 断开连接 |
✅ 通过 Apollo 传输,无需重新连接 |
| 不支持传输的旧版客户端 |
❌ 断开连接 |
❌ 断开连接(无法传输) |
简而言之:近期玩家继续像往常一样被移动,而你旧版本的 Lunar Client 玩家现在也可以了,不会再从服务器掉线。
真实场景
你运营着一个由单个域名背后的 3 个 Velocity 代理组成的网络。某天晚上你推送更新,代理 #2 需要重启:
- Velocity 立即将每个 1.20.5+ 玩家移动到代理 1 和 3。
- ApolloPlayerTransfer 接管你的 旧版 Lunar Client 玩家,并将他们发送到与所有人相同的备用代理。
- 你的玩家继续游戏。没有人需要重新连接,没有排队,也没有“你已断开连接”的提示。
这正是以前社区的一部分会在每次重启时掉线的情况。这个插件让他们保持在线。
兼容性“我的设置能用吗?”
在代理上安装任何东西之前,这里有一些关键点:
- ✅ 代理: 需要 Velocity-CTD(正是 CTD 决定了要使用的备用代理)。
不支持纯 Velocity,因为备用选择依赖于 CTD 的
[proxy-addresses] 机制。ApolloPlayerTransfer 没有重新发明任何东西:它复用了你配置中已有的代理选择逻辑。
- ✅ 客户端: 需要在代理和本地都安装带有 Apollo 的 Lunar Client,并启用传输模块。只有 Apollo 玩家才能被传输。
- ✅ Minecraft 版本: 专为 低于 1.20.5 的玩家设计(1.20.5+ 已经由原生处理,插件不干预他们)。
- ✅ 多代理网络: 专为拥有多个代理的网络构建(通常使用 Redis,用于
MOST_EMPTY / LEAST_EMPTY 备用过滤器)。这才是传输真正有意义的地方。
- ✅ Java 21+,就像现代 Velocity 代理一样运行。
- ✅ 零配置维护: 插件不添加配置文件。它读取你现有的
velocity.toml。不需要进行任何新调整即可发挥作用。
如果你的网络符合这种情况,那么这个插件就是为你量身定制的。
安装
- 将两个插件放入代理的
plugins/ 文件夹:
- Apollo-Velocity : 下载
- ApolloPlayerTransfer (本页的
.jar 文件)
- 确保 Apollo 配置中的 传输模块 已启用。
- 重启代理。搞定,插件会使用你已有的 Velocity-CTD 配置。
对于完全透明的传输(可选但推荐)
这些设置不是传输工作的必要条件,但它们使传输对玩家完全透明:
- 跳过 Lunar Client 确认弹窗:在你的域名上添加一个
mc_transfer_accept_from TXT DNS 记录,以自动接受你自己服务器之间的传输。
- 避免“已连接到远程代理!”消息:在
velocity.toml 中启用会话接管 (kick-existing-players / kick-existing-players-check-ip)。
这两项设置的详细信息以及插件的内部机制记录在 项目的 GitHub 页面。
插件不能做什么
为了避免任何意外,让我们明确一下:
- 它不会神奇地让每个旧客户端都兼容。既没有原生传输 (< 1.20.5) 也没有 Apollo/Lunar Client 的玩家无法被传输,他们会像今天一样断开连接。这是协议限制,而非插件问题。
- 它仅在优雅代理关闭时生效。如果是硬崩溃或断电,没有任何代码运行:在这种情况下无人能被传输,无论插件如何。
- 它不替代 Velocity 的原生传输:它补充了那些原本会被遗留的玩家类别。
简而言之
如果你运行一个多代理 Velocity 网络,并且部分 Lunar Client 玩家在每次代理重启时掉线,而其他玩家则被干净地移动:这正是本插件解决的问题。
基于 GNU GPL v3.0 许可证的开源插件。源代码、技术文档和发布跟踪见 GitHub。
ApolloPlayerTransfer
Stop losing your Lunar Client players every time a proxy restarts.
On a modern Velocity network, when a proxy shuts down (restart, maintenance, scaling),
players are automatically moved to another proxy without noticing a thing… but only
recent clients.
Velocity's native transfer relies on a packet introduced in Minecraft 1.20.5. Every
player on an older version, including a large share of Lunar Client users, does not
understand that packet and is therefore simply disconnected instead of being moved.
ApolloPlayerTransfer fills that gap. It's not "yet another transfer plugin": it's the
extension that brings transfers to Apollo-compatible legacy players, so a proxy restart
no longer drops them from your server.
The problem, concretely
Picture a network with several Velocity proxies. One of them needs to restart or be replaced:
| Player type |
Without this plugin |
With this plugin |
| 1.20.5+ client (any client) |
✅ Transferred natively, no interruption |
✅ Transferred natively (unchanged) |
| Older client + Lunar Client (Apollo) |
❌ Disconnected |
✅ Transferred via Apollo, no reconnection |
| Older client without transfer support |
❌ Disconnected |
❌ Disconnected (cannot be transferred) |
In short: recent players keep being moved as usual, and your Lunar Client players on older
versions now are too, instead of falling off the server.
A real-world scenario
You run a network with 3 Velocity proxies behind a single domain. One evening you push an
update and proxy #2 needs to restart:
- Velocity instantly moves every 1.20.5+ player to proxies 1 and 3.
- ApolloPlayerTransfer takes over for your Lunar Client players on an older version and
sends them to the exact same fallback proxy chosen for everyone else.
- Your players keep playing. Nobody had to reconnect, no queue, no "you were disconnected".
This is exactly the situation where, before, part of your community would drop on every restart.
This plugin keeps them online.
Compatibility "will it work with my setup?"
Before installing anything on your proxy, here's what matters:
- ✅ Proxy: requires Velocity-CTD (it's CTD that determines the fallback proxy to use).
Plain Velocity is not supported, since the fallback selection relies on CTD's
[proxy-addresses] machinery. ApolloPlayerTransfer reinvents nothing: it reuses the
proxy-selection logic already present in your configuration.
- ✅ Client side: requires Lunar Client with Apollo installed on the proxy and the
Transfer module enabled. Apollo players are the ones that can be transferred.
- ✅ Minecraft versions: designed for players below 1.20.5 (1.20.5+ are already handled
natively, the plugin leaves them alone).
- ✅ Multi-proxy network: built for a network with several proxies (typically with Redis,
required for the
MOST_EMPTY / LEAST_EMPTY fallback filters). That's where the transfer
really makes sense.
- ✅ Java 21+, like a modern Velocity proxy already runs.
- ✅ Zero config to maintain: the plugin adds no config file. It reads your existing
velocity.toml. There's nothing new to tweak for it to do its job.
If your network looks like this, this plugin is made for your case.
Installation
- Drop both plugins into your proxy's
plugins/ folder:
- Apollo-Velocity : download
- ApolloPlayerTransfer (the
.jar from this page)
- Make sure the Transfer module is enabled in Apollo's configuration.
- Restart the proxy. That's it, the plugin uses the Velocity-CTD configuration you already have.
For a truly invisible transfer (optional but recommended)
These settings are not required for the transfer to work, but they make it fully transparent
to the player:
- Skip the Lunar Client confirmation popup by adding a
mc_transfer_accept_from TXT DNS
record on your domain, to auto-accept transfers between your own servers.
- Avoid the "already connected to a remote proxy!" message by enabling session takeover in
velocity.toml (kick-existing-players / kick-existing-players-check-ip).
The details of both settings, along with the plugin's internals, are documented on the
project's GitHub page.
What the plugin CANNOT do
To avoid any surprises, let's be clear:
- It does not magically make every old client compatible. A player with neither the vanilla
transfer (< 1.20.5) nor Apollo/Lunar Client cannot be transferred, they'll be
disconnected just like today. That's a protocol limitation, not a plugin one.
- It only acts on a graceful proxy shutdown. On a hard crash or power loss, no code runs:
nobody can be transferred in that case, whatever the plugin.
- It does not replace Velocity's native transfer: it complements it for the category of
players it used to leave behind.
In short
If you run a multi-proxy Velocity network and part of your Lunar Client players drop on every
proxy restart while the others are moved cleanly: that's exactly the problem this plugin solves.
Open-source plugin under the GNU GPL v3.0 license. Source code, technical documentation, and
release tracking on GitHub.
评论 0
登录后参与评分
还没有评论,来抢沙发吧