You may write a pre-hook cloud code script with your validating logic and integrate it with [TurnShieldOn()](https://getbraincloud.com/apidocs/apiref/?cloudcode#capi-matchmaking-turnshieldon) method.

You can hook the script to brainCloud authentication API and check the loginCount from the response, the related doc can be found here.

Hi Kirlos, as you can see from the response's message field, there are two elements (id and name) underneath, you need to append .id to specify the first search field for id, so change the "message.from" to "messsge.from.id" should solve this problem.

You can hook the script to brainCloud authentication API and check the loginCount from the response, the related doc can be found here.

Call AttachUniversalIdentity() method from client lib, the username is uniqueness enforced.

Hey, there must be some syntax error in your script, would you be able to provide your script code here?

Hi Dylan, actually, the argument purchaseData for StartPurchase() method takes the Steam Item ID (from Edit Price Entry pop-up) as the input field (not the Item ID from the product list)

Hi Kenneth, our current HTTP Client service doesn't support DELETE with query args yet, we probably add a new DELETE method that takes this parameter in our next release.

You may write a pre-hook cloud code script with your validating logic and integrate it with [TurnShieldOn()](https://getbraincloud.com/apidocs/apiref/?cloudcode#capi-matchmaking-turnshieldon) method.

You can bypass the peer dependencies by adding --legacy-peer-deps flag to your npm install. After modifying package.json, then use npm-install-peers to install the rest of peer dependencies.

Here is the thing, the input parameter data returned from our service proxy is a Java Map object, which does NOT support a number value as key when accessing value using object[key] syntax.

A simple solution for this case is to convert the Java Map object to a real javascript JSON object like below:

data = JSON.parse(JSON.stringify(data));

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