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

This can happen if you’re using multiple devices or multiple app installations, as each one generates its own anonymous ID.

We are deploying brainCloud v5.9 today, which includes a new bulk userItem feature that addresses the inefficiencies you mentioned about the multiple item rewards. Please give it a try later today and let us know if it resolves your use case.

Confirmed, StoreKit2 support is included in the upcoming v5.9 release, scheduled for next week.

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.

Yes, this is a known limitation. Due to backend security applied, Rhino can no longer directly access Java classes. Currently, our backend does not convert Java Boolean objects into primitive values before passing them to Rhino.

I’ll forward this to our development team to see what improvements we can make on our side.

Thanks for pointing this out. We’ve updated the linked file to the latest version.

Also, I’d like to mention that we’ve created a Visual Studio Code extension for Cloud Code scripts. It includes IntelliSense and other helpful features that you may want to give it a try.

You can find more details here:
https://forums.getbraincloud.com/topic/307/early-access-visual-studio-code-extension

Thank you for sharing your suggestions. We will review your suggestions and see how we can incorporate them into future releases.

In both cases, the transactions should already be recorded. In your iTunes case, you might have purchased in a sandbox environment. You just need to enable Sandbox Transactions, and those transactions should then appear there.

Thanks for pointing that out. This type of leaderboard isn’t directly supported by the current leaderboard APIs yet, but I’ll forward your feedback to our team for review.

In the meantime, as a workaround, you can create a Cloud Code script to handle it like a voting system -- the script can retrieve the player’s score and then post an additional “voted” score on behalf of that player.

The API calls should come from your script, not from the scheduled task itself, right? Here’s an example of how to set up a daily execution script for your reference -- https://github.com/getbraincloud/examples-unity/tree/master/Invaders#schedule-a-cloud-code-script-to-protect-replays-from-deletion-for-top-10-and-featured-players

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

You can keep using the brainCloud VC system for the user’s Coins, but track their lives using User Entities that store the Lives count and timestamps, etc.. This gives you more control and flexibility over your Lives system.

It depends on where the Oculus client app is running; if it’s on Android, you’ll need to enable the Google Android platform. If it’s on Windows, then the Windows platform needs to be enabled.

In case you didn’t see Paul’s reply in the chat widget, ANG just means Google Android in brainCloud, so you’ll need to enable the Google Android platform setting.

@william Thanks a lot for your feedback and suggestions! It’s really helpful, and we appreciate you taking the time to share your thoughts.

Just a heads-up, our team is working on this bulk userItem feature.

There’s no direct way to cap the exact number of users in a segment, but you can add more criteria with the testing ID to narrow it down?

On the A/B testing side, each user is assigned a unique A/B test ID (0–99) when their account is created. These IDs can be used to segment players for different testing experiments, and are available as criteria within our Segment system. The abTestingId is returned to the app as part of the authentication response, and can also be accessed via the PlayerStats.ReadUserState() call.

Please refer to the article -- Implementing Continuous Lobbies in the brainCloud Help Center for details.