marzvrover / swiftcraft Goto Github PK

Is this project active or discontinued?

Should properly handle the legacy 0xFE handshake packet

To throughly test the decoder, as #9 calls for, we will also need to be able to encode packets.
We need to encode packets to be able to achieve any sort of communication with the client as well. Thus making it a requirement for #3 too.

I need to come up with the best way to test the MessageToByteEncoder part of the PacketCodec. A quick glance shows that there is not a helper like the ByteToMessageDecoderVerifier for the MessageToByteEncoder.

I need to come up with a way to have a TestPacket that can change definition while still being able to decode it in PacketDecoder so that I can test the decoder.

Add all the datatypes used in the Minecraft Protocol

Clients need to be able to login to the server

At this moment Codec tests are attempting to test just the encoded packet data. In buffer we must first write the length of the Packet.id and all of the data in a VarInt. After that the Packet.id must be written in a VarInt, and finally the data will be written.

With the realm/jazzy workflow running, it is time to start staying on top of documentation.

The macOS workflow is failing. Should be able to pull the work from swiftpackages/Heap to get it to work. Will want to ensure the ubuntu workflow using using the same swift version and that swiftpackages/DotEnv is updated.

Add real logging instead of just print statements

This test throws the Error Unexpected Packet ID 724. I believe this is due to an issue with writing a VarInt of 0x00, but further investigating is required.

Add tests for the PacketDecode ByteToMessageDecoder