General

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.

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.

Oh, server can use client API

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

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.

Great. This perfectly answers my question. Thank you!

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 - 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!

If looking for a Discord to chat with other devs implementing BC, the "GBaaS" Discord server has an official ambassador inside (although mostly for use with a feedback bot to forward to themselves and unofficial dev chatter with other folks implementing BC). It's decently active in the #braincloud channel:

https://i42.games/gbaas (disclaimer: I run this server, but it's been around since 2016)

@Brad-Hester That bug has been fixes (and patched). Thanks for reporting it!

In case anyone else had a similar issue...

There was a Cloudflare-related cert issue associated with a site called cdn.jsdelivr.net.

As I understand it, the Monaco editor that Portal-X uses for editing source and JSON files (and many other common web-based components) makes use of that site.

More details on the issue here: https://github.com/jsdelivr/jsdelivr/issues/18565

The issue was temporary - and seems like it only affected only certain localized regions... (just a guess on my part there).

Anyway - all good now - and nothing directly related to brainCloud.

Paul.

Hi Nguyen,

brainCloud makes use of both Memcached and Redis as part of it's architecture - but we do not directly expose these in our APIs.

What was your use case?

Paul.

Ciao @Greg-Moulds,
you rock boy! 🙂
I tried reducing the "early" launch setting as you suggested and in fact now the waiting time is very short. That was exactly the problem.

Thanks!

Thank you both for the helpful replies. I am educating myself further and exploring options. Depending on what I decide to pursue as the final option, I may be back 🙂