-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when interacting with anything on 1.8.8 backend #192
Comments
Update |
Hi, I think you need the legacy addon for protocolizer if you want 1.8 support, I'm doing a similar setup to you (waterfall with the legacy addon, to pandaspigot (a fork of paper, not spigot) with viaversion there) and I can connect with 1.8.9 without ant error |
Hi @jehendeoff! |
Sorry for the late response. At first I don't recommend installing ViaVersion on the proxy server. Nevertheless this issue still is present so I assume it has to do with the packet decoding. Are mods in use? This issue would definetely occur everywhere else if it was a general decoding issues for all Minecraft client versions. The Backend Server version in this case is irrellevant since the error occurs during decoding of the player packets. Please be sure to run the latest version of the proxy and Protocolize. |
Any update on this? |
Oh, yeah, sorry for not responding! |
Does this issue still occur with the latest version of Waterfall and Protocolize? |
I have viaversion on bukkit I can't put it, I can't put it in both as the same dev of viaversion says also I need it on bukkit how can I solve ? |
I don't quite understand what you mean, but you can't run ViaVersion on bukkit and on the proxy, that's right. You also don't have to run ViaVersion on the proxy since I cannot recommend doing so. |
I'm going to re-check it, thanks |
Describe the bug
When using protocolize on waterfall 1.20 and joining a 1.8.8 backend
an error occurs and kicks the client:
This issue persists no matter the client's version (I'm using latest ViaVersion)
The issue doesn't happen on versions >= 1.12, I can't test if the same applies for < 1.12
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Players should be able to play as normal
Proxy environment
Proxy: waterfall-1.20-536
Protocolize: latest at the time
ViaVersion: 4.7.0
Minecraft versions used
Minecraft versions: ALL tested, none of them is able to successfully play on the server
Backend versions:
The text was updated successfully, but these errors were encountered: