@JasonL Thanks for the update, and for getting this fixed.

One follow-up: now that _copy is auto-appended, the resulting code can
exceed the 12-character limit, and in that case the clone still can't be
saved. For example, a code that's already 8+ characters will go over the
limit once _copy is added.

Ideally, the code field should be editable during the clone step itself,
so the user can set a valid, unique code up front rather than relying on
an auto-generated suffix that may already break the length limit.

Added the additional details to 13660

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.