Thanks for confirming @peter !

Bundles are described in our release notes here - https://updates.braincloudservers.com/braincloud-5.9-is-live-23Q66A

Randomly assigning 100 items? (Gotta say that sounds like a lot). That said - we are adding it to our roadmap.

Have you checked the logs to see what those users are sending in for the country code during authentication? And can you see any commonality amongst those users?

From your stats it looks like we are correctly detecting US, Korea and Argentina... What code are we reading in wrong?

If you send us your appId (via the chat widget) we can take a better look at your users.

So @noah ,

I guess we misunderstood your use case. By the way you were describing things, we were envisioning a scenario where a user avatar is created, and they need to have an initial set of items - i.e., a cheap sword, a cheap shield, worn leather armor, worn boots, etc. Thus, we thought allowing you to add that to a bundle (where maybe you'd have a different bundle per character class) would make sense.

But I guess that's not what you are getting at? From your message:

It differs somewhat from the goal of "dynamically distributing a single item at once."

I mean - if it's a quantity of a SINGLE item as you say - then our existing AwardUserItem() call does allow you to specify a quantity. That said, I suspect you mistyped and meant to say "dynamically distributing MULTIPLE items at once" - which, as you say, would require an AwardMultipleUserItems() call.

Anyway, we can queue up an AwardMultipleUserItems() call on the roadmap - but we're doing heavy lifting on new features for 6.0 right now - and this is easily handled via a custom script (and remember, calls from scripts are just 1/2 API count each, so it's more efficient that way too) - so it won't be top priority at this point.

So - in summary - I can't promise this will be in the next release. Never say never (sometimes the devs fit extra stuff in once the main features are complete) - but I'd say unlikely for 6.0 - more likely for 6.1 or 6.2.

But as I noted - easily handled via a script, right? Unless I'm missing something?

Paul.

Paul.

Hi @royal,

Thanks for the feedback. You make some good points.

We're currently reviewing it to see what options we might be able to offer for brainCloud 6!

Cheers!

Paul.

Hi @jesgonzalez ,

Yes - unfortunately, you need to use AuthenticateExternal. We do not have official middleware status with Xbox. We've been trying for years - but as anyone who has dealt with Xbox in recent years knows, they are extremely resource-constrained.

Paraphrasing our most recent interactions

Due to extremely limited resources and a couple of years of re-orgs, Microsoft won't adopt or support new tools or technologies unless we can prove there’s a clear and active need from developers working on officially approved Xbox titles.

(We actually had been making progress on this a few months ago - but then the personnel we were working with got laid off... So now we're at the back of the bus again.)

Unfortunately, our lack of status means we can't provide clear details on how to do it, but we do have some service partners / contractors / consultants we can refer you to who can quickly connect you. If you want to reach out to us via our Support widget, we can put you in touch with them.

Oh - and be sure to mention this situation to your Xbox account rep (if you are lucky enough to have one). It's only via pressure from the dev community that we're going to get unblocked in this area!

Paul.

Hi,

This limit is adjustable on a per-app basis. I have reached out for more information (via email) to confirm how many divisionsets would satisfy your requirements.

Paul.

Awesome - glad to hear it.

Hi @Ralph - the patch has been deployed. Hope it works better for you now!

Hi @Ralph - we found the issue. It's a path that is unique to apps that are using the older purchase collection storage format (which changed in 3.9). A fix is on the way. Thanks so much for reporting this!

Hi - we decided to go more generic with platforms after initially adding PS3, PS4, etc...

So now all playstation hardware is just shown as "PlayStation" in our charts - and underneath it all is identified as "PS4". Sorry for the confusion.

Paul.

Is the IAP product set as consumable? Is it a new receipt that you're passing in? Is there an appId that we can use to check your logs @Ralph ? (feel free to send the info in via the regular private support channel)

Cool - glad it works for you now!

Hi @LEE-JONG-GUN - the patch has been deployed. Let us know if it works better for you.

Hi @LEE-JONG-GUN ,

Is that a sandbox receipt for that user? We seem to have found a second flow for sandbox purchases - not sure why there are two - maybe for older vs. newer receipts?

Anyway - we've created a patch and will be deploying it soon.

Paul.

HI Lee,

Can you message into our support system with the appId involved - and the profileId of a user who had the issue?

Thanks,

Paul.

Then just call GetSessionForSessionIdAndProfileId() again.

The check your are doing requires the retrieval of the session from memcached. Retaining a copy of the session and then checking that field later will not solve your use case...

i.e. if the players session was valid at the time the system calls GetSessionForSessionIdAndProfileId() -- and then becomes invalid while you've got the session cached --- you can't just check the "isLoggedOut" field - because even if you COULD access it - you would be accessing a STALE copy of it.

So just re-call GetSessionForSessionIdAndProfileId() and if that call is non-null - the session is STILL good - and you are gold.

Hi @noah ,

That call only returns the session if the user if it's valid and the user is still logged in - so you shouldn't need to check that field. If it's non-null you are good.

Paul.

Hi folks,

brainCloud 5.9 is now live - with StoreKit2 support. Go to it!

Paul.

Note - the system allows a maximum of 15 anonymous ids. If you exceed that, it will delete the oldest ids to keep you at 15.

[Background - this used to be totally unlimited - but they really added up for some apps - so we implemented this behaviour and set the max of 15 as being "more than reasonable enough to handle all use cases!"

Paul.