Answer by Brendan · Feb 09 at 06:38 AM
No, new game session servers aren't automatically set up with any specific tags - only the call to SetGameServerInstanceTags can set those up right now. That certainly does seem like a good addition to the StartGame call, at least, so I'll add a backlog item for that. I can't say when we'll be able to prioritize that work item though, so for now I would recommend using SetGameServerInstanceTags. One thing you could do would be to have a second server build that you use as a "lobby" of sorts for players waiting on game sessions. You could have all players matchmake to that server type, and then have it start the game sessions and apply the tags.
Answer by rob · Feb 15 at 05:11 PM
+1 to being able to set tags in StartGame. Our game has a lot of options that you can choose before creating a new game which would like to be able to display to users calling PlayFabClientAPI.GetCurrentGames. I haven't got very far on this yet but I'm assuming tags are the best way to do this?
Answer by webmaster · Feb 15 at 08:00 PM
Brendan - Here is another work around, want to see if you think this would work.
In situations where we there isn't a game server existing with a particular tag, what if we somehow tell the 1st client to start the server, then once the server has started, have that 1st client tell the server to call SetGameServerInstanceTags(). The 2nd client would basically wait a bit then poll the matchmaker for a server with that tag? But the 2nd client wouldn't start a new server.
If say the 2nd client tried 2~3 times and couldn't matchmake into the server with the tag, then we assume somehow that server wasn't started properly, and the 2nd client would basically fail matchmake.