Closed zachstronaut closed 2 months ago
@zachstronaut This will be resolved in the next NGO v1.12.0 update. It will now only log a warning if developer logging is enabled and ignore the RPC. If developer logging is not set, then it just ignores the RPC.
Remote client can send RPC to NetworkObject that has been despawned on host, resulting in error in ProxyMessage on the host when the RPC is received:
Define your RPC like this and call it on the client:
Despawn the same NetworkObject on the host:
myNetObject.Despawn();
Depending on (I assume) message timing and latency, you can get your RPC message from the client to arrive on the host after the network object has despawned there, and then you get the error.
However, the remote client will not have called any
OnNetworkDespawn
methods yet so it has no way of knowing this will happen, and so I'm not sure how to prevent it?Netcode 1.9.1