Best Of

The approach is not optimal, as the sender now has to send a lot of individual messages (one per player who should get the RPC).

For a simplistic interest management, you can use the Interest Groups. You divide the world into groups and players only subscribe to groups to which they are close-by.

https://doc.photonengine.com/en-US/pun/current/gameplay/interestgroups/


Using RPCs can be replaced with RaiseEvent, which is not PhotonView related. That may be a benefit, too.

https://doc.photonengine.com/en-us/pun/v2/gameplay/rpcsandraiseevent

Just override OnPlayerLeftRoom method inside that check for win condition. T

public override void OnPlayerLeftRoom(Player otherPlayer)
        {
			CheckWinCondition ();
   
        }

@UniquelyTama9 I think how I've set mine up may help. In my multiplayer rooms, each player has a team color, 'faction' they're playing as, their username, and their rank. Whenever any of this changes, the request goes to the master client, and then he processes it, and then the master client sends out what is on his screen to everybody else. So I think I've how done that is similar to how you need to sync your cards across every player's screen.

I put the players' data into an object[16]. Then I call an RPC, putting that object into the RPC, and send it to everyone else. Then they 'unpackage' that object and use it to update their screen. Here is what the master client sends:

public void SendFullRoomStatus()
    {
        object[] playersdata = new object[16];

        int x = 0;
        foreach (var e in playersInRoom) {
            playersdata[x] = e.userID;
            x++;
            playersdata[x] = e.team;
            x++;
            playersdata[x] = e.government;
            x++;
            playersdata[x] = e.Rank;
            x++;
        }

        photonView.RPC("UpdateRoom", RpcTarget.All, playersdata);
    }

And here is what the receivers do with it:

[PunRPC]
    void UpdateRoom(object[] RoomStatus)
    {
        playersInRoom.Clear();

        for(int i = 0; i <= 12; i += 4) {
            if (RoomStatus[i] != null) {
                PlayerInRoom newPlayer = new PlayerInRoom() {
                    userID = RoomStatus[i].ToString(),
                    team = (Team)RoomStatus[i + 1],
                    government = (Government)RoomStatus[i + 2],
                    Rank = (int)RoomStatus[i + 3]
                };
                playersInRoom.Add(newPlayer);
            }
        }

        UpdateUI();   
    }

So if I'm reading your post right, you need to take all of the information about each card, put it into an object, and pass that object into the RPC. As you can see, my multiplayer rooms have 4 players, and 4 attributes for each player, which ends up being 16 pieces of data that need to be sent. Similarly, if you have 52 cards, and just one piece of information about each (the 'value'), you can make an object[52] and put in all of that information. The other players can unpackage that object and use it to make sure their cards are shuffled similarly as well.

Tobias thank you very much. This was indeed the issue and setting PhotonNetwork.AutomaticallySyncScene = true fixed the issue.

This could be due to the Master Client knowing views that this player doesn't know yet.
Do you use PUN's built in scene synchronization? Or do you at least pause dispatching incoming messages while you load the scene?
Refer to Switching Scenes.

This could be due to the Master Client knowing views that this player doesn't know yet.
Do you use PUN's built in scene synchronization? Or do you at least pause dispatching incoming messages while you load the scene?
Refer to Switching Scenes.

when i connect (as master of server) the list appears with my name, when a second user joins it will dissapear for both users and cause arrors

when i leave on the master account and the other user becomes the new master, they can see the player list and it has the names of both players even though i already left

im using the default worker scene and the script is attached to the scripts object (same as the chat) and added to its photon view script
https://i.imgur.com/uqddaOw.png

heres the code
https://pastebin.com/VuCZaB84

Calling the RPC for All will execute it locally on the client which called initially. AllViaServer can be used to get about the same delay for everyone's execution (which can be crucial for some things, ofc).
This and related info is mentioned on the doc page about RPCs and RaiseEvent.