Jet currently has only one Minecraft protocol state fully implemented. It is handshake. However, after handshake, client requests a server to switch to one of two protocol states. They are login and status. While login is for logging a player into a server, status is for server list pinging. Login is needed by Jet, because it is an unmodifiable behaviour and is required to let a player join to the server.
Jet currently has only one Minecraft protocol state fully implemented. It is handshake. However, after handshake, client requests a server to switch to one of two protocol states. They are login and status. While login is for logging a player into a server, status is for server list pinging. Login is needed by Jet, because it is an unmodifiable behaviour and is required to let a player join to the server.
This issue is related to https://github.com/Hypejet/Jet/issues/4