itzg/docker-mc-proxy

Velocity 1.18 Support

weihao opened this issue · 8 comments

Tracking 1.18 proxy server support

itzg commented

The image isn't tied to any particular version. What are you wanting to track exactly?

@itzg VELOCITY_VERSION: "latest" only pulls the 1.17 version currently. I want to track when it support 1.18

itzg commented

Now I'm really confused. Velocity is a proxy and doesn't need to track the Minecraft versions such as 1.18. Their latest is 3.1.0:

https://velocitypowered.com/downloads

itzg commented

Aha, the solution was discovered in #82

The issue is that Velocity "pretends" to be the newest client version it is aware of when connecting to a Minecraft server, since they moved their repo, the version we have been pulling down is pretending to be 1.17.x so it gives an Outdated client error when connecting to 1.18.

I wish I had figured this out a month ago, I could have posted it here then, but I just found out they moved their repo about an hour ago. They had mentioned they were migrating, but I saw no other info and was hoping they would wait until AFTER a major Minecraft update to change everything. (especially since I just switched to Velocity in November after testing it in Oct...) I was trying to get it working with viaversion to put my snapshot server on the proxy and couldn't figure out why it was saying outdated client...

I am able to reproduce this:

https://github.com/itzg/docker-bungeecord/blob/8e094dbe35e64baad502816c59181326177d11af/run-bungeecord.sh#L198

https://versions.velocitypowered.com/download/latest.jar returns velocity-3.0.1

itzg commented

The issue is that Velocity "pretends" to be the newest client version it is aware of when connecting to a Minecraft server, since they moved their repo, the version we have been pulling down is pretending to be 1.17.x so it gives an Outdated client error when connecting to 1.18.

Thanks for the clarification. That totally makes sense now.

itzg commented

I'm going to close this and consolidate discussion onto #82