Just small change adding an error log - I think extra explanation what happens and what should be done when trying to connect with non-empty message (for example made using Message.Create(MessageSendMode.Reliable, 0) instead of Message.Create()) could be useful to save other programmers some debugging.
This is a good idea, but I think the message can be clarified/simplified, the check can just be if (message.ReadLength != 0), and this error should be logged in a few other places as well.
Just small change adding an error log - I think extra explanation what happens and what should be done when trying to connect with non-empty message (for example made using
Message.Create(MessageSendMode.Reliable, 0)
instead ofMessage.Create()
) could be useful to save other programmers some debugging.I've noticed this issue being mentioned previously in the past: https://github.com/RiptideNetworking/Riptide/issues/65