Official
Roblox experience metadata, creator-controlled destinations, badge trigger text or another developer-owned surface.
Sources, Confidence & Corrections
Every page should tell you whether a value is official, publicly reported or calculated. This policy explains how gaps, conflicts and dated game data are handled without exposing private research notes.
Reported
A public guide or community record. Useful for planning, but labeled and revisited when the game UI disagrees.
Modeled
A transparent formula using values you enter or a clearly labeled reported preset. It is not hidden game logic.
Conflict rule
Disagreement stays visible
Forsaken and Draconic are good examples: newer public tables report pity while older supplied text says none. The traits page flags the conflict and the calculator lets you set either behavior.
Null rule
Unknown is never zero
Shadow's missing key-material field and incomplete unit DPS values remain Unknown. A missing number must not make a recipe look cheaper or a unit look weaker.
Freshness
Dates are part of the answer
Code status is checked frequently during launch; database and link status are reviewed on a weekly cadence or when the game changes.
Corrections
Open contact and corrections →Send the exact page and evidence
Include the page URL, the claim, the corrected value, where it appears publicly and the date you checked it.
FAQ
Data questions
What does Official mean on Anime Expeditions DB?
It means the claim comes from a Roblox or developer-controlled surface, such as the experience metadata, creator group or official badge record.
How are conflicting Anime Expeditions values handled?
The page shows the current reported value, names the disagreement in plain language and keeps inputs editable. Unknown fields remain Unknown rather than zero.