I put together a small fan-made tracker for Roblox Wizard Alchemy players who just want the current code list without scrolling through a long article first.
The page is here: wizard alchemy codes
What it focuses on:
- working codes first, with a copy button next to each code
- a separate needs-review section when a code has conflicting public sources
- an expired-codes area, even when there are no confirmed expired codes yet
- simple redeem steps for new players
- last-checked dates so returning players can judge freshness quickly
Implementation notes:
- Next.js 15 + TypeScript + Tailwind
- deployed on Cloudflare Workers
- no login, no payment, no user-generated content
- consent-gated analytics for basic launch observation
- fan-made wording and non-affiliation disclaimers are shown on the page
The main product decision was to make the page answer-first: show the codes and copy action before explanations, then keep the caveats visible enough that the page does not imply the list is official or guaranteed.
If you build small utility/content sites, I would be curious about the structure: should the update notes stay on the same page as the code table, or is a separate update page better for this kind of tracker?
Disclosure: this is fan-made and not affiliated with Roblox, Wizard Alchemy, Muggle Academy, or the game developers. Code availability can change after updates.
Top comments (0)