Methodology
This site exists because the alternative — confident rankings with no evidence behind them — is worse than useless. Here is exactly what we do.
Verified as of ·Patch launch1. Nothing is invented
If we cannot source a stat, it is null in our dataset and renders as “unverified” on the page. Our build fails if a cookie asserts a game fact without citing at least one source. That check runs on every commit.
2. Every ranking shows its reasoning
A tier grade is only publishable alongside a written justification and a verification date. This is enforced in code, not by good intentions — a graded cookie with no reasoning fails the build. Currently 70 of 71 cookies carry a grade.
3. Confidence is labelled
officialOfficial sourcecorroboratedCorroborated by 2+ sourcessingle-sourceSingle source — treat with cautionunverifiedUnverified
“Corroborated” requires two independent source hosts. The build rejects the label otherwise.
4. Where we disagree with other sites
The class system is genuinely contested. We publish Charge, Ranged, Tank, Support and Magic. Reports of the official promotional video instead describe Vanguard, Defender and Shooter — plausibly alternative names for the same front-line, tank and back-line roles.
Where the two systems point at different answers for a specific cookie, we set that cookie's class to withheld rather than picking the one we like. Grapevine Cookie is the clearest case: one roster calls it Support, the promotional video shows a Shooter. We would rather show you the disagreement than hide it behind a confident label.
5. Other people's tier lists are quoted, not adopted
Some cookie pages show a community grade from an external tier list. That is reproduced with attribution as a reference point — it is not our ranking, it uses a different scale, and the sources behind it publish no evidence for their placements. Our own tier stays unranked until we can justify it ourselves.
6. Corrections
Found something wrong? Every page lists its sources so you can check our work. Corrections backed by a primary source — an in-game screenshot, an official post — get applied and the verification date bumped.