@moondory77 brainCloud 6.0 is releasing this month (June 2026). I am really excited about the headline features for it, hope you love it!

@moondory77

Regarding your question: "Has the LiveOps feature been removed or deprecated? I can no longer find any documentation for it, and it seems to be missing from the dashboard as well."

I am not 100% sure which feature you are referring to. But maybe you are referring to a feature in our upcoming 6.0 release?

In brainCloud6.0, we will be moving Promotions and Redemptions to a new Braincloud Category called Live Ops.

We will also be introducing a new feature called Campaigns. (In some previews we may have described it as Live Ops Campaigns).

Campaigns are a major showcase of the 6.0 release and will enable Scheduled Limited-Time Game Modes and A/B Scenarios (w/ built-in promotions)

Additional features being released in 6.0 will compliment the development of Promotions and Campaigns making them incredibly easy to develop and powerful.

Could it be possible you saw a sneak peek at the Live Ops Campaigns feature?

Let me know,
Thanks
JH

@moondory77 Hello,

Regarding your question: " I can easily attach Items and Bundles to it. I am wondering if there is a way to achieve this programmatically via a Cloud Code API?"
The calls you referred to (SysCreatePromotion and SysUpdatePromotion) can be used to attach Items and Bundles to promotions.

Could you to check the example script in API explorer to see if it provides what you need?

The devs use the API Explorer to test the new/updated calls during development - and so the JSON there is always up-to-date.

Added the additional details to 13660

@gyutaelee I will investigate the Per Promotion Deployment option you requested.

As I was working on this I thought there may be a workaround for you that you would like. This could work for your team with minimal effort and on your current version of brainCloud portal.

My solution hides the promotion so that only users you flag as TESTERS will see it.

This would let your PROD testers gain the benefit of the no-ads promotion without disrupting your monetization.

Within Automatic Promotions, there is the option to Target members of any of these segments.

Within Scheduled Promotions, there is the option to Offer this promo to: Only users in:

Advancing to App > Design > Segmentation > Segments we can create a segment that filters to players that are flagged as Testers.

Now, segments need to have at least one more criteria, so let's choose something like has logged in at least 1 time.

Save this Segment

IMPORTANT! Add the segment to your Promotion
This will limit the promo to only eligible users. Noone else sees it!

Next we will need to flag some users as Testers. For a DEV app, the easiest way to do this is to go to the User Browser, RECENTLY ACTIVE and pick players (your testers) with recent activity.

GO TO USER to bring up their user summary and check the IsTester checkbox.

Testers get a special icon

Next, we will return to Segments.

Segments are automatically processed overnight, but you can Refresh Segments immediately with the REFRESH SEGMENTS button. Please note: refreshing segments processes every player so this process can take a while and preferably left to low-traffic times of day.

After processing completes, we can check the cohort of testers by returning to the User Browser choosing BROWSE, and Browse Within A Segment.

These are my Testers, so everything worked.

Since only testers are eligible for the promotion, you are free to deploy it to PROD without affecting your monetization. And the PROD Testers you select will be able to gain the workflow benefit of no ads.

Could you let me know if this solution solves your problem?

Let me know if you have any questions,
Regards
John
-Design

Case 13660 - investigating

Case 13633 - [implementing]

Hi @gyutaelee I am bringing this to the dev team for further discussion. thank you for suggesting it.

Case 5996

Dear @dbgtdbz2 ,

About your feature request #1, “Please allow specifying items as conditions for purchasing virtual or bundle items."

I have developed a mockup for this feature.

If we add your Prerequisite Items request to the system as shown, will this work for your needs?

Note that in this implementation, the prerequisite requirement applies only to a Virtual Currency transaction.

Please let me know at your convenience,
Regards,
John H
-Design

Dear @dbgtdbz2 ,

About your feature request #2. "Required item conditions for virtual and bundle items"

Question 1:
For your feature request, do the prerequisite requirements need to apply in the case that the item is included in a Cash Offer (or Cash Bundle Offer that this item might be within)?

Question 1b:
If YES that means a Cash Purchase attempt by the player could be denied by brainCloud due to the player not having the required Item. Is that appropriate?

Question 2
In the case that an item attempts to be awarded to the user by way of a Quest, level up, or gameplay mechanic, if the player does not have the prerequisite items, what should happen?

Thanks,
JH

Regarding #1, It looks like this can be implemented within the current functionality as follows:

When the client is viewing the chat channel, have the client write a user entity saying, in this channel I have read messages up to (the date of the most recent message they have seen). Next, when the app loads the next time, call “getRecentChatMessages” and count up the messages since (the date of the most recent message they have seen). This will give you your count to show for that channel.

Limitations:
The chat queue for a channel has a limit of 250.
Messages have max days and max history (settable by the developer) so if the players been away a long time, some of those messages wont be around to be counted up.
Go to Messaging Chat to view the settings for these.

Regarding #3, The app can store the GroupOwner information in the GroupSummary data which comes back with ListGroups anyway. For existing groups, on login, have the client call GetMyGroups and UpdateGroupSummaryData for any owned groups. The GroupSummary data area is super useful, you could also put say, a group vibe “Casual”, faction alignment or other group descriptor as well.

Regarding #5 we discussed this idea. The devs emphasized that the description text block can be stored in the GroupSummary or GroupEntities areas. This keeps the system as broadly compatible and efficient as possible for all customers.