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
In Minecraft, it's possible to check if your client version aligns with the server's supported versions.
Take a look at these visual indicators:
For clients supporting your server version, they conveniently display their current player count:
However, there's an existing challenge with CloudNet. When the Protocol-Text is modified to anything other than null, CloudNet automatically assumes that the server is undergoing maintenance or a similar state. To resolve this, a viable solution would involve adding an additional entry in the config.json file for supported Minecraft versions.
Furthermore, the code needs adjustment to ensure the Version Number is correctly set based on the provided text, rather than defaulting to 1.
Describe the new feature
In Minecraft, it's possible to check if your client version aligns with the server's supported versions.
Take a look at these visual indicators:
For clients supporting your server version, they conveniently display their current player count:
However, there's an existing challenge with CloudNet. When the Protocol-Text is modified to anything other than null, CloudNet automatically assumes that the server is undergoing maintenance or a similar state. To resolve this, a viable solution would involve adding an additional entry in the
config.json
file for supported Minecraft versions.Furthermore, the code needs adjustment to ensure the Version Number is correctly set based on the provided text, rather than defaulting to 1.
https://github.com/CloudNetService/CloudNet-v3/blob/nightly/modules%2Fsyncproxy%2Fsrc%2Fmain%2Fjava%2Feu%2Fcloudnetservice%2Fmodules%2Fsyncproxy%2Fplatform%2Fvelocity%2FVelocitySyncProxyListener.java#L81
Why do you need this feature?
This feature will empower players by providing clarity on whether they are using a Minecraft Protocol Version that is supported by the server.
Alternatives
I don't think so.
Other
No response
Issue uniqueness
The text was updated successfully, but these errors were encountered: