fix(velocity): upgrade the proxy to 3.5.1 for Minecraft 26.2 - #181
Merged
Conversation
The proxy pinned Velocity 3.5.0-SNAPSHOT build 601 (2026-06-02), which
predates build 604 (2026-06-16, "Minecraft 26.2"). Velocity's ProtocolVersion
enum only gained MINECRAFT_26_2(776) in that build, so the current image
cannot accept 26.2 clients at all -- it would reject them on handshake once
the lobby moves to 26.2.
Move to 3.5.1 build 615: a RECOMMENDED-channel release that contains the 26.2
protocol and stays on the 3.x plugin API, so plugin-agones-velocity 0.5.1,
grounds-platform 0.6.0 and plugin-grounds-runtime 0.1.1 keep working as-is.
Velocity 4.0.0 has no published builds (only 4.0.0-SNAPSHOT) and rewrites the
plugin API, so it would strand all three plugins.
Verified: image builds; the proxy boots ("Booting up Velocity 3.5.1", "Done"),
loads all three Grounds plugins with no API errors, and a server-list ping as
a protocol 776 client is accepted (reports "Velocity 1.7.2-26.2"). Protocol
775 (26.1.2) clients are still accepted, so this is safe to roll out ahead of
the backends.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The proxy cannot accept Minecraft 26.2 clients today. We pin Velocity
3.5.0-SNAPSHOTbuild 601 (2026-06-02). Velocity'sProtocolVersionenum only gainedMINECRAFT_26_2(776)in build 604 (2026-06-16, PR #1807). So the moment the lobby moves to 26.2, 26.2 clients get rejected at handshake.What
VELOCITY_VERSION3.5.0-SNAPSHOT3.5.1VELOCITY_BUILD6016153.5.1 build 615 is on the RECOMMENDED channel (released 2026-07-11), contains the 26.2 protocol, and stays on the 3.x plugin API.
Why not Velocity 4
4.0.0has no published builds —/v3/projects/velocity/versions/4.0.0/buildsreturns[]. The only v4 artifact is4.0.0-SNAPSHOTbuild 5, cut 2026-07-11. v4 also rewrites the plugin API, which would strandplugin-agones-velocity 0.5.1,grounds-platform 0.6.0andplugin-grounds-runtime 0.1.1until all three are ported and re-released. Not worth it to gain a protocol 3.5.1 already has.Verification
Image built locally and run:
Booting up Velocity 3.5.1...→Done (1.82s)!, listening on 25565.Loaded plugin grounds-platform 0.6.0,Loaded plugin plugin-agones 0.5.1,Loaded plugin plugin-grounds-runtime 0.1.1.Velocity 1.7.2-26.2.Chain
Pairs with groundsgg/minestom-lobby#23 (lobby → 26.2) and groundsgg/grounds-dependencies#3 (BOM → Minestom 26.2). This one is independent and safe to merge first.
Still open:
paper/Dockerfileandpaper-gamemode/Dockerfileare onPAPER_VERSION=26.1.2(protocol 775). Velocity does not translate protocols, so a 26.2 client can reach the 26.2 lobby but will be kicked when it is routed to a 26.1.2 Paper gamemode server. Deliberately out of scope here.