A useful code page should tell you what is known, how it is known, and what still needs checking.
How we use sources
| Evidence | What it supports | What it does not prove |
|---|---|---|
| Official announcement | The developer published the stated code, reward, or event details. | That the code still works or that a future event has already started. |
| Successful game test | The code succeeded in the correct game on the recorded date and account. | That every account can redeem it, or that it will remain active. |
| Third-party report | Another publisher reported the information. | That we tested it or that the developer confirmed it. |
| Player report | A person described an experience that may warrant review. | Universal code status from one account's result. |
We use the correct Roblox game and its creator, Ball Battles Studio, to establish identity. Similar names are not a reason to merge two games' codes or mechanics.
What code labels mean
- Tested active: a recorded successful redemption supports the status. The date matters; it is not a permanent guarantee.
- Official, not tested: a developer source supports the code, but this editorial desk has not recorded a successful redemption.
- Reported, not verified: a third-party source exists. This is not an endorsement as a working code.
- Expired: sufficient evidence supports that the code no longer redeems. We do not infer this solely from an “already redeemed” result.
- Needs review: evidence conflicts or an earlier status is no longer reliable. The code is removed from the available list while it is reviewed.
Research candidates are not automatically promoted into a working-code list. An empty verified section is more useful than an invented verification claim. Reward amounts stay unspecified when the evidence does not establish them.
Three dates, three meanings
Content updated means a substantive page change. Source checked means the cited source was reviewed. Last successful test means a redemption actually succeeded in the game. A later unsuccessful check does not overwrite the date of the last successful test.
Checking a page without finding a change does not make its content new. We do not create a new monthly code page, change dates automatically, or add a “new” label to an old code to imply freshness.
Guides, rewards, and events
Guides distinguish first-hand testing from source-reported instructions. We do not present another publisher's screenshots as our own. Planned event times retain their time zone and remain labeled as announcements until evidence supports a launch.
The reward planner calculates from the values entered by its user. Its totals are estimates based on those inputs, not a statement of account eligibility or a promised payout.
Corrections and responsibility
The Anime Ball Battles Codes editorial desk is responsible for these pages. To challenge a claim, send the page URL and supporting evidence. We review the underlying source, correct supported errors, and record material corrections in the change log.
This is an independent resource. There are no advertising placements or sponsored rankings on the site at launch. Any future commercial relationship affecting content should be disclosed where relevant.