1 Answer
- Newest
- Most votes
- Most comments
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.
answered a year ago
Relevant content
- asked 6 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 3 years ago
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.