bitHeads

Hmm, not really...

You can get the number of sessions created in an hour with this call: https://getbraincloud.com/apidocs/apiref/#capi-globalapp-sysgetdailycounts

But brainCloud doesn't otherwise track a concurrent session count per app.

There are certainly 3rd party analytics packages that you could link into your client that would give you that sort of information though.

Paul.

I see - clever Ali.

So basically the matchmaking was a custom implementation using custom entities.

I assume once all players had been decided the last player in ended up creating the async match and then it went from there?

And agreed - sounds like a good use case to add to our list.

Paul.

FYI - this feature was added in brainCloud 4.13 - https://getbraincloud.com/apidocs/release-4-13/

Hi,

brainCloud currently offers two forms of matchmaking:

Offline matchmaking - for async match (i.e. words with friends) or one-way multiplayer (i.e. class of clans) style games. Both of those multiplayer types require you to have an opponent to play against when the match starts.

There is also online matchmaking - which uses our lobby system - which is suitable of any online / real-time sort of multiplayer.

(That one doesn't require you to have an opponent in mind when the lobby starts... and the lobby can start a match via a relay or room server session right away...)

That said - I get the feeling that you are talking about more of an async match scenario (i.e. not-necessarily-online multiplayer) - where the match can start before an opponent has been identified.

Am I correct that that is the scenario you are wanting to target?

It's an interesting approach - as there's a much lower chance of matching against another player who isn't going to respond in a timely manner.

Let me know if I've got the scenario right and we'll give it some more thought...

Paul.

So - the 3rd party service would use OpenId to log into your brainCloud app to verify whether a user exists or not (and presumably to potentially get other permissions).

Is that the suggestion?

Paul.

Hi Dan,

Thanks for reporting that. We'll get it fixed up.

Paul.

Hi Kirlos, as you can see from the response's message field, there are two elements (id and name) underneath, you need to append .id to specify the first search field for id, so change the "message.from" to "messsge.from.id" should solve this problem.

You can hook the script to brainCloud authentication API and check the loginCount from the response, the related doc can be found here.

Call AttachUniversalIdentity() method from client lib, the username is uniqueness enforced.

I agree - and security-wise prefer it to the pre-hook solution we were considering...

We are looking into it.

Jake - I've sent you a question in the support chat - wondering what the timelines for your app are...

Paul.