question

1. Any PlayFab Client API will require session ticket or entity token in the header for verification. Only login related API doesn’t require one, which means clients cannot access any PlayFab service without login. Simply set the property “CreateAccount” as false in the request of Login API should do the job. If the account is not existed, failure callback will be returned. Please note that if CreateAccount is set as True, PlayFab will automatically create new account if it is not existed.

In addition, the callback result of login API will contain a property "NewlyCreated", which indicates if this login call has created a new account.

The login identity will be linked to the account on PlayFab. You may store a local copy of the login information in the devices. However, we recommend linking a recoverable login method. PlayFab documentation website provide a detailed explanation on authentication: https://docs.microsoft.com/en-us/gaming/playfab/features/authentication/login/

2. Yes

3. Yes. You may also use Rules with Cloud Script to do the setup job automatically for players. When a title player account is created, PlayStream Event "player_added_title" will be generated, which can be used as a trigger of Rule, to execute Cloud Script for initialization. In the script function, pre-defined varibale "currentPlayerId" can be used to get the target player's ID.

4. There are many resources on PlayFab for data storage. For example.

• Title Data. Client API can only read it. Only Server/Admin API has the permission to update. It is shared globally.
• Player Data. There are 3 types of Player Data, which are Player Data, Player Read-Only Data, Player Internal Data. Client API will have the permission of read/write on Player Data. The other 2 will need Server/Admin API. All of them have a permission to set it public/private. Basically other players can get those public data as long as they keep a PlayFab ID. You may see there are 2 tabs in Player's page of Game Manager. For Player Data (title), all the belonging data is title-specific, meanwhile for Player Data (Publisher), it can be shared between titles (but must be within the same studio). it is because a Master Player Account is shared between titles within the same studio. Players are able to login in different titles within the same studio via the same identity and Player Data (Publisher) is the shared data in the studio.
• Objects. It belongs to the new Entity Data Model, the use scenario is similar to Player Data but controlled by the Entity Policy. The Read/Write permission can be modified. In some scenarios, small group of players can modify one Object, like Group Objects. However, please understand that you shouldn't use any resources for multiple read and write at a short time. If it is required, you may consider using external database, like Redis.