It should be possible to find network objects using their ID

[ashkan-saeedi-mazdeh]

Is your feature request related to a problem? Please describe.
This is mostly a convenience and resource saving feature.
I want to find NetworkObjects using the object id sent over the network and MLAPI of course contains the list.

Describe the solution you'd like
Expose the list to the users by using NetworkManager.GetNetworkObject(objectId); or somethign similar so we don't have to maintain a redundant separate list.

Describe alternatives you've considered
I can add a NetworkTracked component to my objects and maintain the list myself.
it will be redoing some done work and an additional list in memory and I might get Network life-cycle callbacks wrong.

Additional context
You need this when an RPC should work on multiple objects or has to work at least on one object other than the one it is being called on.

[LukeStampfli]

You can use NetworkSpawnManager.SpawnedObjects[objectId] for this. Is this sufficient?

[LukeStampfli]

Closing this issue, the solution above should work. Alternatively starting from 1.0.0 there is also the NetworkObjectReference type which can be used to serialize a reference to a NetworkObject over the network.

[ashkan-saeedi-mazdeh]

sorry for not seeing this
If the solution using SpawnManager works on the clients too. that is good enough. otherwise, NetworkReference is mandatory if you don't want to maintain a list.