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.

Added the additional details to 13660

Q1: The removed player is completely excluded from reward calculation, so if the deletion happens before the job runs, that player is never iterated over and receives no rank or rewards.
Q2: Yes, the modified score will be used. The job always reads live state. Note that whether the score actually gets modified depends on the leaderboard type (e.g., for the LOW_VALUE type, only updates if the new score is less than the existing)
Q3: No backfilling, the next joiner goes to the latest instance, not the freed spot in ^2. No loop over earlier instances (^1, ^2) ever happens. The next joiner goes to ^3 (or ^4 if ^3 is full). The freed spot in ^2 stays empty permanently.

brainCloud developers have just release several playable builds of our famous examples! See our cool features in action. Find them at https://getbraincloud.com/demos for Windows, Mac, online and mobile.