Hi @LEE-JONG-GUN,

We've got a new button for you. It will be released next week.

Paul.

Hmm - I'll discuss with the devs to see what can be done to have more "open in another window" options for some convenient use cases like this one.

Hi @francesco-lenolli ,

The ProductService has actually been deprecated.

You should use the AppStore service instead.

I hope that helps!

Paul.

Yup. We as devs often resist change. Hopefully you'll come to appreciate Portal-X as you use it more!

No problem @kamil-preciuk - and keep that feedback coming!

Hi @kamil-preciuk,

Okay - there was definitely a regression on that page -- though it wasn't related to the feature I suspected. Anyway - check it now - it should be much much faster. And thanks for reporting it!

Oh - and everyone else - the Regions and App Store analytics pages are now live. Hopefully they help you to get great insights into your apps!

Cheers!

Paul.

Hmm - thanks for reporting this...

That screen IS seeming slow to me. I'm having the devs check it out. We recently added fetching of the entity size to the preview panes for Global Entities (and others) - and I'm suspecting that code may have crept into the routines that we use to fetch the list of objects? Maybe?

In any event - if you find things slow in Portal-X - definitely report them! A big focus of Portal-X was to have much better performance in dealing with larger apps with larger collections of data, users, etc... and in general I believe we've very much succeeded there.

Paul.

Hi Kamil,

Thanks for the feedback. I do appreciate that as we've worked to standardize the flows - that a few extra steps have been added to some of the usage flows. We'll continue to refine that.

Interesting regarding performance. Where abouts in the world are you located? And what screen are you seeing the loading data on?

D'oh - so sorry you will miss it.

Any thoughts on the features that made you like it so much? We are always looking for ways to make Portal-X better!

Paul.

Hi folks,

We've enabled the Language page - but are going to hold on the Region and App Store pages - we've got a few calculation and display issues to address...

(It's hard to have our "test" data replicate the great variety of scenarios that we can see in live data. Anyway - we should have these fixed up in a jiffy )

Paul.

Hi folks,

brainCloud 5.4 is now live!

Note - the new Analytics Screens (for Region, Language and App Store analytics) - won't be available for another day or so. That's just cause the system needs to accumulate the data that those screens depend upon.

Hope you like the release!

Paul.

Hi folks,

brainCloud 5.4 is ready for release - and has a ton of new features - including:

• EdgeGap Multiplayer integration
• New Matchmaking Monitor screen (plus matchmaking performance improvements)
• New Server Monitor screen
• New Region, Language and App Store analytics screens
• New APIs for retrieving transactions; IfExists versions of Leaderboard and Event APIs; GetMyDivisions() now returns claimed tournaments in the "Complete" state; etc.

You'll find the full release notes here.

We are on track to deploy the release on Tuesday, Sept 10th.

[We had been planning to deploy Wed Sept 5th - but a late-discovered issue with our updated matchmaking system forced a delay. That said - it's all good now!]

Questions and feedback welcome. We hope you enjoy the release!

Paul.

Hmm - not currently...

I'll put it to the devs for review.

Update - we discussed it and we think you are good to go.

A test of 1000 stats revealed that the resulting statistics object (that contains all values) was only about 64KB - which is smaller than I had feared. So it looks like 2000-2500 stats will come in less than 200KB.

Note - that IS 200KB more data that will be returned during an Authenticate call - and during readUserState() - but it should work okay.

I assume you'll be creating these stats dynamically. That is controlled via the setting on this page (you've probably already discovered it).

One warning is that stats are case sensitive - so we'd definitely recommend that you standardize the creation/accessing of the stats - maybe do an uppercase() or lowercase() cast before creating / accessing them.

I hope that helps. Good luck!

Paul.

Hmm - I don't think there's a hard limit - but that said - I'm not sure > 2000 stats would be recommended either.

I know of apps in production with hundreds of keys - but I am not aware of any in the thousands.

Let me check with the devs...

Hmm - not currently - but it's coming...

Unfortunately it didn't make it into 5.4 (which drops in a few weeks) - so that will end up in 5.5.

Paul.

brainCloud doesn't directly support loot boxes currently... Though of course the Item Catalog and User Items services give you the building blocks to construct your own system in cloud code.

To implement such a system, you would:

• use Global Entities or Unowned Custom Entities to represent the collection of loot box templates
• construct your JSON with the rules (percentages, etc.) for constructing the loot box
• then write a cloud code script that when run - performs the work to award the user the relevant items

Note - there are future plans to add such a feature to brainCloud - but it isn't scheduled yet. I'll add your +1 !

Paul.

Hi,

The general approach is to have your script re-schedule itself immediately when it runs (before it does the rest of it's processing).

So then - you just schedule it to run the first time... and each time it runs it re-schedules itself to run again.

You want to re-schedule the script immediately before you do the rest of the processing - so that if there happens to be an error in your script - the rescheduling still happens... (otherwise your weekly cycle would stop).

I hope that helps!

Paul.

Hi - normally what you'd do there is attach it as a reward to XP level 1. <- XP level 1 has a minimum XP of 0 - so users get it when the user account is created.

I hope that helps!

Hi,

Thanks for the suggestion. We're actually working on more country support right now - so adding segment criteria for it makes total sense.

As for the "OR" and "AND" support - the system currently supports "AND" ...
... but yeah, adding "OR" will be a bigger deal.

I'll run it by the devs and add it to the roadmap with your +1 though...

Paul.