How we test

Our method is the product. This page sets out how a number gets onto this site, and what has to be true before we call it verified.

1. Record first, every time

Every play session gets an ID before it starts. We note the game build, platform, mode, progress point and settings, and we record the session. While playing we log cash before and after each activity, purchases, unlocks, failed attempts, restarts and anything unexpected. Approximate timings are allowed in the log, but they are flagged and rechecked against the recording before anything is published.

Recordings stay private. We do not publish gameplay footage, game artwork, maps or audio.

2. One claim, defined precisely

Each finding makes a single claim: what the activity pays, how long it takes, what it requires. It states where timing starts and stops, the prerequisites, the progress point and any other conditions. Unknown values are left unknown — never estimated to fill a gap.

3. A person checks every run against the recording

A run counts only when a named reviewer has checked it against the original recording interval. That rule applies to everything, including events that software flagged for us: automated tools may suggest where to look, but they can never mark anything as observed or verified.

A run does not count if it was:

  • not reviewed against the source recording;
  • invalid (for example, a save was reloaded mid-run), and we record why;
  • performed under different conditions from the finding’s;
  • a re-export or re-watch of a run we already counted.

4. Independence is counted by recording, not by file

Two clips exported from the same playthrough are one source. To be verified, a finding needs at least 3 counted runs from at least 2 independent recordings. Corroboration by a second player is preferred, and we show how many players contributed.

5. What the labels mean

LabelWhat it takesHow it is shown
CandidateA raw event with a source reference. AI-extracted events always start here and cannot leave this state without a human reviewer.Not visible publicly.
Measured onceAt least one first-hand run that a human reviewer has checked against the original recording. No generalisation beyond those conditions.Visible, labelled "measured once", with the exact source conditions.
VerifiedAt least 3 valid, human-reviewed runs under consistent rules, from at least 2 independent recordings, with no unresolved contradiction. A separate player is preferred.Shown in comparisons and recommendations.
ContestedCredible conflicting evidence exists. We investigate and retest.Visible with a conflict warning; excluded from default comparisons.
Needs retestRelevant mechanics changed, or a game update has not been rechecked.Visible with a game-update or age warning; not ranked.
RejectedInsufficient provenance, prohibited rights, or false data.Not public. The reason is kept in the audit history.

6. The arithmetic

Every money figure is net of the in-game costs we recorded during that run.

net per run      = money gained − recorded in-game costs
hourly (if any)  = mean net × 3600 ÷ mean full-cycle seconds

An hourly figure is only published when all of the following are true:

  • the activity can be repeated for a comparable reward;
  • the finding is verified;
  • at least 3 runs recorded both net reward and full-cycle time, including travel, setup, waiting, cooldowns and failed attempts.

One-time missions never get an hourly rate. Turning a single payout into “money per hour” suggests a sustainable income that does not exist. Where an input is missing, the page says not established.

A change in on-screen cash is not automatically a reward. Purchases, transfers, retries and story events can all move the balance, so a reviewer attributes every change.

7. Listed prices

Prices are read from in-game shop and menu screens in our own recordings, then a reviewer checks each one against the recording. A listed price is what the game shows, not something we paid, so it is reported as a price, never as income. It counts as verified only when the same price appears in at least 3 sightings across at least 2 independent recordings. Sales, discounts and game updates can change prices, so we note when each was last seen. Charges we did pay, such as fuel or a road toll, are read from the change in on-screen cash and reported the same way, as a cost; the summary says which kind it is.

8. Minimum versus normal

The fastest time we achieved is not the time a typical player should expect. We report the median and the range, include failed attempts, and say who played.

9. Updates and corrections

Game updates can change mechanics. When a build changes something a finding depends on, the finding is flagged for retest and, if needed, marked “needs retest”. Every material change to a published number gets a dated revision that keeps the earlier value and the reason. Report a correction.