I know it's just a tutorial to help us get started, but I'm wondering what is the recommended place to store the secret key so that the game can access it if needed but the client can't? What I was doing before with playfab never needed the secret key in the client code so I had it as an Environment Variable on my PC so I could call Admin API's without the need of keeping the secret string around in my code base.

1d1f8c92-82e6-4698-8438-e1f887bfe903-image.png

I'm fairly new so I'm pretty much only calling things inside of the website other than login. Today all I've done is create a few items and I've been running debug sessions on my cloud code that initializes my players first build. When I look into the API Usage it says I have 9000+ bulk operations. Am I doing something wrong or is the expected behavior?

Q1: The removed player is completely excluded from reward calculation, so if the deletion happens before the job runs, that player is never iterated over and receives no rank or rewards.
Q2: Yes, the modified score will be used. The job always reads live state. Note that whether the score actually gets modified depends on the leaderboard type (e.g., for the LOW_VALUE type, only updates if the new score is less than the existing)
Q3: No backfilling, the next joiner goes to the latest instance, not the freed spot in ^2. No loop over earlier instances (^1, ^2) ever happens. The next joiner goes to ^3 (or ^4 if ^3 is full). The freed spot in ^2 stays empty permanently.

brainCloud developers have just release several playable builds of our famous examples! See our cool features in action. Find them at https://getbraincloud.com/demos for Windows, Mac, online and mobile.