"NullReferenceException" before the first connection attempt.

[corthax]

With or without server, before the first connection attempt console is spammed with errors. After - it's ok.

After clients are connected everything seems to work fine...

Custom project (based on your youtube tutorial).

All breaking code changes are applied.
Installed with Package Manager.

On client, without server:

On client, with server:

On server, throw error after client connects, for each client:

[tom-weiland]

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?

[corthax]

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.

[tom-weiland]

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."