Add a NetworkBehaviour component after calling NetworkObject.Spawn()

[TheCaveOfWonders]

Is your feature request related to a problem? Please describe.
We currently cannot dynamically add NetworkBehaviours to a GameObject AFTER having spawned the object on the clients, so after calling NetworkObject.Spawn() for that object.

Describe the solution you'd like
Add a NetworkBehaviour AFTER the GameObject in question already spawned on the clients.

Additional context
One of the goals is to have the server spawn prefab GameObjects on the clients, and then add NetworkBehaviours to them pending some conditions.

If this is something that will not or cannot be supported -at least not in the near future- please let me know and I'll try to design my way around it.

[luismasuelli]

I think this will be easier if you do a NetworkBehaviour doing like this:

public SyncronizedComponentAdder : NetworkBehaviour {
    public void AddSyncComponent<T>() {
        if (!isServer) throw new RuntimeError();
        AddComponent<T>();
        AddSyncComponentClientRpc(typeof(T).FullName);
    }
    [ClientRpc]
    private void AddSyncComponentClientRpc(string fullName) {
        // Get type by its full name: https://stackoverflow.com/questions/1392763/creating-c-sharp-type-from-full-name
        // Actually, there are many ways of iterating multiple assembles to search where the type is declared.
        Type type = yourOwnImplementationToGetTypeByFullName(fullName);
        // Remember that Unity allows this way of calling AddComponent.
        AddComponent(type);
    }
}

This is just a concept. I did not test it, but you can do something like this to work.

[JesseOlmer]

This feature request is not in the short term plans for the SDK.