-2
\$\begingroup\$

I started using PlayFab. Could someone help me and explain with small example for what to use Player Data (Title), and Player Data (Publisher), and for what not to use?

\$\endgroup\$
3
  • 1
    \$\begingroup\$ Searching the PlayFab documentation for those terms brings up tutorials & quickstart info. If that info isn't helping to resolve your problem, you probably need more info in your question explaining what you've tried & what specific issues you encountered. \$\endgroup\$
    – Pikalek
    Jul 31 at 18:15
  • \$\begingroup\$ I see both are the same. So, what are they specific for? At less give me an example. Unfortunately, their forum is bad. \$\endgroup\$
    – user43474
    Jul 31 at 18:26
  • \$\begingroup\$ from the docs: Player Publisher data is data associated with the player account, as opposed to the player account plus the title. It is used to save information about a player relevant to all titles in your studio (which may also contain title-specific information, for purposes of cross-title rewards). \$\endgroup\$
    – Pikalek
    Aug 1 at 0:49

1 Answer 1

1
\$\begingroup\$

First, it might be good to clarify the difference between player data & player publisher data:

Player data is player information that is specific to a game title. It should be used for title-specific information - such as saving your player's position in a dungeon, or other game-specific data.

Player Publisher data is data associated with the player account, as opposed to the player account plus the title. It is used to save information about a player relevant to all titles in your studio (which may also contain title-specific information, for purposes of cross-title rewards).

And as noted later on:

They are both dictionaries mapping a string to a JSON blob (or other arbitrary string value).

Based on your question usage, it seems like you are asking about player data called title & publisher. Based on the documentation, that means for some game XYZ, you would use those mappings to store the title for XYZ and the publisher for XYZ. Sometimes these are referred to in the documentation as Key/Value Pairs or KVPs.

The definition for player data says it hold game title specific information such as the player's position. But there could be more than one game that uses player position. As mentioned here in the documentation, the title establishes the current scope, which is to say makes sure that you are referring to the data for the intended game.

That same documentation also explains that the publisher field is used for managing account data across several titles. For example, if a publisher has multiple games, they might want to encourage players of one title to purchase & play your other titles. In that case you could grant a reward for playing multiple titles. By consistently using the publisher KVP, you can more easily query for the necessary information to see if a reward should be given. The documentation also gives a link to an example project using simple in-game cross promotion where players get rewarded for participating in more than one of your games.

\$\endgroup\$

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .