-
-
Notifications
You must be signed in to change notification settings - Fork 693
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
Refactor GameProtocol to remove version slash-combinations #4979
base: master
Are you sure you want to change the base?
Conversation
@@ -84,7 +84,7 @@ public final class GeyserServer { | |||
/* | |||
The following constants are all used to ensure the ping does not reach a length where it is unparsable by the Bedrock client | |||
*/ | |||
private static final String PING_VERSION = pingVersion(); | |||
private static final String PING_VERSION = GameProtocol.DEFAULT_BEDROCK_CODEC.getMinecraftVersion(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not against this, but one thing that should be noted here is that because we no longer override minecraftVersion the ping version will now become 1.21.20 instead of 1.21.21 (which was the version that'd show in the ping before this PR)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch
thanks |
These changes need to be re-tested |
…ctor-gameprotocol # Conflicts: # core/src/main/java/org/geysermc/geyser/network/UpstreamPacketHandler.java
changes
bedrockVersions
field in Geyser dumps has the same effective change ^api changes
GeyserApI#supportedBedrockVersions()
now returns a list whose MinecraftVersions are all a single minecraft version; no slash combinations. This means there are multiple MinecraftVersions in the list of that same protocol version, but the minecraft versions are actually parseable.other notes
Unrelated to this PR, disconnect messages for outdated clients for versions >=622 and <712 are currently broken. CloudburstMC/Protocol#255 will allow us to fix that in the future.