Thank you for sharing this information. It does not have an impact on our server-side validation.

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

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

Update - we've confirmed with the server team that we believe we are all set.

We'll perform some tests when the Sandbox servers cut over the week of Jan 20th to confirm.

Paul.

@wjurica Assuming you're using c#, consider Newtonsoft for the deserialization & mapping process. It's two lines of code to map your data to a class.

https://www.newtonsoft.com/json

Hi @kinco-h - I assume (hope) you got the info you needed from our support folks?

Hint - you access chat support by clicking on the "Ask Support" button in the top right-hand corner of the Design Portal...

2024-12-04_09-07-57.png

Cool. Thanks for sharing the solution here @devsleeper !

Hi @PJ ,

Your usage of lobbies is exactly why we added the concept of long-lived lobbies. (Admittedly it wasn't part of the original use case - which is probably why some of the documentation doesn't seem to properly reflect that usage <-- we'll review that).

So - needless to say - keep going as you are - and reach out if you hit issues!

Happy coding!

Paul.

My profile displays in a different format than my logs do yes - reading 16:05:53.051 PST vs 4:05:53 PM PST, it's not a huge thing but would be nice as preference in profile settings (or cycling format on the log view timestamp itself)

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!

Thank you so much!

You can achieve it by writing a cloud code script that retrieves the data of each individual user's user entities and stores it in a custom entity collection. After that, call the method RunBatchUserScript() to execute this process for every user within the app. Then, the resulting collection can be downloaded for analytical purposes.

For clarity, Firebase Cloud Messaging recommends creating a topic using Pub/Sub, though this approach is optional.

Oh, server can use client API

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

Gooood!!!

Hi there- thanks for bringing this to our attention! A newer version of the Unity Package containing a fix for this has been uploaded. Available here: https://github.com/getbraincloud/braincloud-csharp/releases/tag/5.4.1

Hi @francesco-lenolli ,

The ProductService has actually been deprecated.

You should use the AppStore service instead.

I hope that helps!

Paul.

2024-09-17_19-55-15.png

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

one workaround im thinking of doing is having a "fake" user stat. one that tracks the actually XP and another that's "unlocked XP". then just increase the unlocked XP whenever someone "claims" the milestone

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

2024-08-27_09-37-51.png

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.