Hello, We have just migrated to the Play Fab as our Online Game Service.
I do have some Questions regarding the Live Operation Aspect on Play Fab.
Game Version: It seems that the Title Data would be a good place to Store the Current Game Client Version so the Clients can Verify with this value and Display the Message to the Players to Restart and Update the Game Client but it Seems that the Title Data is not Meant for frequent changes. So what would be the best way to approach this?
Maintenance Mode: This might be similar to the Game Version case , But What would be the best place to store Live Ops configuration data/variables that are to be changed when Pushing Updates or Maintenance . Such as Maintenance Mode, Disabling Matchmaking? (I Understand we can Disable Client API Request Access but that Disabled complete Access such as Authentication which is not desirable )
Thanks in Advance.
Answer by Citrus Yan · Jun 23, 2020 at 06:21 AM
Title Data is a sharded and cached resource, which can take a while (up to fifteen minutes ) to be fully updated to all shards based on the size of the data. In your case, the data size updated should be quite small and so does the update frequency, therefore it should be fine for you to approach this based on your real-world scenario.
Title Data is also the proper place to store Live Ops configuration data/variables, and, you can check out the tutorial on API access policy to learn how to disable certain APIs at your demand.
Answer by Rima · Jun 23, 2020 at 07:03 AM
Hi @Citrus Yan,
Alright it make sense now. Seems like a good solution and plan for us.
Thank you for your response and the link.
How to handle changes to a large number of users,Handling large batch operations 1 Answer
Differents Titles Enviroments (single game) 1 Answer
Cloudscript + Azure Functions + Redis 1 Answer
Is the limit of Titla data just 1 MB? 1 Answer
What is the name of the data point relating to a user's session? 1 Answer