@JasonL
Thank you!!

Hi Chris,

User entities are primarily indexed by profileId + entityType - so the singleton API will scale well no matter how many players you have.

That said, if your use case gets more complicated, with say hundreds of entities of a particular type per user (say maybe you are modelling user created towns, that sort of thing) - you could consider using Owned Custom Entities instead. You can define addition, custom indexes for those... keeps those lookups fast and efficient.

In addition, if you end up having >1000 Global Entities, you should definitely look at switching to Unowned Custom Entities. Same deal - you can define your own custom indexes...

Hope that helps!

Paul.

Hi @Alexandru ,

We've just officially added the Segment call you're looking for to brainCloud 4.55 - which is targeted for release in the next ~30 days...

Updated Roadmap here - https://portal.productboard.com/braincloud/1-braincloud-baas-roadmap

Paul.

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

No problem - happy to help!

Paul.

Happy to help! 👍

@paul-winterhalder
then it can repeat push notice?

Thanks guys! I figured it would be ridiculous if I had to do timeout checks and retries myself 🙂

Follow-up on this...

My guys have looked into it, and the way we version our global files isn't compatible with this new feature from Unity. Apologies!

(PS - No plans yet for when/if we'll support it. Certainly tons of folks use an external CDN with brainCloud apps though - so the option is still there for you!)

Happy to help! 🙂

Paul.

HI @richard - we're currently working on a feature that will handle this directly for brainCloud 5.9.

In the meantime, an interim approach would be to:

Manage the Lives in a virtual currency. In the item catalog - you can indicate the currencies to award from the offer via the extra data JSON. And create a post-hook on PurchaseUserItem - calling a script to award the appropriate currencies - and immediately consume the new "item" that was purchased...

Just a thought...

[But yeah - we're going to have a more direct solution in 5.9 - which is currently targeted for November release.]

Paul.

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.

Okay - cool!

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

You are welcome. Thanks for the suggestion!

Ah - perfect. Yeah - that sounds like a better option given the full requirements.

Glad you found it... and welcome to brainCloud!

D'oh - bit late on the update, but 4.1 has been released, and you can now search on isOpenGroup (as well as the new groupSummaryData).

4.1 Release notes here - https://getbraincloud.com/apidocs/release-4-1/

Cheers!

Paul.

Awesome! Still a few things to clean up but I appear to be right back to testing within the editor, but against brainCloud's actual lobby system. The key was setting debug to true in the config.js and following the instructions at the end of the GitHub page. Thanks again!

Okay, I built it using the commented out part above.

Hi Panagiotis,

Thanks for the feedback!

That vertical icon bar on the far left is new in 5.2. It was key to allowing us to free up more space - moving the Debug + Log screens to their own pane. (i.e. now the screen is only ever split vertically in 2 - instead of sometimes split into 4 pains - 2 verticle and 2 horizontal).

The font scale and tab size options were there before too - but are somewhat more discoverable now that we have that cog wheel.

Glad you like the changes!