brainCloud

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

brainCloud 4.11 is targeted for release tomorrow...

There are a bunch of features and improvement, including:

• Enhanced Redemption Code service
• New Division Management API
• Configurable timeouts for Relay Servers
• Improvements to the Unity Client (including a websocket-native.jslib fix for Unity 2021)
• New Unity Authentication Example

and more.

You will find all the details here: http://getbraincloud.com/apidocs/release-4-11/

Happy coding!

Paul.

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.

Well - the new release isn't out yet - it's just a Release Candidate.

https://github.com/mozilla/rhino/releases

That said - we are very happy to see the progress - since it has been over a year since 1.7.13 was released!

Hopefully soon!

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.

And brainCloud 4.9 is live!

Let us know if you have questions or issues!

Paul.

It looks like the next Rhino release may have some extra support for us there. We will look to enable it once it's available.

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.

Hi,

brainCloud doesn't really force anyone to do anything - we are a toolbox to be used to build your game.

And we certainly wouldn't try to force bad code.

The recommendation to bundle API calls together into scripts reflect the reality that:

• Deserializing a request from a client takes significant time+processing. Processing API calls from within a script is definitely less CPU intensive than receiving and processing them one-at-a-time - thus our API Count pricing reflects that
• There is also a perceivable performance benefit to the end-user. A script that performs a number of API calls from within will outperform those same API calls called directly from the client.

So - we see it as win:win:win - better user experience, better experience for the end-user, and less cost to you.

We encourage you to organize your scripts as makes sense for your application. To help support this - brainCloud allows you to import script functions into your script to be called (bridge.import()) - or to call other scripts directly (bridge.callScript()).

As for why our pricing is elastic - that is so that the costs we incur from your app match the costs to you. This puts us both on the same side when optimizing your app. The lighter your app, the lower the costs on our end, and we pass those savings onto you!

Hope that helps!

Paul.