Hi Jose,

Sounds like you want to look into our Presence feature.

Presence is designed to let users know when their friends are online. You can think of it like the old Xbox Live friends feature - where you can see which of your friends are online - and optionally what they are doing.

And Presence uses RTT - so users will be notified in realtime when the presence information of a followed user changes.

Presence works with Friends, Groups, and arbitrary lists of users.

More details here - http://getbraincloud.com/apidocs/apiref/#capi-presence

Hope that helps!

Paul.

Hi,

brainCloud offers a number of APIs for looking up other players. You'll find them all in the Friend service.

As far as looking up players by name, it isn't highly recommended - since names in brainCloud are not guaranteed to be unique (and thus lookups are less deterministic and slower).

It's generally more useful to look up other players by UniversalId - which are guaranteed to be unique.

Now - maybe your app isn't using Universal Identities - so it seems odd to lookup by the UniversalId. Luckily, brainCloud supports a non-login version of a UniversalId - so you can have the user pick a Display Name which will be associated with their account, but they don't actually log in via it (and there's no password for it stored).

To use non-login UniversalIds...

Attach the non-login identity via AttachNonLoginUniversalId() Later on, to update the id, use UpdateUniversalIdLogin() <-- disregard the misleading name - it works for both login and non-login versions of UniversalId Set the player's name to match the universalId (useful for leaderboards) via UpdateUserName() Finally, to look-up a player, use FindUserByExactUniversalId() or FindUserByUniversalIdStartingWith()

Hope that helps!

Paul.

I figured it out. Segment has a Legacy - Project source type, using that worked.

Solved:

IDK if this is the right approach but I am using brainCloud's LitJson and JSONMapper. I will map out the things I need and put it into an object of variables I chose to parse out.

(Post the answer from brainCloud chat channel)

Actually, there is a workaround that you can perform the tournament rewards adjustments,

Turn off the auto claim Add a post-hook to Authenticate instead <- where auto-claim would normally run And in the post-hook look to see if they have tournament rewards, and if they do, claim them there - performing any award adjustments that need to be made.

(Note: this issue has been solved through our online chat support.)

As a further heads up folks - it is looking like the 4.5.6 server release may get delayed until early next week. This is to allow us to create a proper mechanism for controlling with specific versions of Lobby Services are active at a time... (right now, it is possible for both old and new lobby services to be active during an upgrade transition - and given how much lobby processing has changed in this release - that wouldn't be good).

That said - the rest of 4.5.6 is ready - so we are going to be doing a bit of an incremental roll-out...

We are starting to release the 4.5.6 Client Libraries today We are also making the 4.5.6 Relay Servers available (on our existing 4.5.5 servers) <- this is a simple feature gate for us to enable.

Then, once the 4.5.6 servers (with the new Lobby Servers and a few other fixes) are available, we will release them... that should be either late this week, or more likely early next week).

Anyway, just FYI...

Paul.

I implemented this pretty easily just using events. Instead of adding a friend I instead send a 'friendRequest' event to the potential friend. once that player views the event and accepts the request the friends are added.

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)

To limit operations like IncrementExperiencePoints() to cloud code only. This will essentially take away the ability to make these calls from the bare client API. You can see a script that enforces these restrictions here - https://getbraincloud.com/apidocs/cloud-code-central/handy-cloud-code-scripts/restrictclientcalls-script/

Refer to another post below for more strategies you can apply to prevent cheating: https://forums.getbraincloud.com/topic/23/discussion-strategies-to-prevent-cheating-in-tournaments

Hi Lee,

Apologies for the issue.

As you mention - it appears that the issue was due to a Redis failure - and some fail-over handling in our API Servers that didn't seem to work properly for all servers. This resulted in some RTT errors for some apps.

The issue has since been addressed (by rebooting the failing servers).

We're going to do a post-mortem on the Redis fail-over code to see if we can find the offending code-path - and we've added additional monitoring alerts that will look for just this sort of error in the future so that we can act upon it immediately.

Thanks for reporting it!

Paul.