The second client to connect is disconnected because a reliable message can't be delivered

[tom-weiland]

When connecting multiple clients (tested with the dedicated server demo and the sample FPS project) the first to connect works as expected, but the second to connect is disconnected almost immediately due to "poor connection".

This is because of an issue in the Converter.SetBits method that causes it to not properly overwrite bits in some cases, which can scramble the data in messages. This results in an incorrect sequence ID being written to the message, meaning it can't be acked properly, so the sender thinks it's not being delivered despite the receiver receiving it.