Kerege - Game Backend and Live-Ops Console for a Cross-Platform Multiplayer Game

Dashboard, player search with a quick view panel, player detail with 8 tabs and 6 audited actions, grants and revocations, and remote config with the client version gate.

Support agents grant up to 1,000 Embers alone and senior support up to 5,000. Larger grants and every bulk grant wait for a second approver, who cannot be the requester.

Critical keys such as match rewards, pass prices, crossplay, voice chat and the odds link need a second approver before a change reaches live. Every edit shows a diff and the players it affects.

24 players in 15 countries across 5 platforms, 2 with child profiles, plus 15 grants, 7 reason codes, 10 segments, 8 support cases and 9 staff users.

One Player, Many Platform Accounts

Each platform has its own sign-in and reports its own privileges, such as communication, user-generated content and crossplay. Without one account above them, progress stayed on the platform it was earned on and support could not tell duplicates apart.

Currency Nobody Could Trust

With balances partly on the client and grants made by editing rows, there was no record of why a player's Embers changed or who changed them. A server-authoritative economy needs every movement as a ledger entry with a source, a reason and an idempotency key.

Live Changes at Midnight

Live events were switched on by a developer editing a config file at midnight Bishkek time, mid-afternoon in the Americas. Changes had to become scheduled, targeted by segment and platform, checked against a diff and approved for the keys that move the economy.

Children and Data Rights by Country

GDPR expects a data request answered within one month and lets each EU country set the age of digital consent between 13 and 16. The UK Children's Code covers players under 18 and COPPA needs parental consent under 13. Deletion requests had been answered late or not at all.