hypejet / jet Goto Github PK

Since Minecraft 1.16, servers are able to send custom registry data, such as biomes and dimension types. Since Jet aims on customizability, it should be added before 1.0 release.

Jet data needs to be finished first.

Minecraft servers have an important feature for client -> server interaction. It is called "commands". Commands are represented by a string, which server parses and does a certain thing. Mojang introduced an open-source command parser, which is even used by a vanilla server. Due to that, it should not be hard to implement a command system with brigadier - the command parser - and it would let users create commands easily.

An event system is needed in Jet in any case. Our Minecraft server software does not contain any vanilla features, it it up to user to re-implement them if they are needed. However, server's behaviour can not be controlled via plugins without an event system.

Since Play Minecraft Protocol State is huge, we decided to split development of it to multiple pull requests.

This pull request aims on making a server joinable. That means that a player is spawned on a world with chunks.

Related to: #21

SWF is a pretty nice and tight world format, suitable for networks.

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 #4

Status is one of two Minecraft protocol states that follow a handshake packet. A use case of it is to receive a server list MOTD.

Related to: #4

Jet should support SpongeMixins, might be complicated as we need to have a class transformer or something, however there are already libraries doing this and fabric has a pretty full library doing this too.

Plain Jet does not have any behaviour. It it up to a user to add it. To do that, it's needed to have a plugin system, which would contain all API interfaces to interact with server.

Play protocol state is a Minecraft protocol state, during which the game is in progress.

This is the most important state to implement in Jet.

Related to: #4

Since Jet aims on maximum customizability, it needs to have a support for chat and command signing. However, we do not plan on making a ready implementation, it is up to a user to do that.

Since Jet is a Minecraft server software, it needs to contain every packet supported by the Minecraft protocol.

Configuration is a Protocol State, during which server initializes world and settings, such as resource packs. Jet cannot fully work without this state with modern versions of Minecraft.

Related to: #4