@JasonL This is what I'm already doing, which is why I'm requesting a new feature, as it has the drawbacks listed above.

Looking at it again, I see you added time correction. I'll try it.

No problem! glad to hear that.

yes that reason too. readgroup result data is not enough so need more data(like score) so need.

Hi Lee,

Thanks for your suggestion. Certainly seems like a simple and useful thing to add!

Paul.

Almost, but you can't define the price in virtual currency.

The solution I came up with is to make a cloud script that purchases and then immediately sells a user item. The user item has a buyPrice and a sellPrice which effectively does the currency conversion.

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.

Thank you! I've hacked an implementation for now that just guesses the ranks on the client side without grabbing the actual ranks. The players will only discover it if they're playing sitting side by side. 🙂

I implemented this pretty easily just using events. Instead of adding a friend I instead send a 'friendRequest' event to the potential friend. once that player views the event and accepts the request the friends are added.

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

Hi @LEE-JONG-GUN ,

Thanks for the feedback.

This is admittedly a tricky one.

The best route I've seen to handle it is to use our shared (i.e. parent-child) accounts feature - which involves using a parent app for the player account - and a child app for the character accounts.

Note that it does involve two live apps - but we can put your parent app on a special plan with no live fee (you just pay for API calls) - and there won't be a ton of API call from that app - cause 99% of all calls will be against the child app.

There is more info here - https://docs.braincloudservers.com/learn/key-concepts/authentication/shared-accounts/

I hope that helps!

Paul.

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

Ah - perfect. Yeah - that sounds like a better option given the full requirements.

Glad you found it... and welcome to brainCloud!

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

Cool. Thanks for sharing the solution here @devsleeper !

Hi @PJ ,

Your usage of lobbies is exactly why we added the concept of long-lived lobbies. (Admittedly it wasn't part of the original use case - which is probably why some of the documentation doesn't seem to properly reflect that usage <-- we'll review that).

So - needless to say - keep going as you are - and reach out if you hit issues!

Happy coding!

Paul.

My profile displays in a different format than my logs do yes - reading 16:05:53.051 PST vs 4:05:53 PM PST, it's not a huge thing but would be nice as preference in profile settings (or cycling format on the log view timestamp itself)