hi. @paul-winterhalder @johnh Recently, security-related issues have become an ongoing concern within our company. In this era of AI, we are facing persistent security challenges, such as intrusions into our internal network and the theft of keys belonging to remote workers. I believe this is a matter that can no longer be deferred. API keys must be assigned specific permission scopes. While the current IP range configuration may have been designed with only servers in mind, it becomes highly impractical when developing internal web admin tools that rely on server-to-server (S2S) keys—as it would require registering the individual IP addresses of every staff member, which is simply not a viable solution. Please take this issue into consideration.

@JasonL It works! Thank you!

@paul-winterhalder I will explain in detail using the widget.

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.