Follow-up on this... My guys have looked into it, and the way we version our global files isn't compatible with this new feature from Unity. Apologies! (PS - No plans yet for when/if we'll support it. Certainly tons of folks use an external CDN with brainCloud apps though - so the option is still there for you!)

We are developing our service using BrainCloud's S2S capabilities. The client-side application does not include the BrainCloud SDK. This is because we already have our own authentication system. When creating users via S2S, we use the "External Auth Create" method and subsequently handle operations based on the profileId. Therefore, to maintain a structure where existing user information is updated through the client's login process, the server must directly call the client authentication dispatcher API. In the S2S setup, there is an issue where authentication calls can only be used to issue sessions via the s2sdispatcher. Consequently, the server is manually invoking authentication using the client-side API. I consider this flow to be abnormal. After all, even though the integration is S2S-based, the client login API still needs to be called once. However, the issue is that without calling the client authentication, there is no way within the S2S setup to update the last login time and certain other information you mentioned. I believe this is a common issue that can arise when adopting and using Brain Cloud within an existing system, much like in our case. In summary, the user has created an external account in BrainCloud via the server using sysCreateUserExternalAuth. We issue a token to the user based on our internal authentication system, signing it using the BrainCloudProfileId. Consequently, authentication via the BrainCloud client is no longer required. However, without client-side authentication, there is no mechanism to update information. We need to find a solution to address this gap.

@JasonL It works! Thank you!

Hi @jongdae.won , brainCloud 6.0.1 has been deployed. The Campaign Analytics feature - as well as the APIs for updating the campaign and scenario JSON, are now live! Paul.

Happy to help! Paul.

@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. [image: 1779474011850-cb1f4861-16f8-432a-bb22-4b71dc0b0ce1-image.png] Within Scheduled Promotions, there is the option to Offer this promo to: Only users in: [image: 1779472315918-2a5f3a28-91ba-4f2c-bb1c-5a2c04ead1e5-image.png] Advancing to App > Design > Segmentation > Segments we can create a segment that filters to players that are flagged as Testers. [image: 1779472502119-59f8d7bc-3640-450f-ab67-086af9b8acdd-image.png] Now, segments need to have at least one more criteria, so let's choose something like has logged in at least 1 time. [image: 1779472567232-d86e5f6d-ded8-4c7e-ab26-1c07f9813f0e-image.png] Save this Segment IMPORTANT! Add the segment to your Promotion This will limit the promo to only eligible users. Noone else sees it! [image: 1779474059997-7aca6582-cff3-4469-ae98-6339b341ba06-image.png] 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. [image: 1779473025782-ec366981-f641-4833-87f2-64798766555c-image.png] GO TO USER to bring up their user summary and check the IsTester checkbox. [image: 1779473098382-d1094afd-ca63-4ce6-8070-477c879fb1d4-image.png] Testers get a special icon [image: 1779473149842-e02b71bc-db5b-4127-a6a7-1528697aee6f-image.png] 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. [image: 1779472658705-e306d8e0-553d-475c-a780-43fbed29a271-image.png] After processing completes, we can check the cohort of testers by returning to the User Browser choosing BROWSE, and Browse Within A Segment. [image: 1779473489489-43a330f6-e572-4b0b-a8ca-c0d631e63240-image.png] These are my Testers, so everything worked. [image: 1779473539999-a8b56bbb-536c-447b-9e7d-a8d8236ff165-image.png] 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

Hey, thanks for reaching out. To answer your main question directly: yes, brainCloud's lobby and matchmaking system can trigger an Edgegap server deployment automatically. You do not need to build a custom C++ room server to make this work. https://github.com/getbraincloud/examples-cpp/tree/develop/relaytestapp The relaytestapp example on the develop branch of examples-cpp is a working client example that does exactly what you are describing. It uses brainCloud lobbies and matchmaking to find a match, and once the lobby is ready to launch, brainCloud handles spinning up the Edgegap server and passes the connection details back to all players through RTT. The server configuration you see in the screenshot is what ties everything together on the brainCloud side. That entry defines which Edgegap application to deploy, which regions to consider based on the selected beacons, and the credentials needed to make the deployment call. Once that server is linked to a lobby type, the entire launch sequence is handled for you. The relaytestapp is a solid starting point to see this end to end. [image: 1778170400682-screenshot-2026-05-07-at-12.13.17-pm.png]

Agreed @armitage - the bulk messaging feature is planned for the use case you describe... (and yup - still coming ).

Hi @jesgonzalez , Yes - unfortunately, you need to use AuthenticateExternal. We do not have official middleware status with Xbox. We've been trying for years - but as anyone who has dealt with Xbox in recent years knows, they are extremely resource-constrained. Paraphrasing our most recent interactions Due to extremely limited resources and a couple of years of re-orgs, Microsoft won't adopt or support new tools or technologies unless we can prove there’s a clear and active need from developers working on officially approved Xbox titles. (We actually had been making progress on this a few months ago - but then the personnel we were working with got laid off... So now we're at the back of the bus again.) Unfortunately, our lack of status means we can't provide clear details on how to do it, but we do have some service partners / contractors / consultants we can refer you to who can quickly connect you. If you want to reach out to us via our Support widget, we can put you in touch with them. Oh - and be sure to mention this situation to your Xbox account rep (if you are lucky enough to have one). It's only via pressure from the dev community that we're going to get unblocked in this area! Paul.

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.

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. [image: 1760954460867-2025-10-20_05-58-47-resized.png]

Ok, I found it. It wasn't a global setting, it was a filter on the reports. Thanks!

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.

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.

Okay - cool!

@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.

You are welcome. Thanks for the suggestion!

Ah - perfect. Yeah - that sounds like a better option given the full requirements. Glad you found it... and welcome to brainCloud!

D'oh - bit late on the update, but 4.1 has been released, and you can now search on isOpenGroup (as well as the new groupSummaryData). 4.1 Release notes here - https://getbraincloud.com/apidocs/release-4-1/ Cheers! Paul.

Awesome! Still a few things to clean up but I appear to be right back to testing within the editor, but against brainCloud's actual lobby system. The key was setting debug to true in the config.js and following the instructions at the end of the GitHub page. Thanks again!