Bug NetworkManager.Singleton.IsClient is TRUE on dedicated server

OK I'm not sure HOW I haven't noticed this before, but I just ran into a nasty issue where NetworkManager.Singleton.IsClient is TRUE on dedicated server builds.

I just HAPPEN to have a decent workaround for this that fixes just about every issue I'll have as a result, but I was curious if anybody else has tested a Dedicated Server build? I'm not sure what I could've done on my end for this to be messed up but I wouldn't put it past me

 

Is this maybe before the server got started, or called too early before NetworkManager is initialized? Maybe the dedicated server build is actually running StartClient() instead?

You may want to make a simple test with a new project to confirm whether the issue is reproducible if you can't find a flaw in your code. When an issue like this seems as fundamental as you describe it, I find it likely it is already known with users complaining but I'm not aware of any of that. I would first check the more likely causes (see above).

That's not to say it cannot be a bug, just doesn't seem very likely.
Btw, which version of Netcode? Maybe try upgrade to the latest (v1.2) if you aren't using that.

 

I just tested this and it's coming up as false for me. I don't check this flag though but use SystemInfo.graphicsDeviceType == UnityEngine.Rendering.GraphicsDeviceType.Null to check it's the server in the bootstrap code. The bootstrap code itself is a cut down version of the Multiplay example.

 

I'm not using batchmode or any server command line arguments outside of my own, should I be? (this is in Unity 2020)