-
Notifications
You must be signed in to change notification settings - Fork 169
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
Incompatibility with Velocity's modern forwarding. #1240
Labels
Comments
Modern forwarding doesn't work for < 1.13 so i guess this won't be a thing until ProtocolSupportVelocity becomes a thing (So i can transfer data at login state for old versions). |
In reference to the velocity issue; Do I correctly understand that this issue here is caused by ProtocolSupport disabling or changing vanilla behavior (with login plugin channels)? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is currently not possible to use Velocity's modern forwarding with ProtocolSupport. When a player tries to connect, the forwarding process breaks somewhere internally and a player cannot connect. Upon switching to legacy forwarding, which emulates Bungeecord's behavior, this issue is resolved. However, modern forwarding provides much better security, which cannot be found in Bungeecord without external plugins like IPWhitelist.
Server version: 1.15.2
/ps buildinfo:
protocolsupport.ProtocolSupport$BuildInfo(buildtime: 2020.03.16 at 04:11:14 MSK, buildhost: build.true-games.org, buildnumber: 481, buildgit: https://github.com/ProtocolSupport/ProtocolSupport:origin/master:7faca44da1740b9c455fc776f8043b2ccdb892b3)
The text was updated successfully, but these errors were encountered: