Hello!
I Am currently implementing multiplayer with PlayFab Party and players should be able to join a specific Game based on the networkId provided by party.
The problem is that the networkId is very long, and certain rich presence services only allows a maximum of 128 characters to provide your game credentials so other can join you.
I'm looking into a solution where a client can execute a cloudscript that takes the networkId as input, and gives back a ~9 character gameId which can be used by players to join the game.
This "Map" of course needs to be:
* Persistant, gameId <> networkId pairs should be alive as long as the network exists.
* Scaleable
* Maintainable, remove networkIds that has existed for more than x amount of time.
When scrummimg through the Playfab Universe most data seems to either be tied to Players, or the Title, where title data is not meant to be updated regurarily.
This data wouldn't make sense to tie to a player either, since then the one joining would need to know the PlayerId rather than the GameId.
My question is:
Have I overlooked any service that fits the criteria above? Or would it be better to use some other service like Azure Tables to keep track of this "living map"?
