Does LeaderboardService.RemovePlayerScore revert rewards?
-
Hello,
I'm working on a system to purge tournament records of fraudulent players.
If I call LeaderboardService.RemovePlayerScore to wipe a player's entry, does the service also handle the reversal of rewards (or update their reward status) linked to that specific score? Or do I need to manually handle the reward adjustment?
Thank you in advance!
-
No,
RemovePlayerScore()does NOT handle reward reversals. You need to handle that manually. Also note that if the leaderboard is configured for a tournament, it will throw an exception and refuse to remove the score. CallLeaveTournament()for a tournament-based leaderboard, but it does not reverse rewards either. -
Thanks for the clarification.
Just to be sure: if an abusive score has already been accumulated, is there no way to exclude that user from the reward table and dynamically recalculate the rewards for others? i.e., Can we not adjust the rewards distributed through the Claim API retroactively?
-
To clarify a bit more, I'd like to ask about the interaction between these API calls and the "Calculate results" job.
-
Regarding LeaveTournament():
If a user is kicked via LeaveTournament() before the "tournament - Calculate results" job runs, does the calculation job ignore their prior score? Or does the score they recorded before leaving still affect the overall reward eligibility? -
Regarding PostTournamentScoreOnBehalfOf:
If we use PostTournamentScoreOnBehalfOf to manually reduce a user's score before the "Calculate results" job runs, will the rewards be determined based on this modified score?
-
-
I have one more question regarding the behavior of division instances.
Suppose there are instances ^1, ^2, and ^3 generated by a division set ID named "week". If a user belonging to instance ^2 is removed via the LeaveDivisionInstance API, what happens when the next user joins the "week" division set?
Will the newly joining user fill the empty spot left in instance ^2, or will they just continue to join the latest/new instances (like ^3 or ^4) regardless of the eviction?
-
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.