Hello, I believe this might be a combination of issues. Could you please review the sample’s log output to see if you’re encountering any errors on either of the instances?
I suspect the issue is that you’re using a client policy without the matchmaking:managePlayers permission.
This means that Player A is probably failing to register Player B to the session, which is causing the player count to remain at 1/4.
For Player B, the reason for the discrepancy is that remote clients who join a session will have their own local view of the session, and this view does not automatically receive data updates about the back-end version.
Mirroring the API calls, outlined in the documentation linked below, is not required, but it can be beneficial for remote clients to keep their local view in sync with the back-end session.
You will need to use the game’s own networking to manage this.