Happy to help!

Hi Davis,

As with most things brainCloud - there are a few ways that you could approach this.

You could certainly use player statistics - as you are for your other unlocks.

brainCloud allows you to attach "extra data" to a product - they are essentially key+value pairs, that get returned as a simple JSON map in the VerifyPurchase response.

You could catch that response on the client, or for more security, do it from the server - either via a cloud code script that wraps the VerifyPurchase() call itself, or as you said, a post-hook on the VerifyPurchase call. Just update the named "statistic" based on the "extra data" portion of the VerifyPurchase response.

There is one other way of doing this - which is to have a special currency for your "coin booster". <- brainCloud allows you to have as many as you want.

To use it, simply create a currency called "coinBooster" - and allow the customer to buy one of them. Voila - no custom code!

Hope that helps!

Paul.

Hi Claudiu,

It's possible to do this using cloud script... you just need to impersonate the other user...

Here's an example script that does this - caveat, it only returns the first page of user items.

Create the script, and set it's test parameters to:

{
  "profileId": "www-xxx-yyy-zzzz-123456"
}

(Note - you'll of course want to replace profileId with an id of a user that you want to test with.)

And here's the code...

var response = {};

// We need to impersonate another user to make this call
var otherSession = bridge.getSessionForProfile( data.profileId );
var otherUserItemsProxy = bridge.getUserItemsServiceProxy( otherSession );

// Now, request the page of items from that proxy
var context = {
  "pagination": {
    "rowsPerPage": 50,
    "pageNumber": 1
  },
  "searchCriteria": {},
  "sortCriteria": {
    "createdAt": 1
  }
};    
var includeDef = true;

var itemResult = otherUserItemsProxy.getUserItemsPage( context, includeDef );

if (( itemResult.status == 200) && ( itemResult.data.results.count > 0 )) {
    response.items = itemResult.data.results.items;
} else {
    response.items = [];
}

response;

For convenience I've attached an export of the script. You can import this script into your app from the Design | Cloud Code | Scripts screen.

Hope that helps!

Paul.

RetrieveAnotherUsersItems.ccjs

Hi folks,

As most of you probably already know, we released brainCloud 4.3 last week.

New features in this release include:

• Geo Matchmaking - automatically match users to the closest servers
• Custom Entity Migration - export/import of custom entities is built into our Deployment service
• Set-top Hand-off API - need an easy was for user to log into an set-top box of VR headset? We've got you covered
• User Service - building an app with an admin component that needs to be able to page through your users? brainCloud now supports this...

And a bunch of other community requests, including:

• User Items Screen
• Dynamic Group Leaderboards
• Autojoin across multiple group types
• Reset quests API
• Bundle Compression
• OKTA authentication support

Plus our web + ui folks freshened up the look-and-feel as bit as well!

Check out the Release Notes for all the details.

Happy Coding - and let us know what you think!

Paul.

D'oh - dueling support team responses!

Hi David,

Thanks for reporting this - it looks like the signature of that method changed over time, but we didn't update the cloud-code version of the call.

The cloud-code version of that call requires an additional boolean parameter - "includeMetadata" - which determines how much data is returned in the result.

If true, the result of awarding an achievement looks like this (we've since determined the client has likely retrieved/cached that extra data anyway, so there isn't normally a need to return it):

{
    "data": {
        "achievements": [
            {
                "extraData": null,
                "googleAchievementId": null,
                "achievementId": "EGG_ACH02",
                "description": "You saved 10,000 Animals!",
                "title": "Saviour",
                "appleAchievementId": "",
                "steamEnabled": false,
                "fbGamePoints": 10,
                "imageUrl": "https://internal.braincloudservers.com/files/portal/g/11281/metadata/achievements/EGG_ACH02.png",
                "steamAchievementId": "",
                "invisibleUntilEarned": false,
                "fbEnabled": true,
                "appleEnabled": false,
                "googleEnabled": null,
                "id": "EGG_ACH02",
                "status": "AWARDED"
            }
        ]
    },
    "status": 200
}

if false - you just get the id and status of any achievements that are awarded.

If the achievements had already been awarded, you'll get an empty array of achievements back.

So anyway, try something like:

var achievementRes = gamificationService.awardAchievements(achievementIds, false);

and you should be good to go!

Thanks again for reporting this - we'll get that fixed up (which will probably mean we'll add an additional cloud-code method with the proper signature. This method will continue to work though!)

Cheers!

Paul.

Hmm, I'm guessing that this is so that you as a developer have a warning that you may be mucking with an online user's data?

Sadly, unless the user is using RTT, the system doesn't deterministically know that a user is still online.

We do however know when the user last logged in - and that is shown on the User Summary page here (see capture).

You can further get an idea if a user is still online via the User Monitoring | Logs page...

Might be interesting to see if we could query the last session for the time of the last received request... though we'd need to somehow differentiate a real session from an API Explorer session... Hmm, some food for thought.

Hi,

This is very doable in brainCloud.

Check out the Tiers design note in this knowledge-base article:
http://help.getbraincloud.com/en/articles/3344756-increasing-tournament-engagement-with-divisions-and-or-tiers

Hope that helps!

Cheers,

Paul.

Happy to help!

Hey Chris,

Turns out that there was a unique index rule that hadn't been applied to your instance. That's been fixed now - and we've confirmed that all the other indexes are up-to-date as well.

Apologies for that - you should be good to go now.

Paul.