bitHeads

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.

Hi folks,

brainCloud 4.9 is coming soon! (i.e. will be released in the next 2-3 weeks).

Here's a quick summary of the new features:

• Amazon GameLift support
• Join-in-progress for Room/Relay server games (i.e. backfilling)
• Query available Lobbies
• Unity client compression
• AppStore item purchases
• Tournament management APIs
• $text query support (for custom entities)
• Async Match API improvements (returns summaryFriendData in calls)

And more.

For all the details - see the release notes - https://getbraincloud.com/apidocs/braincloud-4-9/

Any questions or comments - post them here!

Cheers!

Paul.
(PS - brainCloud 4.9 contains an important change/fix for script path handling. Folks organizing their scripts into folders will want to take note. Of course, there's a compatibility flag so the changes don't take effect until you want them too.)

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.

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));

Hmm, I actually am not sure why sampleData[1] works.

I would have thought the correct syntax would have be sampleData["1"] and data["1"] ?

No?

Hi Fabio,

The full roadmap on this is still in progress.

We do have an API now that allows you to upload cloud code scripts.

It's part of our Builder API - and you can request it via our support channel.

The script management API is still a V1 version - in that you manage scripts individually. We have plans to evolve the API so that you can upload zipped packaged to be synced with the scripts - in a similar fashion to what you can do via the web portal.

Although this is taking longer than planned, we wanted to ensure that we built the new support on a solid foundation. So we've added cloud code includes, folders, new script management screens, improvements to performance and caching, etc.

The Visual Studio plug-in is still on our radar - we just need to ensure that the proper API foundation is in place.

Anyway - if you are interested in getting ahold of the builder API, definitely message our support team.

Cheers!

Paul.