I have a conundrum... So I allow the player to change avatar picture. When doing this it saves an index to player data. When the player chooses an avatar too much too fast it doesn't save because PlayFab limits saves. So then next time they log in, it is not the newest avatar they chose. What do I do about this?
You are not supposed to update player data very often, which will hit the rate limit. It's recommended to cache player data changes locally and update them periodically, or when application exits.
This kinda makes sense... I still don't totally understand why there is a limit :)
I am not sure What the issue is and why you are saving an index in player data but here's what I do.
I Use the Playfabs UpdateAvatarUrl call to update my Player's avatar.
After The Player updates the Avatar I add a cool down timer, 1 hour( depends) , and make the button interactable= false for an hour ( to optimize the calls made to playfab server).
void Start()
{
if(currentTime > timeSinceLastUpdatedAvatar+ 1 hour)
{
//Unfreeze The UdpateAvatarButton
}
else
{
//Freeze The UdpateAvatarButton
}
}
void UpdateAvatar(){
if(currentTime > timeSinceLastUpdatedAvatar+ 1 hour) {
PlayFabClientAPI.UpdateAvatarUrl(new UpdateAvatarUrlRequest
{
ImageUrl = AvatarUrl_forPlayfab
}, result =>
{
Debug.Log("Avatar Updated. New avatar is:"+ AvatarUrl_forPlayfab);
//Freeze The UdpateAvatarButton
}, error => {
Debug.Log("Avatar Update Failed");
}
}
}
4 People are following this question.
