Additive sceneloading sceneid fix

[paulpach]

No description provided.

[miwarnec]

this was the bug report: #72

[MrGadget1024]

I don't think it fixed the problem?

[paulpach]

hang in there vis, I still want to take a look at this one

[miwarnec]

so all that was left was making preparetospawn public? that's weird

[miwarnec]

also, I made this comment on the issue last time:

'I need to get some sleep for now. This might work if you try it @MrGadget1024 , but we can't merge it yet because OnPostProcessScene -> setactive(false) -> ondisable -> spawnableObjects.add would add sceneids from objects that are not in the starter scene, which means that there would be problems if someone tries to spawn them even though the extra scene isn't loaded. or perhaps not.'

will have to look into that again

[paulpach]

@vis2k After a client loads/unloads a scene, he needs to call:

NetworkClient.PrepareToSpawnSceneObjects();

which is why this is public.

After a server loads/unloads a scene, we need to call

NetworkServer.SpawnObjects();

Those changes + this pull request = additive scene loading works

[MrGadget1024]

if NetworkClient.PrepareToSpawnSceneObjects(); and NetworkServer.SpawnObjects(); need to be called after unloading a child scene, perhaps these methods need better names? Not very intuitive as they are.

[miwarnec]

@MrGadget1024 if you have an idea for better names then please open another issue/pr

[miwarnec]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀