I just stumbled across this while taking a look at the LagCompensationManager - there is a possible System.NullReferenceException in Update:47 which will be caused when networkManager is null.
The issue with this line is, that the && operator has precedence over || so if networkManager is null, it will check the second condition, networkManager.IsClient.
I just stumbled across this while taking a look at the
LagCompensationManager
- there is a possible System.NullReferenceException in Update:47 which will be caused whennetworkManager
is null.The issue with this line is, that the
&&
operator has precedence over||
so ifnetworkManager
is null, it will check the second condition,networkManager.IsClient
.