Editorial policy
A fact needs two independent public sources before this site treats it as settled. One source stays labeled as one source. A missing number stays blank.
What counts
Public web pages, store listings, official help articles, patch posts, YouTube titles and descriptions, and press write-ups. An automated search summary is a clue, not a source. Multiple pages from the same publisher count as one independent source. The game site, official help center and Azra studio site belong to one publisher; the roster separately shows evidence-page totals.
How a page is written
The first screen answers the query. Tables use a status column for the source count, such as “3 sources” or “New code · 1 source.” Dates of the reading sit in the source list. If Play says one score and the App Store says another, both rows remain. The editor’s note is in the first person and ends with a single limitation sentence. That sentence is the only place the page draws the boundary.
What we will not do
We will not host an APK, invent a pity rate, fill a reaction chart the help article does not name, or copy a single tier list that misspells a character. Code pages do not open with a disclaimer. When the active list is empty, the page reports the dated list snapshot and identifies older articles without predicting a release schedule.
Corrections: [email protected]. The code table is also re-read on a schedule from the three static lists named on the codes page.
Questions
Why are some cells empty?
No public source gave that value. An estimate would look like a fact.
How often are codes checked?
On a six-hour schedule against RallyCodes, GamingonPhone, and MuMuPlayer, plus a manual look at official news.
Who decides a conflict?
Nobody collapses it. Both claims stay, with their links.