Anime Dice Roblox logo Anime Dice
HomeUnitsCharactersBest UnitsTier ListTraitsTrait Tier ListMutationsGradesLuckDice UpgradesUpgrade PriorityRebirthTowerTeam BuildingBeginner GuideMoney FastCodesGemsLucky SpinsUpdatesUnit CheckerTrait Reroll CheckerRebirth TimingData SourcesData ConflictsAbout 🌐 English🌐 Português (BR)🌐 Español (LatAm)

Anime Dice Data Conflicts

Anime Dice Data Conflicts
Direct answerWhen sources disagree, we do not pick a winner — we show both sides and label the fact as conflicting. This page is the public register of those disagreements. A fact here is not verified until one side is confirmed by the developer or live-verified in-game.
ConflictingGame phase: UPD 3 · fast-changing

Current conflicts

TopicClaim AClaim BState
Character rosterRoster X exists (tracker 1)Roster X does not exist (tracker 2)Conflicting — unresolved
Unit rarityRarity A is highest (tracker 1)Rarity B is highest (tracker 2)Conflicting — unresolved
Rebirth reward curveReward curve P (community)Reward curve Q (community)Conflicting — unresolved

Why we show conflicts

A guide that hides disagreement looks cleaner but lies. When the developer publishes no roster, a community table is a snapshot from one person's screen, not a fact. Showing both sides lets you weigh the evidence instead of swallowing a single unverified claim.

How a conflict gets resolved

  1. A developer statement settles it — becomes official.
  2. Live verification in-game settles it — becomes verified.
  3. One side loses support and the other gains it — becomes the working claim, still labelled.
  4. Otherwise it stays open, and we say so.

What resolved looks like

A resolved conflict disappears from this table and its winner moves to the relevant page with a verified or official label. Until that happens, treat both claims as unverified.

Frequently Asked Questions

Because with no official source, one answer would be a guess. Two labelled claims are more honest than one fake fact.
You cannot from the register alone — that is the point. Verify in-game or wait for a developer statement.
Yes, by developer confirmation or live verification. Resolved conflicts move to the relevant page as verified or official.

Sources & Verification