-
Notifications
You must be signed in to change notification settings - Fork 34
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
Krypton cannot connect to servers running the LilyPad proxy #22
Comments
This is actually an incompatibility between Krypton and the LilyPad proxy software. Given that Krypton works perfectly fine with BungeeCord, Waterfall, and Velocity, and the overall diminishing support for LilyPad, this is a bug but it is very low priority for me. |
Yeah, fair point. It was just this particular server that died with it. Perhaps you could maybe implement some form of "compatibility mode" (which just disables everything)? |
That is the wrong approach to take. Krypton is intended to be wire-level compatible. Any deviation from that is considered a bug. |
Fair enough. I just think it'd be an easy way to add ""compatibility""; just allow users to disable it in-game. |
After some further investigation, I have determined that the issue is triggered by the The issue arises specifically from a bug in LilyPad (or Given that this would affect a very limited audience (people running Linux and the minority of servers running LilyPad) I'm not in any big rush to fix this issue. You can work around it by adding |
I was joining the server (
play.mineclub.com
) because I heard of it and thought "why not?"But when joining with krypton, it doesn't allow you to join the server.
No stack trace in the console either.
Might have something to do with how they send a custom resource pack, but I'm not sure. I know so little about this domain that I'm not even going to attempt to diagnose any of this.
Or, it might just be because they're doing cursed packet stuff. Good lord, some of the packets they're sending are cursed. The stuff fills up my console to the brim with errors and warnings.
The text was updated successfully, but these errors were encountered: