There’s no direct way to cap the exact number of users in a segment, but you can add more criteria with the testing ID to narrow it down?

Cool - good to hear it. And once again: thanks for reporting it!

Hi @richard,

Hmm - yeah - I don't think that JSON is currently editable in the portal.

Paul.

Hi @william ,

We do have plans to support the new receipts. The work has been assessed - but not scheduled yet. I would expect it to be early next year.

Thanks for asking!

Paul.

Hi,

Oculus authentication is supported.

The devs are currently gearing up to add IAP support for the Meta Horizon store.

I hope that helps!

Paul.

Please refer to the article -- Implementing Continuous Lobbies in the brainCloud Help Center for details.

Apologies for the late reply, but thank you! This really clears up the flow for me. 🙂

The only thing regarding FindOrCreateLobby instead of CreateLobby is that the request to CreateLobby is deliberate. While I do intend to integrate FindOrCreateLobby as a "just throw me into a running game" option (which probably is the desired flow in most cases), I also want a player to be able to say "I want to start a game for my friends, and I also want to be the host and set the rules of the room".

I'm just clarifying that in case I'm misunderstanding the intent between the two calls, and that FindOrCreateLobby can indeed be used for either flow that I just described.

Sorry for the confusion, I was under the impression a publisher key gave you certain read-only permissions on a user given they own your game (this was silly in hindsight)

While the users in question had public profiles, their privacy settings for friends lists were set to private.

Thank you for your help! I now understand what you meant by "as long as users grant your app permission".

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.

Hi @william - thanks for the suggestion - I'll present it to the devs.

One note - when doing custom queries, MongoDB should automatically choose the appropriate index for it -- you shouldn't have to mention it in your query. Thus - adding a custom index for queries that you are finding slow SHOULD pseed them up... (thus your last feature is actually part of the system)

And... the upgrade is complete.

Hopefully a non-event for everyone!

Reach out to support if you see any weirdness!

Cheers,

Paul.

Oh - and one thing that wasn't in the release notes... we bumped up the Design Portal session timeout -- so if you go away from the portal and come back to it later -- there's a better chance that you can pick up from where you left off (instead of being booted and having to re-login).

Ah! Thanks for letting us know!

@JasonL
Thank you for the info, much appreciated!

Okay - cool!

สวัสดี ต้องขออภัย แต่เราให้บริการช่วยเหลือเป็นภาษาอังกฤษเท่านั้น

[Hi. Apologies - but we only provide support in English.]

You are welcome. Thanks for the suggestion!

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

No problem! glad to hear that.