Best Of

Well to be honest I'm after similar answers myself on the forum. What I have found so far.

Each object on the map that will need updating will require its own pun mono class to control how it will sync on the network.

As such I'm leaning to believe your map should not stream itself more than once.

What you will likely need is a RPC call to tell the server to pass the seed to the joining client. It should then be able to recreate the map itself. Using the seed and the same method used by the host. (This is my understanding of seeding a procedural map.)

If your map is a true random even with your seed value. Then you would have to stream its contents at the start to all players. Since lag and other things can bog down how quickly a player receives the map data. You also likely will have to have all players waiting until all have loaded the map and finished building it. Then start your game logic of starter base placement and let the players go.

Buildings and units should have their own network view. With their own script to stream as they will be moving and need to be synced to all players. Spawning them though again will likely need to happen in a RPC to spawn your prefab. Then set its owner, controls, and other setup requirements. It will have a pun mono to stream its position. Using the photon spawn method. All players will have the unit spawned when this is called. When the server runs the RPC to spawn. The network view scripting takes over on the object itself.

The part I seem to be stuck on myself is how to choose specific clients to send updates to on spawn. Without streaming them again until certain conditions are met. In the sense that I need to spawn units without the enemy player seeing them. At least until they are at the same location.

I updated our encryption doc and it will be up within the next days here:
https://doc.photonengine.com/en-us/pun/current/reference/encryption

This gets clarified:

In PUN, you can send RPCs and events with encryption on demand. The frequent and regular updates for networked objects, are not encrypted.

To call an RPCs in a secure way, use RpcSecure() on any PhotonView.

PhotonNetwork.RaiseEvent() can be used to send custom events with or without encryption.

In both cases, the server will decrypt the message and re-encrypt it to send it the other players. A Server Plugin could make use of the data, read or change it.

When an operation is sent encrypted, any data you send and all operation paramters are serialized and then encrypted. A lean header per message (length, etc.) remains unencrypted.



Hope that helps.