RemoteDisconnect function

[noprops]

In the RemoteDisconnect function of MatchplayNetworkClient, it returns without action when clientId == m_NetworkManager.LocalClientId, and only calls NetworkShutdown if this is not the case. Why is this?
It feels like it should be the other way around, calling NetworkShutdown when clientId == m_NetworkManager.LocalClientId.

[JoshIpock]

​The Logic of RemoteDisconnect
​The reason NetworkShutdown is bypassed when clientId == m_NetworkManager.LocalClientId is to distinguish between a remote peer leaving and the local player leaving.
​Handling Remote Peers: When a different player (clientId != LocalClientId) is disconnected, the local client needs to clean up the network representation of that specific player. However, it should not shut down the entire network connection, as the local player is still in the game.
​The Local Player Exception: If the clientId matches the local player, the logic assumes that a full shutdown is either already being handled by a different specialized function (like Shutdown() or Disconnect()) or that calling a generic "Remote Disconnect" logic on oneself could lead to a recursive loop or a "ghost" session state where the client attempts to disconnect from a connection that is already closing

​Why it isn't "the other way around"
​If NetworkShutdown was called specifically when the IDs matched, every time a remote player left your lobby, your entire game's network stack would crash or close, booting you to the main menu.
​By only triggering the shutdown logic when the ID does not match, the system ensures it is only reacting to external peer changes while keeping the local connection alive.

This is from my Gemini advanced model that I pay for. So take it as you will. I am only trying to help you out if possible.