Methodology
Every claim on GTADB carries a visible evidence rating and traces to a record in the source database. This page is the contract behind those badges.
The evidence ladder
- Officially confirmed
Explicitly named or described by Rockstar Games or Take-Two — site pages, Newswire posts, official store/media publications.
- Seen in official footage
Clearly visible in Rockstar-published video or imagery, described without interpretive leaps.
- Identified
Strong identification built on official evidence — e.g. figures carried consistently by announcement-day coverage of an official reveal.
- Probable
Strong evidence exists but identification isn't definitive — e.g. a mechanic described by press previews of official footage without first-party wording.
- Unconfirmed
Community or speculative claims without sufficient evidence. Rarely recorded at all; never presented as fact.
- Debunked
Previously circulated claims contradicted by stronger evidence — kept visible so the record corrects the rumor.
Rules we hold ourselves to
Sources. First-party Rockstar/Take-Two publications are the backbone. Press is cited only for announcement-day details Rockstar released but didn't restate in writing (like US pricing), and is always marked as press. The 2022 development leak and other stolen material are never sources — early, unrepresentative, and wrong to platform.
Naming. We never invent names. A vehicle Rockstar hasn't named either stays out of the database or enters with an honest descriptive identifier and a sub-official rating — certainty is never fabricated.
Corrections. When a fact changes or we get one wrong, the record is corrected, its verification date updated, and the change logged publicly in the discovery feed — the database's audit trail. We don't silently rewrite history.
Tooling. GTADB is researched and maintained with software assistance (including AI tooling) for cataloguing and cross-referencing, but no fact is published without a citable source — the evidence bar applies to the workflow, not just the output.
Report an error. Spotted something wrong or missing a source? Email corrections@gtadb.gg with a link to the record and, ideally, the source we should be citing.