question

Simply choosing a different reset schedule will not allow players to compete on the same daily leaderboard in their local time zone, since at any given time players in different time zones will be competing on a different version of the leaderboard.

For example, it might be either the 15th, 16th, or 17th day of March for you right now, depending on your time zone. So at any given time, there must be 3 active (writeable) versions of a daily leaderboard.

Since only one version of the Playfab leaderboards is writeable, 3 separate leaderboards (i.e., with different statistic names) are required to build this feature.

I was able to implement this feature by creating 3 leaderboards and resetting them on a staggered 3-day schedule, such that any given instance of the leaderboard is active for 3 days.

Unfortunately, Playfab cannot be configured to reset a leaderboard every 3 days, and cron does not support this type of schedule, either, so none of the recommendations for resetting the leaderboards are viable. (Also note that Cloudscript does not support Admin API calls, so can't be used for this purpose, either.)

I was able to solve the reset problem by creating an Azure WebJob that runs every 24 hours and resets the next leaderboard in the staggered rotation. I found the WebJob to be much simpler and more appropriate for this task than the Azure Function recommended in the documentation.

I also used this same pattern to create a weekly leaderboard that starts and ends in the player's local time zone using only two leaderboards that are reset on a staggered 14-day schedule (so reset one of the leaderboards every 7 days).

I used the same WebJob that runs every 24 hours to reset the appropriate leaderboards depending on the number of days since a base date mod 3 for daily leaderboards and the week since a base date mod 2 for the weekly leaderboards.

The final step was to use local time in the game to determine which leaderboard the player should access. For the daily leaderboards this is the leaderboard that was reset the day before, and for the weekly leaderboards it is the leaderboard reset the week before.

So it's not trivial, but with multiple instances of each leaderboard and some tricky date calculations in your game and WebJob I'm happy to say it's possible to workaround the Playfab leaderboard limitations and create a great player experience for leaderboards shared across time zones.