ninjakickja

> true story **Current findings:** When you cancel connection attempt, StopClient is called, which flows down to KcpClient.Disconnect(). However, the client never connected, so the connected bool is false, which...

> Which layer is this an issue in? The transport wrapper to KCP or the KCP logic itself? I think the wrapper. KCPClient.cs

in KCPClient.cs: adding else // if not connected { connection = null; } seems to solve the issue, but causes a new NRE error because connection became null. This is...

Can't a similar solution work, just have separate bools for server and client, not using the same?

Yep you cannot disable and re-enable NTR like this. Unless you can trick the OnSerialize to set 'initialState' = true. I reckon you are better off introducing another bool for...