Constant/Static Data vs Global Variables

[pjcard]

"is best suited for Global Constant/Static Data and is not suitable or reliable as Global Variables."

This seems like an important warning, but it is very unclear to me what it means. If a global value were truly constant, what point would there be in putting it into title data? Can you explain what you mean? What use case did you intend for Title Data to serve?

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 784f614b-e71e-1c6e-ba9c-c0fa5aee784c
• Version Independent ID: 30842519-a9a9-1ee2-be48-3cb5ec95c0f6
• Content: Title Data - PlayFab
• Content Source: playfab-docs/features/data/titledata/index.md
• Product: playfab
• GitHub Login: @shikha-tarware
• Microsoft Alias: shtarwar

[RonaldHarding]

This is the updated location of the content https://learn.microsoft.com/en-us/gaming/playfab/live-service-management/game-configuration/titledata/

This looks like good feedback to me, it's not my area but my understanding is that title data should be items that change as a matter of configuration not variables. That is to say, you don't want to have them updating in response to user activity on their own. It'll take a while for updates to propagate and the behavior will become undefined. Rather, title data is to be used for cases where you the developer are making changes to config. Off the top of my head here are some examples of good uses of title data:

• Enabling a feature flag that lights up a new world in your game for all players at approximately the same time
• Swapping out the weekly challenges that your azure functions/clients check against for player completion
• A schedule for events that is consumed by the client to change the interface in a pleasing way

I'll see if I can track someone down to put better wording here.