1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
When the number of players whose player session status is TIMEDOUT, COMPLETED reaches maxPlayers count, the player can no longer participate in that session. How can I fix it?
Use RemovePlayerSession() to remove a player from a game session.
When the game is over, change the PlayerSessionCreationPolicy for the session to ‘ACCEPT_ALL’ to allow new players to enter.
Are you trying to reuse a game session for multiple matches? We suggest that one game session per match, that's how FlexMatch is designed with.
con risposta un anno fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata un anno fa
Thanks for your answer! After changing the player status of Reserved status to Active through AcceptPlayerSession(), RemovePlayerSession() is being called when the player's session is disconnected. If I call RemovePlayerSession(), is it correct that the Player status is changed to COMPLETED without any additional work, and a new player can enter Matchmaking in the empty slot? Even if I call RemovePlayerSession() and change the player status to COMPLETED, Matchmaking will no longer put it in the vacancy.