Unet problems when scenes aren't exactly the same

It seems Unet breaks when i have a host and client with two scenes that are even slightly different - for instance, if there's a seemingly minor bug fix on the server's copy of the scene. Is this expected? If so, are there best practices for dealing with this?

If it's not just a bug I can fix, I'm planning to go the route of telling users that they have to match agme versions (if those 2 version had a change in the multiplayer scene they want to play).

 

You need exactly the same scene because HLAPI assigns sceneIDs to NetworkBehaviours in the scene.
If they have different ids then bad things will happen

Note that there is a sceneId 'matching' bug anyway. So even if you have the same scene, you will still get errors. See HLAPI Pro (signature) for a fix.

 

Thanks! Yep, I used HLAPI Pro for mine for this very reason, thank you!!

In your games, do you simply have to require people have the same version?

 

Crazy idea - and it's probably not this simple - but could a public field be added to NetworkIdentity to generate a static unique sceneID in the editor?

 

Yes.