save-load-netcode

To enforce server-authority save and load in Unity multiplayer, wrap all world save I/O in an IsServer check and route client save requests through a ServerRpc, ensuring the host governs persistence and prevents desyncs.

Clients desync during multiplayer save and load when they are allowed to directly perform disk I/O. Prevent this by enforcing host-controlled persistence where the server coordinates SaveWorldAsync calls and synchronizes network profiles on join.

Yes, this server-authoritative save approach applies specifically to client-server Unity projects using NGO 2.10, ensuring the server governs disk I/O, synchronization, and reconnection profiles.

To trigger a save from a client in a server-authoritative multiplayer session, the client must invoke a save request via a ServerRpc, which prompts the host to execute the actual SaveWorldAsync disk operation.

The best way to handle player profile loading during multiplayer reconnection is to drive it through server-side state synchronization, applying network-synced profiles on join rather than client-side loading.

You should not allow clients to execute save commands directly in multiplayer when strict server authority is required, as client-side disk I/O leads to world state desyncs and opens the game to cheating.