Question NetworkManager's Player Prefab is being destroyed on Scene Loading on the Client

So, I'm experiencing this issue where the player prefabs get destroyed on the client side even when they got a "Don't Destroy on Load" script attached to them:

Code (CSharp):

1. public class DontDestroyOnLoad : MonoBehaviour
2.     {
3.         void Awake()
4.         {
5.             DontDestroyOnLoad(gameObject);
6.         }
7.     }

The weird thing is that it was working fine so far, I've tested it like 100 times over the course of 2 weeks, and they never got destroyed till now.



I've tried toggling on and off this parameter on the "NetworkObject" to see if that helps, but the outcome is the same.

 

Check the callstack of the first error message and see where in your own code (if any) this call originates from. Check any script that may attempt to destroy the player prefab instance.

Do you spawn player prefabs manually?
Do you use NetworkSceneManager to change scenes?
Do you perhaps call StartClient() and then perform a scene change on the client side? When a client connects, it will automatically load the scene the server is running.

 

I got this Stack Trace activated, but I got no more info than the one that shows here:

 

No, it's done automatically.

Yes, I do it from the Server/Host

So, in theory the "NetworkSceneManager.LoadScene" is called from a function with this [ServerRpc(RequireOwnership = false)], and solely gets triggered only when all clients are ready (so it's called only once). Also, before using the "NetworkSceneManager.LoadScene" there is an if statement:

Code (CSharp):

1. if (IsServer && NetworkManager.IsListening)
2.             {
3.                 if (_gameSceneName == null)
4.                 {
5.                     Net.LogError("NetworkSceneLoader has no on-demand scene assigned");
6.                     return;
7.                 }
8.              
9.                 Net.LogInfo($"Try load scene: {_gameSceneName}");
10.                 var status = NetworkManager.SceneManager?.LoadScene(_gameSceneName, LoadSceneMode.Single);
11.                 if (status != SceneEventProgressStatus.Started)
12.                     Net.LogWarning($"Failed to load Scene '{_gameSceneName}' => {status}");
13.             }

So, only the server would be able to use the scene loading

 

Does anyone have any idea?

 

Hi, thanks for replying.

The version I'm using is the 1.0.2

None of my scripts do that. But just to make sure, I tried and find the word "destroy" on the entire solution, and indeed, none of my scripts are calling a destroy. It started to happen yesterday for the first time, but I tested the project a bunch of times prior and everything went as expected. It happens on the client (on the editor) after loading the scene on the host (and not always: from yesterday I believe it happens around 95% of the time).

EDIT: It appears to happen only on the editor. If I host on the editor and join as a client on a build, the error doesn't show up (thus the player prefabs are not getting destroyed). This only happens if there are a host and a client, and the client is being played on the editor.
But it's even weirder the fact that if I use 2 clients and a host, say, build 1 hosting, build 2 as client 1, and the editor as client 2, then the error doesn't show up.

 

Do I have to update it from the website? If I remove it, will it produce any incompatibility with my existing netcode's objects?

I checked the history of the source control but I haven't seen anything suspicious.

 

This is weird. My Unity version is this one:

 

Hi, today I tried a couple of times and it seems to be working: the prefabs didn't get destroyed. However, it also worked yesterday until it didn't. Unfortunately, I'm afraid I can't be of help in order to track the bug since I don't have any clue of what the cause might be...

If the problem disappears completely or I'm able to track the bug I'll let you know for sure.

PS: I couldn't test it on 1.1.0 because I have no access to this version, so the update on the situation is on the 1.0.2 version, which might not be helpful.

Anyway, thanks for helping!