LEADERBOARD ID MODE MINIMUM ALLOWABLE VALUE MAXIMUM ALLOWABLE VALUE RESERVOIR SAMPLE SIZE
{{leaderboard.name}} {{leaderboard.mode}} {{leaderboard.min}} {{leaderboard.max}} {{leaderboard.sample_size}}

{{currentLeaderboard.name}} - Processing of new entries could take up to 5 minutes before they appear here.

No scores for this leaderboard
No scores for search: {{searchScoresControl.value}}
PLAYER SCORE
{{score.user}} {{score.value}}

No banned players

NAME
{{playerName}}

Leaderboard queue processor

Are you sure you want to delete leaderboard: {{currentLeaderboard.name}}?

All data in {{currentLeaderboard.name}} will be lost.

Are you sure you want to ban the player '{{currentScore.user}}'?

'{{currentScore.user}}' will have their future scores rejected. All their current scores will remain. The scores can be deleted manually.

These changes will be reflected locally in the CGP for now and may take a few minutes to propagate to the server.

Are you sure you want to delete the player '{{currentScore.user}}' with score '{{currentScore.value}}'?

These changes will be reflected locally in the CGP for now and may take a few minutes to propagate to the server.

Are you sure you want to remove the ban on {{currentPlayer}}? This will restore all their scores to existing leaderboards and allow their future scores to be posted.

These changes will be reflected locally in the CGP for now and may take a few minutes to propagate to the server.

Processing the leaderboard queue manually is a development only feature.

This feature could lead to duplicate entries. It is highly recommended that you do not to use this feature in an production environment.

By default the leaderboard queue processor executes on a scheduled cycle. The default is every 2 minutes.

Are you sure you want to manually call the processor?