Expired and disputed codes

A code that granted rerolls last week can be dead today, and the four codes sites update at different speeds. This is the archive, with who says what.

Checked 2026-11-154 min read

A code that worked last week can be dead today, and the four sites that track Arcane 101 codes update at different speeds. This page is the archive: what each source has moved to its dead list, with the date that source last updated — plus the order to check a code before you write it off.

Dead by broad agreement

These five appear in the expired lists of every source that mentions them:

MrGuider and GameRant do not list these at all — they neither confirm nor deny. Two sources out of four agreeing that a code is dead is enough to stop retrying it, especially when the same two sources keep their live list separate and current.

Disputed: claimed dead by some sources, alive by others

The pattern is consistent: the two sources that updated on 12 November still carry STOPRELEASINGBUGSPLS; the two that updated later (13 and 14 November) do not, and one explicitly moved it to expired. When the more recently updated sources agree a code is dead, believe them.

THX4LIKES is the opposite case — only the single most recent list has dropped it. It is worth one attempt.

Unverified: only one source lists them

These are not in the expired list and we are not putting them there — they are simply single-sourced. They are also the newest codes in existence, added within two days of our check, which explains why nobody else carries them yet.

Two things make them plausible: the naming follows the same convention as the confirmed codes (like-count milestones, update announcements), and the game's own listing asks players to join its community channels for codes — which is exactly where a 1,500-like milestone would be announced. Two things argue for caution: nobody else has confirmed them, and we cannot test them.

The order to check a code before calling it dead

Work down this list. It runs cheapest check first and most likely cause second, so you stop at the real answer instead of retrying blindly.

1. Paste it, do not type it. Copy the string straight out of the table above. STOPRELEASINGBUGSPLS is 18 characters and one transposed letter is indistinguishable from an expired code.
2. Check that you are in the Lucky's Pals group. This is the most common cause of a live code failing, by a wide margin. The group is ID 3204788, about 14,664 members, and the game's own description says codes are for members only. Join it, relaunch, try once more.
3. Check that you finished the tutorial. A fresh account cannot redeem anything. If the first quest is still open, close it before you judge any code.
4. Strip leading and trailing spaces. Codes are case-sensitive and all uppercase; a paste that picks up a trailing space fails the same way a dead code does.
5. Compare against the disputed rows above. If your code is STOPRELEASINGBUGSPLS and it failed, the likeliest explanation is that GameRant and MrGuider are right and the code is dead — not that you did something wrong.
6. Only then assume it expired. By this point you have eliminated the group requirement, the tutorial gate, whitespace and case — which is everything that actually causes failures.

Why the lists drift apart

Codes here are announced on the developer's community channels and expire without a public schedule. A site that refreshes weekly keeps a code listed for up to a week after it dies; a site that refreshes daily drops it the same day.

That produces exactly the disagreement above: STOPRELEASINGBUGSPLS alive on the two 12 November lists, dead on the 13 and 14 November lists. When you see a code alive on one list and dead on another, check the update dates before the verdicts — the fresher list is usually right.

Related

• The live cross-check table — all six codes, four sources, side by side.
• How to redeem — the group and tutorial requirements that make live codes fail.
• Races and rerolls — what the reward does, and why it is random.