The QoS SDK’s GetSortedMultiplayQosResultsAsync currently takes fleet IDs, requiring developers to fetch the appropriate fleet IDs for the current environment that the app is configured for.
Ideally this would instead take queue names, similar to CreateTicketAsync, and then let the backend resolve which fleets are used and need queries based on the provided queues. The queue names are already something clients will know about for matchmaking requests and would make integration much simpler.
Alternatively but not as good would even just taking fleet names to prevent needing to manually resolve IDs per environment, but frankly it’s a bit odd even having clients have any knowledge of anything regarding fleets- it’s a concept that client code shouldn’t have to be aware of or care about.