Some players cannot join with different version from the server about fabricproxy-lite

[DominoWWW]

Yes, support 1.19-1.19.2 servers would be quite nice!

[james58899]

The 1.19.3 and 1.19.2 handshake packets are incompatible.

[gadget78]

would this be the reason for floodgate having issues with this ??

[Glucy-2]

would this be the reason for floodgate having issues with this ??

What do u mean, I am using floodgate but this issue doesn't seem to be related

[warmbroke]

diff --git a/proxy/src/main/java/com/velocitypowered/proxy/connection/backend/LoginSessionHandler.java b/proxy/src/main/java/com/velocitypowered/proxy/connection/backend/LoginSessionHandler.java
index 8495a878..fcc80b06 100644
--- a/proxy/src/main/java/com/velocitypowered/proxy/connection/backend/LoginSessionHandler.java
+++ b/proxy/src/main/java/com/velocitypowered/proxy/connection/backend/LoginSessionHandler.java
@@ -187,7 +187,7 @@ public class LoginSessionHandler implements MinecraftSessionHandler {
             ? VelocityConstants.MODERN_LAZY_SESSION
             : VelocityConstants.MODERN_FORWARDING_DEFAULT;
       }
-      if (player.getIdentifiedKey() != null) {
+      if (false && player.getIdentifiedKey() != null) {
         // No enhanced switch on java 11
         switch (player.getIdentifiedKey().getKeyRevision()) {
           case GENERIC_V1:

Just patch out forwarding version 2 and 3 directly in velocity. This is the easiest way.

[RealKomander]

diff --git a/proxy/src/main/java/com/velocitypowered/proxy/connection/backend/LoginSessionHandler.java b/proxy/src/main/java/com/velocitypowered/proxy/connection/backend/LoginSessionHandler.java
index 8495a878..fcc80b06 100644
--- a/proxy/src/main/java/com/velocitypowered/proxy/connection/backend/LoginSessionHandler.java
+++ b/proxy/src/main/java/com/velocitypowered/proxy/connection/backend/LoginSessionHandler.java
@@ -187,7 +187,7 @@ public class LoginSessionHandler implements MinecraftSessionHandler {
             ? VelocityConstants.MODERN_LAZY_SESSION
             : VelocityConstants.MODERN_FORWARDING_DEFAULT;
       }
-      if (player.getIdentifiedKey() != null) {
+      if (false && player.getIdentifiedKey() != null) {
         // No enhanced switch on java 11
         switch (player.getIdentifiedKey().getKeyRevision()) {
           case GENERIC_V1:

Just patch out forwarding version 2 and 3 directly in velocity. This is the easiest way.

What does this mean? I have the same bug, how to fix it?

[RealKomander]

please help!

[james58899]

Closed, as this is an old issue and unlikely to be fixed.