MasterClient switch behavior when client.disconnect() is called with a room with a non zero TTL
in Native
Hello,
This question is about the demo_iPhone_loadBalancing_swift demo. When I do the following :
1. Device A (player number 1) creates room with the following room options (note the non zero TTL)
3. Device A calls client.disconnect().
Device B has leaveRoomEventAction called. When I check for the master client like so :
I get :
I was expecting the masterClientID to have changed to 2 even with a non zero TTL. It appears that the master client didn’t switch. Is this the expected behavior?
If yes, are there any Photon configuration settings that I can set to permit the masterClientID change before the time out?
Thanks,
This question is about the demo_iPhone_loadBalancing_swift demo. When I do the following :
1. Device A (player number 1) creates room with the following room options (note the non zero TTL)
let options = EGRoomOptions(true, true, 0, nil, nil, "lobbyName", EGLobbyType_DEFAULT, 2 * 60 * 1000)2. Device B (player number 2) joins room
3. Device A calls client.disconnect().
Device B has leaveRoomEventAction called. When I check for the master client like so :
let masterID = networkLogic.client.currentlyJoinedRoom.masterClientID self.demoView.log(String(format: "masterID : %d", masterID))
I get :
masterID : 1
I was expecting the masterClientID to have changed to 2 even with a non zero TTL. It appears that the master client didn’t switch. Is this the expected behavior?
If yes, are there any Photon configuration settings that I can set to permit the masterClientID change before the time out?
Thanks,
0
Best Answer
-
Hi @GreenRollingHills.
Yes, this is expected behavior.
No, there are no config settings that you can set to change this behavior.
Changing the master client to a different player when the current one becomes inactive simply is a feature that is not supported in the objective C client right now.5
Answers
-
Hi @GreenRollingHills.
Yes, this is expected behavior.
No, there are no config settings that you can set to change this behavior.
Changing the master client to a different player when the current one becomes inactive simply is a feature that is not supported in the objective C client right now.5