Skip to content

feat(leaderboards): add allow_manual_resets and upcoming_resets to leaderboard detail response#472

Merged
kirre-bylund merged 2 commits into
devfrom
feat/1279-manual-leaderboard-reset
Jun 8, 2026
Merged

feat(leaderboards): add allow_manual_resets and upcoming_resets to leaderboard detail response#472
kirre-bylund merged 2 commits into
devfrom
feat/1279-manual-leaderboard-reset

Conversation

@kirre-bylund

Copy link
Copy Markdown
Contributor

Summary

Part of #1279 — Manual Leaderboard Resets (Phase 3: SDK support).

Adds two new response fields to LootLockerLeaderboardDetailResponse:

  • allow_manual_resets (bool): whether this leaderboard allows manual resets to be requested via the server API.
  • upcoming_resets (LootLockerLeaderboardUpcomingReset[]): pending manual resets that have been requested but not yet processed, ordered by scheduled_for ascending. Only populated when allow_manual_resets is true.

Also introduces the new LootLockerLeaderboardUpcomingReset class with:

  • id (int): unique ID of the manual reset request
  • name (string): optional human-readable name
  • scheduled_for (string): UTC ISO 8601 time at which the reset will be processed

These are auto-deserialized from the game API response — no new SDK manager methods are required.

…aderboard detail response

Adds two new fields to LootLockerLeaderboardDetailResponse:
- allow_manual_resets: whether the leaderboard allows manual resets
- upcoming_resets: array of LootLockerLeaderboardUpcomingReset, containing
  pending manual resets ordered by scheduled_for ascending

Also introduces the new LootLockerLeaderboardUpcomingReset class with id,
name, and scheduled_for fields.

Part of #1279
Field removed from LootLockerLeaderboardDetails as the backend no
longer requires the per-board opt-in. Manual resets are unconditionally
available.
@kirre-bylund kirre-bylund merged commit 447cf16 into dev Jun 8, 2026
58 checks passed
@kirre-bylund kirre-bylund deleted the feat/1279-manual-leaderboard-reset branch June 8, 2026 08:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant