o3
o3 copied to clipboard
Unknown PktType: 0xe0
Unknown PktType: e000ReceiveMessages: unhandled packet type:
There is a fmt.Printf()
in the lib in handleClientServerMsg()
in packethandler.go
.
Thus packettypes.go
is missing the 0xe0.
I think it happened, when a accidentally started one client twice.
While e000
is the output of this Printf()
, I verified the pktType 0xe0
with temporary inserting and handling unknownE0 pktType = 0xe0
.
Looks like you found the "duplicate connection" packet!
Phillipp Berger of OpenMittsu seems to agree: https://github.com/blizzard4591/openMittsu/blob/ae6364826a0b918a51c20c2e1caa6d0457f8e964/src/protocol/ProtocolSpecs.h#L42
I have never seen it before but I will check the Android App to confirm.
This actually also touches #14. When I start two clients at once, the second one receives this message and crashes shortly afterwards. Will try to implement safe handling.
We are now handling this. However, the implementation and communication of errors is very basic and not well thought out. Since we need to rewrite connection handling anyway I didn't put much thought into a clean solution.