What do you want to see in the API?
The structure of how the match type is handled has changed on clientside. Previously there was only one field that handled the matchmaking type (Clan2v2, Random2v2 ect.) Now there however is a second field that contains the actual game mode that the players are setting up to go and play.
This new GameType field should thus be added to the handling so that this can be properly delivered between players.
How do you think this should work?
Add GameType field to the MatchData field (or whatever its actually called). (It can be integer/Enum, however since the se can be in somewhat rapid flux on the client side due to testing different things integer is likely easier.)
Room creation endpoint should also take this GameType data to determine what it actually is.
RoomData updates over the MQTT should also include this new GameType field.
What do you want to see in the API?
The structure of how the match type is handled has changed on clientside. Previously there was only one field that handled the matchmaking type (Clan2v2, Random2v2 ect.) Now there however is a second field that contains the actual game mode that the players are setting up to go and play.
This new GameType field should thus be added to the handling so that this can be properly delivered between players.
How do you think this should work?
Add GameType field to the MatchData field (or whatever its actually called). (It can be integer/Enum, however since the se can be in somewhat rapid flux on the client side due to testing different things integer is likely easier.)
Room creation endpoint should also take this GameType data to determine what it actually is.
RoomData updates over the MQTT should also include this new GameType field.