Hi @gyutaelee,

Thanks for the follow-ups. Here are answers to your three new questions:

A1: Right now, pagination for GetSocialLeaderboard (or other social leaderboard APIs) is not supported, and adding it would be a non-trivial server-side change, not a quick configuration tweak. It’s something we’d like to improve, but it’s not on the short-term roadmap at the moment.

A2: Raising maxMultipleLeaderboardScoreLimit to 100
The maxMultipleLeaderboardScoreLimit value is configurable on a per-app basis, with a default of 10. We do try to keep this value low because GetMultiSocialLeaderboard is quite expensive on the server, but for your use case we should be able to bump it to 20 for your app so you can safely call GetMultiSocialLeaderboard([leaderboardId], 20, replaceName). We’re not normally bumping this limit to 100, but 20 is reasonable. If you’d like us to do that, just let us know your appId and we can review and apply the change.

A3: Getting only the current player’s rank/score in their friends leaderboard**
There’s no dedicated API currently that returns just “my rank among my friends” in a single call. However, you can get both the top list and your “my rank” context in one call using GetMultiSocialLeaderboard with a single leaderboardId and a leaderboardResultCount set to your truncated top‑N (e.g., 50 or 20). The response includes a selfIndex field computed server-side:

If the current player is inside the top‑N, selfIndex is their rank (0-based). If the current player is outside the top‑N, selfIndex is -1, and you can show something like “Your rank: > N” in the UI.

All fields are editable during the cloning step, and the Code field is also editable there. I’m not sure why it’s looking like the Code field isn’t editable for you, it should work the same whether it’s under or over the 12‑character limit.

@Paul-Winterhalder Thank you!

My question has been answered.
Thank you for your kind and detailed explanations every time.

Added case 13932

Thank you for your response.

We used the automated promotion without making any changes to it. However, we confirmed that it works correctly in the production app.

It seems that the issue may have been temporary, or that there was something incorrect in our configuration at the time. If the issue occurs again, we will contact you again with more details.

Thank you for your help.

The SDK is just a plain C# source library you can drop into any .NET project (not Unity-only). You can find usage examples and the source in our GitHub repositories at https://github.com/getbraincloud.

@johnh
I apologize for the late reply. I have reviewed the details you mentioned.
If the item purchase matches the mockup photo above, it appears to be quite useful.
'Helmet Equipment Enhancement Ticket'

Requires a specific item, consumes currency
These needs can be fully resolved with a single transaction.
I expect that if this feature is included for paid products as well, their utility will increase in the future.

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

Ah - great to hear @jongdae-won . Thanks for the update!

Added the additional details to 13660

Thank you for your kind response.

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

cb1f4861-16f8-432a-bb22-4b71dc0b0ce1-image.png

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

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.

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.

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

ec366981-f641-4833-87f2-64798766555c-image.png

GO TO USER to bring up their user summary and check the IsTester checkbox.
d1094afd-ca63-4ce6-8070-477c879fb1d4-image.png

Testers get a special icon
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.

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.

43a330f6-e572-4b0b-a8ca-c0d631e63240-image.png

These are my Testers, so everything worked.
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

Case 13633 - [implementing]

@Paul-Winterhalder , could you please respond to @noah 's inquiry?

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

Thanks @Brad-Hester !

Thank you for your helpful response. I will proceed as you suggested.

It's been resolved. Thank you for your response!