"NullReferenceException" before the first connection attempt. about riptide HOT 3 CLOSED

The only thing that could cause a NullReferenceException on line 297 of the Client class is connection being null, which it will be if you haven't initiated a connection yet. However, Riptide itself does not try to send any messages before initiating a connection, which means that you must be trying to send something before connecting...

Do you send messages in Update or from anywhere else which might execute before you call your client's Connect method?

from riptide.

Oh well. Indeed I send messages on Update before client is connected. Previous RiptideNetworking version was ok with that :D
Connection null check with some error message would be nice though, for debugging.

from riptide.

Previous RiptideNetworking version was ok with that

I'm pretty sure it just silently discarded the message though. It wouldn't have tried to actually send it without being connected.

Connection null check with some error message would be nice though

I mean you are getting an error message (the NullReferenceException), and the stack trace should show you exactly what your own code is calling to cause it—it's just that it doesn't explicitly tell you "you can't send messages until you're connected."

from riptide.