Note - the system allows a maximum of 15 anonymous ids. If you exceed that, it will delete the oldest ids to keep you at 15.

[Background - this used to be totally unlimited - but they really added up for some apps - so we implemented this behaviour and set the max of 15 as being "more than reasonable enough to handle all use cases!" 🙂

Paul.

Thanks for reaching out and for raising the question.

At the moment, the VS Code extension does not support targeting or importing from a specific directory. Its primary purpose is to synchronize Cloud Scripts stored in brainCloud and provide a convenient way to edit them using standard VS Code workflows and tooling.

We have created an internal task to review this limitation and discuss potential improvements to the extension so that it better supports directory-based workflows in the future.

In the meantime, one practical workaround is to export your Cloud Scripts directly from the brainCloud portal. Once exported, all scripts can be reviewed locally. You can then organize them into a folder structure that mirrors your desired layout, including the use of subfolders and .ccjs files. From there, you can zip the contents and import them back into your app, which can significantly reduce the need for repetitive copy and paste actions across individual files.

Please let us know if this approach works for your use case or if you have additional feedback on how you would like to see the extension evolve.

Hi @bkmitchell ,

thanks for reaching out.

Unfortunately our built-in relay server tech doesn't support what you need for Unity WebGL multiplayer.

Most brainCloud devs implementing your use case would integrate with Photon or Edgegap for their multiplayer for this reason. They both work well and work well with brainCloud!

[PS - This is an area of ongoing development for us though and we aim to fill this gap in the future. I can't comment on timelines for that though...]

Paul.

Hi. Yes, unless an adhoc tournament is scheduled to start immediately after one finishes, there will always be a "wait" version (version with no tournament) in between scheduled adhoc tournament versions.
And when it comes to the retained versions, we skip counting the wait versions.

Posting a copy of the AWS service health page for posterity.

It mostly refers to the outage impacting DynamoDB - but a lot more services than that were impacted. We expect that just means that a lot of AWS services use DynamoDB under-the-covers to operate.

2025-10-20_05-58-47.png

Hi,

Actually - voting leaderboards are implemented via the PostScoreToLeaderboardOnBehalfOf() call - where you can basically vote for someone else's score. [i.e. voting for that person].

Create the leaderboard as a "Cumulative" leaderboard - and basically the player votes for the score of another player - incrementing it by +1.

I suppose we should add those details to the roadmap item!

I hope that helps to clarify things!

Paul.

As I mentioned in the support chat - the issue is that midnightPSTinUTC isn't dynamically calculated for midnight today -- it's midnight PST on Oct 4th. [i.e. over a week ago].

What's happening is the call is accepting that past date - which puts the script in the front of our queue to be run ('cause we think we're late!) - and it gets run in the next 60 second job interval. And then reschedules itself in the past again.

So basically this script is running roughly 60*24 = 1440 times a day.

Anyway - I'll have the devs look into it - we should return an error if you are scheduling the script too far into the past... [i.e. a second or two in the past is probably fine - and best to do in case the scheduling script has delays of some sort... but clearly 10 days in the past is too far! Probably 60 mins in the past is too far! 🙂 ]

Thanks for reporting this. I’ll forward it to our team and get it fixed.

HI @richard - we're currently working on a feature that will handle this directly for brainCloud 5.9.

In the meantime, an interim approach would be to:

Manage the Lives in a virtual currency. In the item catalog - you can indicate the currencies to award from the offer via the extra data JSON. And create a post-hook on PurchaseUserItem - calling a script to award the appropriate currencies - and immediately consume the new "item" that was purchased...

Just a thought...

[But yeah - we're going to have a more direct solution in 5.9 - which is currently targeted for November release.]

Paul.

We are very interested in doing it - just need to find a model that works and is reliable...

Thank you for the feedback. We’ll take a look and follow up if needed.

@JasonL
Yes we can do that too, I was just wondering how granular our control over the segment is, as one of the requirements for our testing was to have a precise number of users for each group.

Thank you so much for the info, I'll write again if I have more questions.

@Paul-Winterhalder Now, purchase validation proceeds normally regardless of the “Use App Store Server API for legacy receipts (optional)” option setting.

Hi @richard,

Hmm - yeah - I don't think that JSON is currently editable in the portal.

Paul.

@JasonL @Paul-Winterhalder Thanks for your help, the error no longer appears after the Google Android platform was enabled.

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!