How Droidex Verifies Game Data

Evidence labels

Officially announced

A mechanic or change appears in a developer announcement.

Game reference

Game mechanics, rewards and prices listed in Droidex for the stated version.

Verified in game

The Droidex team observed the value or behavior in the live game.

Calculated

The result follows from visible inputs and a stated formula.

Community reported

Players reported the behavior, but direct verification is incomplete.

Not confirmed

The evidence is incomplete, so Droidex does not publish a guessed value.

Review and update process

1. Record the latest live version separately from the newest version fully reviewed across shared content.
2. Identify pages and dataset fields affected by each update.
3. Correct the shared source data, visible page, crawlable HTML, and regression tests together.
4. Publish a page-specific review date, version, and evidence label.
5. Keep unknowns explicit and add a correction note when a factual change matters to player decisions.

What the labels prevent

A precise number should never look more certain than the evidence behind it. Official announcements establish that a change was stated, direct observation establishes what the current game displayed, and a calculation establishes only the result of its published inputs and formula. Community reports remain reports until the behavior is reproduced.

Not confirmed means Droidex leaves the value unknown. It does not mean zero, impossible, or false. When a later review resolves the question, the shared data, visible page, crawlable HTML, and regression checks are updated together.

Current review scope

The latest monitored game version is recorded separately from each page's review label. Monitoring a new update does not silently claim that every older guide has been rechecked. Material corrections receive a page-specific review timestamp and retain the evidence label that supports the change.