Stellar Affinity Codes Tracker
Tick codes as you redeem them — saved locally in your browser.
Use this tracker with the active codes list. Mark a code once you redeem or confirm it failed. Data stays in localStorage on this device — it is a checklist, not an autofill bot and not a second mailbox.
After the 29 July 2026 EROLABS launch, captains often pollute trackers with non-codes: 5000 star fragment (碎星) server gifts, CBT 200% star-diamond (星鑽) returns, login pull rows (200), and carnival titles. Those claim through mail / event UIs described on launch rewards. Only put alphanumeric Redeem strings here.
How to use
- Open active codes and how to redeem.
- Add or tick entries below as you work — one account at a time if you reroll.
- Clear completed rows after a patch if the list rotates (patch notes).
- On livestream nights, pair with current events so you know which drop belongs to which broadcast.
Account hygiene tips
- Redeem on your keeper account only (reroll).
- Bind EROLABS login first (download & PC).
- Dead codes belong on expired, not in your hopeful list.
- After success, map rewards with currencies and spend via progression / gacha & summon.
- Ticket rewards should wait for a tier list target and a beginner week plan.
What this tool will not do
- Invent working codes when the public table is empty
- Claim mailbox launch gifts for you
- Sync across phones or browsers
- Bypass EROLABS account rules
Related
- Tools hub
- Codes hub
- Launch rewards
- Bond checklist for the affection half of dailies
Keep the tracker boring and accurate. Exciting inventiveness belongs in planetary adventures, not in fake coupon rows.
Multi-account warning
Rerollers with five emulator instances should not share one tracker brain. Either keep separate browser profiles or accept that ticks are per device. Redeeming a once-per-account code on a throwaway instance is a common launch tax. Decide the keeper using reroll before festive livestream keys drop.
When public codes are empty for days, leave the tool idle. Opening it is fine; inventing rows to feel productive is not. Spend that energy on beginner week missions and bond checklist ticks instead.
Export mindset
If you need long-term history, screenshot the tracker weekly or copy rows into your own note. localStorage is convenience storage, not an archive. Pair screenshots with expired codes when a campaign ends so your future search-self sees why a key died.
Livestream workflow
Pause the VOD. Type the key into a note. Launch the game. Redeem. Tick the tracker. Only then unpause. People who redeem from memory mistype; people who never tick retry forever. If the key fails, mark failed immediately and check expired codes later rather than looping during the stream.
Also keep a second note for “claimed in mail, not a code” so fragment and diamond returns do not clutter the tracker UI. Clean tools get used; cluttered tools get abandoned by day four of carnival.
Weekly cleanup
Every Sunday, delete ticks older than the current patch notes cycle, archive failures against expired codes, and leave only live experiments. A short list is a used list. Then skim launch rewards once to ensure no mail gift is still sitting unclaimed while you obsess over coupons.
If you play on PC emulator and phone, pick one Redeem device for the week so tracker ticks match reality. Split-device chaos creates duplicate attempts and false already-redeemed confusion during busy carnival evenings. Treat empty weeks as a feature: no rows means claim mail and play, not invent keys. When a partner launcher posts a coupon URL instead of an in-game string, note it outside this tracker so the checklist stays Redeem-only.
Frequently Asked Questions
Quick answers to the most common questions.
Why did my checks reset?
Browser storage cleared, private mode, or another device.
Can I sync phones?
Not yet — use one primary device.
Is this an autofill bot?
No. It is a checklist only.
Where do new codes come from?
[Active codes](/codes/active/) and official posts — never from invented tracker rows.
Should CBT diamond mail be listed here?
No. That is mailbox return value — see [launch rewards](/events/launch-rewards/).