IsOwner false on a NetworkBehaviour with 'NetworkObject that has IsOwner = True'

[MaybeKush]

Description

I have a class Fighter inheriting from NetworkBehaviour. Then a more specific class for the Fighter innheriting from Fighter. That class is attached to an object with NetworkObject component attached. I start server, spawn the object on Server (dynamically) with ownership = client (btw I spawn this new NetworkObject by Instantiating it under our Player default object, which is spawned by Network Manager under the Default Player Prefab field. Then after Instantiating it under that, only 1 line after I spawn it on the Network using its NetworkObject through the server). NetworkObject says IsOwner true, NetworkBehaviour script says IsOwner = false.

Reproduce Steps

Idk the steps exclusively. Though it could be related to Inheriting or how I instantiated it.

Actual Outcome

IsOwner is false on NetworkBehaviour but true on NetworkObject.

Expected Outcome

IsOwner should have been true in both NetworkObject and all NetworkBehaviours attached to it.

Screenshots

Console is logging IsOwner from the NetworkBehaviour script

Environment

• OS: Windows 10
• Unity Version: 6000.0.24f1
• Netcode Version: 2.2.0
• Netcode Commit: Idk specifically, but the Package manager says released on December 16, 2024

[EmandM]

What NetworkTopology are you using (Client-Server or Distributed Authority)? Could you post the code showing how you're instantiating the NetworkObject and the NetworkBehaviour?

[MaybeKush]

Sorry, didn't mean to close the issue lmao.

This is the part where the network object is spawned. The OnNetworkSpawn method is on the "Player" object which is instantiated through the default player reference in NetworkManager which instantiates the "Player" object as soon as a client joins.

[EmandM]

Thank you for the code snippet. Do you mind explaining more about what behaviour you were expecting vs what was happening?

[MaybeKush]

I am spawning the FIGHTER object with SpawnWithOwnership so I am expecting all the NetworkBehaviours attached on that FIGHTER object to also have isOwner = true for owners.

But as it turns out, only the NetworkObject component has isOwner = true for owner clients, and not the network behaviours.

I am currently working around this by using reference of the NetworkObject and checking NetworkObj.IsOwner.

[NoelStephensUnity]

Hi @MaybeKush,

There might be some additional script I will need to better help you, but before we do that I have some recommendations based on the script segment you provided us:

• Your script looks like it is Instantiating a NetworkObject and not the entire network prefab GameObject?
  • i.e. NetworkObject nObj = Instantiate(_fighters[1], transform);
    • My assumption is you are not getting any form of compilation error so _fighters[1] is an array of NetworkObjects?
  • This will not create a full network prefab instance.
  • You might try:
    • Instantiating the root GameObject of the network prefab asset.
    • Get the NetworkObject component of the instance.
      • Use this to invoke the Spawn method.
    • =or=
    • Use NetworkObject.InstantiateAndSpawn using the root GameObject of the network prefab asset.
• I would recommend doing any spawning within the OnNetworkPostSpawn and not OnNetworkSpawn.
  • The reason being is that OnNetworkSpawn is while the NetworkObject is still in the middle of spawning (i.e. not all NetworkBehaviour components will have run through the spawn process yet) while OnNetworkPostSpawn assures that all NetworkBehaviour components have run through the spawn process (i.e. all spawned properties will be set on all of the associated NetworkBehaviour components).
• Since you are spawning instances for each client connected, I would actually check against the NetworkBehaviour component's OwnerClientId relative to the default player prefab instance's OwnerClientId just to make sure you aren't checking for IsOwner on the Server/Host side when it is actually a newly connected client's player.
• I noticed that you are passing in a direct NetworkObject as a parameter in InitializeOnTargetRpc. This will not work as you must use a NetworkObjectReference to do this (so you will want to make that adjustment too).

Once you have made those adjustments, let me know if you are still getting the same result.