About Anime Zero Wiki

An independent fan resource for the Roblox game Anime Zero. Not affiliated with, endorsed by, or operated by the developer (LY*) or Roblox Corporation.

What this site is for

A sourced alternative to copied lists

Anime Zero is a game with a lot of moving parts and very little documentation. The developer does not publish damage tables, drop rates or official rankings, and most of what exists online is copied from other lists. This site exists to be the version that shows its sources: every number is either something we tested or something clearly marked as community-reported.

Why pages look shorter

That is a slower way to publish, and it is the reason some pages here look shorter than the competition. A page with four verified facts is worth more than a page with twenty guesses.

How the codes list works

  1. A watcher checks the public code sources and the game's update signals every 15 minutes.
  2. Anything that looks like a new code is queued for review instead of being published.
  3. The code is redeemed once in game. Only codes that pay out reach theworking list, each with the timestamp of that check.
  4. Codes that stop working move to the expired table, where they stay for reference.

That is why every row on the codes page carries its own label: the difference between “we saw this” and “we proved this” is the whole point of the site.

How guides and tier lists are written

How guides are tested

Guides are written after playing the content, one page at a time, and they carry the patch they were written against. Tier placements come from dungeon runs where that is possible, and from community documentation where it is not — thetier list marks each row so you can tell which is which.

When numbers are missing

Numbers that the game does not publish, such as drop rates, are simply absent. Where a tool needs a figure the game does not give, like the pity thresholds in theroll calculator, the number is editable and the default is labelled as community-reported.

What we will not publish

The principles behind the pages

Label, do not guess

A code is listed the moment a public source reports it, with the source and the date attached. Only a string we have redeemed in game carries the verified label, so you can always tell a confirmed code from a reported one.

Label the source

Community-reported numbers — pity figures, synergy bonuses, tier placements — are marked as reported. We do not present someone else's test as our own.

Keep the history

Expired codes are moved to their own table instead of being deleted, so you can tell a retired code apart from one that never existed.

Correct in place

When a patch changes something, the page is edited with a note rather than quietly rewritten. A guide that silently changes its mind is worse than one that shows its work.

How to report a problem

Reporting a failed code

If a code on the list fails for you, say so in the community Discord with the code and the message the game returned. Failed codes are moved to the expired table with a note, and a code that was never real is removed from the unconfirmed list entirely.

Reporting a guide correction

Corrections to a guide are just as welcome. If a mechanic changed and a page still describes the old behaviour, that is a bug on this site, not in the game, and it gets fixed the same way.

Contact

TODO before launch: replace with the real contact address.

[email protected]

See also Privacy and Terms.