NetworkObject despawning state

[danielchipman]

Is your feature request related to a problem? Please describe. Situation: A client script is holding a reference to a NetworkBehaviour. The associated NetworkObject is despawned, and in response to the NetworkBehaviour reporting this to the reference holder, the ref holder starts listening for when the same object is respawned, using its network ID. Applicable scenario would be for intermittent client disconnects, and area of interest. Currently, NetworkObject.IsSpawned doesn't get set to false nor does it get removed from NetworkSpawnManager until after NetworkBehaviours finish their OnDespawn behavior. As a result, the system acts as if the object is indeed spawned. NetworkBehaviour.IsSpawned doesn't help here since looking for a respawn requires observing the NetworkObject directly through the NetworkSpawnManager.

Describe the solution you'd like Set NetworkObject.IsSpawned = false and remove from NetworkSpawnManager.SpawnedObjects before calling networkObject.InvokeBehaviourNetworkDespawn()

Describe alternatives you've considered If the above causes backwards incompatibilities or other breaks in dependencies during shutdown flow, could add an IsDespawning flag or change IsSpawned to a state enum that can convey the accurate status of the NetworkObject while it is being despawned.