CRK codes are redeemed in a browser on Devsisters' own coupon page โ not inside the game. Two minutes, six steps, and your rewards are in the in-game mailbox.
Cookie Run: Kingdom's global version handles coupon codes on the web: the DevPlay coupon site takes your account ID and the code, then mails the reward into your game. The in-game Settings screen only shows your ID โ it never asks for a code. That's why every "enter code in Settings" guide you may remember from older versions is out of date.
Same thing, three names: the DevPlay coupon page asks for your DevPlay account; the game's Settings โ Info screen labels it your User ID; older community guides say Player ID. For redemption they all mean the same identifier โ and the official help article also accepts the email address linked to your DevPlay account.
Open the DevPlay coupon page โcrk-codes.com never sees your ID or account โ redemption happens entirely on Devsisters' site.
Searches for "code 50000" spike whenever a new wave of players finds the Info screen. 50000-something is your User ID โ the number you paste next to the code on the DevPlay page. Real CRK codes look like MISSEARTHBREAD26: words, mixed case, one redemption per account.
| Message / symptom | What it actually means |
|---|---|
| Invalid code | Typo, wrong case (codes are case-sensitive), or the code never existed โ "generators" invent fake ones. |
| Expired | The code's window closed. Check the code's status on our codes page โ each entry carries the expiry date. |
| Already redeemed | Codes are one per account. It worked the first time; the reward is in that account's mailbox. |
| Silently nothing | You pasted the code into the ID box (or the ID into the code box). The page won't always flag it โ re-check both fields. |
| Wrong account | The ID belongs to a different account than the one you're mailing rewards into. Guest accounts make this easy to do. |
| Region lock | Rare: a handful of event codes were region-locked. Global codes, which is nearly all of them, are not. |
| Mailbox empty | Redeemed fine but never restarted the game. Restart, then check mail before assuming failure. |
Deeper walkthrough of each error: CRK code invalid โ every reason, ranked.
Autocorrect and case. Mobile keyboards love to "fix" all-caps strings โ a lowercased code fails as "invalid" even though you typed the right letters. Paste, don't type; and if you must type, dismiss the autocorrect bubble before it lands.
Field swap. On a small screen the ID box and code box sit close together, and pasting into the wrong one gives no error โ just silence. If redemption "does nothing", re-check which field holds the 50000-style number and which holds the word-string before concluding anything failed.
Browser login state. The coupon page works in any mobile browser, but if you're logged into a different DevPlay account in that browser than the account you play, rewards mail to the logged-in one. Guest-account players hit this most: tie your game to a proper DevPlay account first, then redeem.
A guest account has a User ID and can redeem codes โ but guest data lives on the device. Lose the device (or reinstall without linking), and the Crystals you redeemed go with it. The safe order: link the game to a DevPlay account in Settings first, then redeem. The code doesn't care; your rewards do.
If any step fails, the failure has a name โ the seven reasons, ranked.
Redemption is a web page, so the flow is identical everywhere: any browser, any device, the same two fields. On PC, keep the game and browser side by side and copy the ID with the mouse. On iOS/Android, screenshot the Info screen instead of hand-copying โ one fewer transcription error. The only thing that ever differs by platform is which keyboard tries to autocorrect your code (see the mobile traps above). Emulator players: the flow is still the web page, not an in-game menu.
New codes drop around livestreams, subscriber milestones, conventions and seasonal events โ roughly every three to six weeks in 2026 โ announced on the official @CRKingdomEN account โ. We check daily and list every code with its status on the home page; the method is public on how we check codes.
โ Page fact-checked November 1, 2026 against the DevPlay coupon page and Devsisters' official help center.