Data Conflicts & Verified Data
Quick answerThis is the trust layer of the site: every claim that currently disagrees is registered here instead of being silently averaged. A conflict is not a bug — it is the honest state of a fast-changing game.
Registered conflicts (2026-09-06)
| Claim field | Dispute | State |
| Mutation multipliers (Crane / Bloom / Spirit Bloom) | Community % values disagree; none verified | Conflicting |
| Fuse upside | Sacrificed-income math differs across sources | Conflicting |
| Rift egg probabilities | No published table; reports vary | Unverified |
| Boss token shop costs | No confirmed price list | Unverified |
| Exact biome speed thresholds | Version-sensitive; screenshots disagree | Conflicting |
| Rare egg spawn windows | Approximate mechanic; cycles vary | Unverified |
Why conflicts are not resolved to a winner
PRD §9: a deterministic output requires MULTI_SOURCE or better. If we picked a 'winner' without verification we would be guessing for you — so conflicts stay visible and each side keeps its source.
Resolution path
- A live-verified, versioned report matches one side → that side flips to Live verified.
- A second independent match → MULTI_SOURCE; tools may now use it.
- Conflict stays open while sources disagree — tools answer VERIFY / HOLD.
Trust is not 'we are confident'; trust is 'here is the state, and here is what it would take to change it'.
Frequently Asked Questions
None until verified — the registry exists precisely because neither side has won. Verify in game or wait for a dated live report.
Use the Contact page with version + date + source.
Claims are never silently deleted; they are marked Stale or superseded with the new state.