<crickets>

D'oh! We get it - we're all busy - and some folks are shy.

That said - the more feedback we get, the better we understand what features the community is looking for! (We've got plenty of features queued and/or in development - but it's prioritizing them that's the real trick.)

So let us know what works and what doesn't!

For example, is the Self-Service Account Deletion useful? Or were you all just planning to handle it manually, making it less important?

Paul.

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.

Hi there- thanks for bringing this to our attention! A newer version of the Unity Package containing a fix for this has been uploaded. Available here: https://github.com/getbraincloud/braincloud-csharp/releases/tag/5.4.1

one workaround im thinking of doing is having a "fake" user stat. one that tracks the actually XP and another that's "unlocked XP". then just increase the unlocked XP whenever someone "claims" the milestone