I was able to reproduce the error, however there were no crashes. Did you use the "Error Pause" or stop on exception options maybe?

The issue is actually within Photon and was fixed some time ago, but now occurs again:

https://forum.unity.com/threads/operation-set-252-not-called-because-client-is-not-connected-and-i-have-one-more-problem.887458/
https://forum.photonengine.com/discussion/15862/operation-setproperties-252-not-allowed-on-current-server-masterserver-on-demo

The fix is to implement the OnLeftRoom callback for the scene change. In the UIGame script, scroll down to the end and do the following changes:

public void Restart() { ... Disconnect(); //instead of Quit(); } public void Disconnect() { ... //comment out Quit(); } public override void OnLeftRoom() //rename Quit method to this callback { ... }

@habeeb22
solved
in GameManager

private void Start() { if (PhotonNetwork.IsMasterClient) { NetworkManagerCustom.GetInstance().addPlayerthis(); } }

in NetworkManagerCustom

public void addPlayerthis() { foreach (var playerrr in PhotonNetwork.PlayerList) //loop through each player and spawn a player { this.photonView.RPC("AddPlayer", playerrr); } public override void OnJoinedRoom() { //we've joined a finished room, disconnect immediately if (GameManager.GetInstance() != null && GameManager.GetInstance().IsGameOver()) { PhotonNetwork.Disconnect(); return; } if (!PhotonNetwork.IsMasterClient) return; //add ourselves to the game. This is only called for the master client //because other clients will trigger the OnPhotonPlayerConnected callback directly //StartCoroutine(WaitForSceneChange()); addMyself(); } void addMyself() { //I connected My selve OnPlayerEnteredRoom(PhotonNetwork.LocalPlayer); }

hope it will help if any one needed
Thanks
Habib

I was just about to refer to a similar question regarding Mirror's headless build option, in case you were using that (it doesn't sound like it):
https://flobuk.com/forum/post/11928

I'm glad you figured it out!

@baron Thank you I Thank I will be fine now since nothing is broken at the moment.

In Mirror, that's where the List Server comes into play. With the NetworkListServer component, games created are added to the List Server for others to join. There is no visual list of rooms though - that's a design decision I made for this asset: one button to play, basically to comply with mobile practices. If there is a room available for the selected game mode, other users will join it randomly.

More information on this is on page 16 in the documentation pdf. I just tried to open the Mirror website again, but now the whole website is currently offline.

The Photon implementation works the same, however without the need of a separate List Server.

Currently preparing an update for submission to the Asset Store. It should be available later today.

Upon testing, points 1 & 2 & 3 did not occur anymore on 10/10 game launches.

I discovered a rare issue with the device log getting spammed and a Socket exception, where the causing line is in the Mirror code itself. I hope you understand that I am not able to deliver fixes in Mirror within the asset, but if you run into that, the following if-catches should be added in the NetworkDiscoveryBase script.

async Task ReceiveGameBroadcastAsync(UdpClient udpClient) { // only proceed if there is available data in network buffer, or otherwise Receive() will block // average time for UdpClient.Available : 10 us if (udpClient == null) return; if (udpClient.ReceiveAsync() == null) return; //...

@baron @baron Ah, ok so it was a design choice when restarting from the end game menu to effectively quit and find another game (possibly with someone else)?! Weird as this could be achieved by the player by hitting quit + play. In my mind "Restart" means starting a new game with the same players.

Thanks for the repro steps. I was able to reproduce this using the latest Mirror Asset Store release, 30.2.2.

after they connect, exit one of them => both are brought to the main menu

Just a note on that part - this only happens if you disconnect the master client hosting the game. Disconnecting a client does not stop the master from continuing playing.

In the OnClientDisconnect method in the NetworkManagerCustom script, I tried adding a "hard" disconnect using StopHost() like this:

//switch from the online to the offline scene after connection is closed if (!NetworkManager.IsSceneActive(offlineScene)) { StopHost(); SceneManager.LoadScene(offlineScene); } else CreateMatch();

When testing, 10 out of 10 times the issue you mentioned did not occur anymore. However there was a rare issue when starting a game on both applications at the same time, both clients would think they are the master, but actually land in the same room. Please let me know if you experience that issue at some point. Usually, this should not happen as you would not try to start multiple instances as a host on the same device.

Are they stacked on top of each other? I.e. maybe their colliders overlap so only one can move at a time?

Could you provide steps to reproduce this in one of the example scenes?

Side note: the bot logic is very simple, their first target position is indeed the center of the map. However if they encounter enemies on their way, they will try to chase them and move to a random position around their target, or a spawn location of one of the other teams.

@baron thanks for the speedy replies anyways. I'm a bit ashamed I missed that, and of how long I looked for it...

@Baroni Thank you very much, for both the reply and the excellent asset.

Great, thanks for posting. It could have still taken a few days until my update gets approved on the Asset Store.

There is actually a sample on the official PUN docs for just that:

https://doc.photonengine.com/en-us/pun/current/lobby-and-matchmaking/matchmaking-and-lobby#play_with_your_friends

As mentioned on that page, have your button call PhotonNetwork.JoinOrCreateRoom with a room ID that can be shared with other people.

Thank you for responding so quickly—your answer work.