@Paul-Winterhalder Yes please, there are other gaming backends which only works with Open Id . I already shared one requirement with Jason. Implementing this will not just solve my edge case but open opportunities for lots of other backends to work well with BrainCloud

Thanks @Paul-Winterhalder

@JasonL I understand the reason, but please do provide a way to pass custom data to authenticate api so we can use that data to set user displayname or profile picture or soemthing else on post-hook.
Without this, we have no choice but to call a seperate call from client (so no beneift of 2 free api inside cloud call)

Hi Ali,

First of all - sorry for the slow response. I somehow missed this message.

The MultiSocialLeaderboard call is normally used to create Candy Crush-style maps - where you would normally show just the top player on each node of a map.

It's otherwise a pretty expensive call (as we're filtering/joining your friends list with multiple leaderboard lists) - so thus we restrict things to keep things fast and server utilization reasonable.

Do you have a use case that requires the larger leaderboard sizes - or maybe you were mistaking the intention of this call with another?

Anyway, hope that perspective helps!

Cheers,

Paul.

Thank you very much 🙂

Just noticed this was never replied to!

To clarify - our new Users API was delivered in 4.3 late last year.

Cheers!

Paul.