My view is that there should be a "guaranteed service availability" at the time of purchase not unlike buying an appliance with a year warranty..

Pull the game from stores and let the remaining players enjoy the sunset.
Of course it's not always as simple as "just keep the lights on longer" but a guaranteed period of availability which is tied to new purchases should be in your plans before your service ever reaches the public, rather than hoping to grab as much money as possible before dumping it and throwing the consumer under the bus.

And... the upgrade is complete.

Hopefully a non-event for everyone!

Reach out to support if you see any weirdness!

Cheers,

Paul.

Oh - and one thing that wasn't in the release notes... we bumped up the Design Portal session timeout -- so if you go away from the portal and come back to it later -- there's a better chance that you can pick up from where you left off (instead of being booted and having to re-login).

Ah! Thanks for letting us know!

@JasonL
Thank you for the info, much appreciated!

Okay - cool!

สวัสดี ต้องขออภัย แต่เราให้บริการช่วยเหลือเป็นภาษาอังกฤษเท่านั้น

[Hi. Apologies - but we only provide support in English.]

You can schedule a recurring daily cloud code script to run after the completion of your daily tournament. This script will use the GetGlobalLeaderboardPage method to retrieve the daily tournament winner's information and score, then post it to the monthly tournament using the PostTournamentScoreOnBehalfOf method.

We agree with that @antony - we'll get that request to the devs.

Hi folks,

FYI, here's one minor update regarding the Retention Analytics screen:

We have changed it to show Classic retention by default.

The reason for the change is that Rolling Retention naturally trends downward over the 30-day period of the report. That's simply due to mathematics. Rolling retention for a particular day measures whether the user returns that day - or any day thereafter. Thus - the days at the end of the calendar period have fewer days after them - and so the stat will naturally be lower.

We don't want folks to mistakenly think their retention is trending down - so we're now defaulting to Classic Retention which is more deterministic over the 30 day period. For those who wish to view the Rolling Retention - it's just a mouse click away!

Cheers!

Paul.

thx, I will give it a try

Thank you for sharing this information. It does not have an impact on our server-side validation.

Update - we've confirmed with the server team that we believe we are all set.

We'll perform some tests when the Sandbox servers cut over the week of Jan 20th to confirm.

Paul.

@wjurica Assuming you're using c#, consider Newtonsoft for the deserialization & mapping process. It's two lines of code to map your data to a class.

https://www.newtonsoft.com/json

Hi @kinco-h - I assume (hope) you got the info you needed from our support folks?

Hint - you access chat support by clicking on the "Ask Support" button in the top right-hand corner of the Design Portal...

2024-12-04_09-07-57.png

Thank you so much!

You can achieve it by writing a cloud code script that retrieves the data of each individual user's user entities and stores it in a custom entity collection. After that, call the method RunBatchUserScript() to execute this process for every user within the app. Then, the resulting collection can be downloaded for analytical purposes.

For clarity, Firebase Cloud Messaging recommends creating a topic using Pub/Sub, though this approach is optional.

Oh, server can use client API

Okay, I built it using the commented out part above.