According to the documentation, a SessionId is a guid (globally unique identifier)
See RequestMultiplayerServer()
However, when we call GetMatch() we need to also pass in the QueueName in addition to the Match Id (which is equivalent to the SessionId)
What's the point of having a guid if you can't use it to uniquely identify something?
I think it's because RequestMultiplayerServer() isn't always used with matchmaking, so the Session ID isn't always a Match ID unless the server was allocated by the Matchmaker or you've requested the server and given it a Session ID equal to an existing Match ID. Furthermore, servers that haven't yet been assigned to a match have no Session ID, so there is the potential in both of these cases where you could call GetMatch() with an empty string.
Hmm, I think I sort of follow. I understand now that RequestMultiplayerServer() isn't always used with matchmaking, therefore it won't always have a MatchId and therefore GetMatch() wouldn't make sense in that case.
However, for matches that are matchmade, I'm trying to understand what use-case there is where you would have two sessions simultaneously with the same MatchId/SessionId. Can you describe a case like that? Otherwise I still don't understand why GetMatch() can't be called with just a SessionId.
Even when we use RequestMultiplayerServer(), we also need to provide buildId and seesionId to determine one session. SessionId should be created by the game developer, the same sessionId can be used to two builds. So, when we call GetMatch(), we also need to pass the queue name.
I understand this is the API specification, but can you describe a "real world" situation where you'd want to use the same sessionId for two builds? I don't understand.
5 People are following this question.
