You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only thing is how would a client below 1.7 connect to the server via bungeecord/velocity (assuming the server is of a compatible version)? It would be unable to connect through either proxy and the server would block direct connections
I said that
It's just that if the server is below 1.7 then if you're using info forward the server will only accept bungee/velocity connections which the equivalent client for the server wouldn't be able to connect through making the server inaccessible to the target client somewhat defeating the point
But ViaVersion is available for 1.8+
I feel like this feature would be more useful for pre 1.8 servers that support bungeecord if it wasn't for the caveat of the actual clients being unable to connect
I don't think there is a good way to allow the clients to join and have the bungeecord forwarding. Thats just how its gonna be. Either have bungeecord forwarding enabled, but only allow 1.7+ clients or don't enable it and allow same version clients to join as well
Hello, how is this issue different from #654 ? Does this issue mean that you can have a backend server that does not support "modern" forwarding? Allowing you to put the backend server in offline mode and ViaProxy will keep the player skin etc and implement the modern forwarding logic + auth to the Velocity proxy?
This issue is regarding ViaProxy generating its own bungeecord/velocity-forwarding payload (For scenarios where ViaProxy is the only proxy and there is no Bungeecord/Velocity in the setup)
Activity
Hedwig7s commentedon Mar 25, 2024
Only thing is how would a client below 1.7 connect to the server via bungeecord/velocity (assuming the server is of a compatible version)? It would be unable to connect through either proxy and the server would block direct connections
RaphiMC commentedon Mar 25, 2024
Clients below 1.7 are not supported by ViaProxy
Hedwig7s commentedon Mar 25, 2024
I said that
It's just that if the server is below 1.7 then if you're using info forward the server will only accept bungee/velocity connections which the equivalent client for the server wouldn't be able to connect through making the server inaccessible to the target client somewhat defeating the point
RaphiMC commentedon Mar 25, 2024
This option is intended for 1.8+ servers
Hedwig7s commentedon Mar 26, 2024
But ViaVersion is available for 1.8+
I feel like this feature would be more useful for pre 1.8 servers that support bungeecord if it wasn't for the caveat of the actual clients being unable to connect
RaphiMC commentedon Mar 26, 2024
I don't think there is a good way to allow the clients to join and have the bungeecord forwarding. Thats just how its gonna be. Either have bungeecord forwarding enabled, but only allow 1.7+ clients or don't enable it and allow same version clients to join as well
jobpaardekooper commentedon May 24, 2026
Hello, how is this issue different from #654 ? Does this issue mean that you can have a backend server that does not support "modern" forwarding? Allowing you to put the backend server in offline mode and ViaProxy will keep the player skin etc and implement the modern forwarding logic + auth to the Velocity proxy?
RaphiMC commentedon May 24, 2026
This issue is regarding ViaProxy generating its own bungeecord/velocity-forwarding payload (For scenarios where ViaProxy is the only proxy and there is no Bungeecord/Velocity in the setup)