CODLOCKERHow We Verify
Every number on CODLOCKER traces to one of three sources, in order of preference:
1. The player themselves. Most settings come directly from a player's own Twitch channel — either shown on stream or via the chat commands (!sens, !fov, !controller, !deadzone) their own bots answer with. Nothing is closer to the source than the player's account publishing their own numbers.
2. Official league data. The Call of Duty League publishes select player settings, including button layouts. Where the league has published a value, we use it and mark it accordingly.
3. Event broadcasts and interviews. Settings visibly confirmed on official broadcasts or stated by the player in interviews.
What we never do: guess, copy from unsourced lists, or fill a blank with a plausible number. A page showing a dash means we don't have a verified value — full stop. The Verified badge means the page's data came from the sources above; Unverified marks community-reported values still awaiting confirmation.
Pros change settings mid-season constantly, so every player page carries a last-updated date. Spot something stale or wrong? Tell us — corrections with a source (clip, VOD timestamp, stream link) get fixed same-day.
Why a value can be missing
A dash means no source we accept has published that field for that player. About a third of the controller records here sit that way, usually because a pro has shown sensitivity and field of view on stream but never opened the deadzone submenu on camera. Filling those with a league average would make the page look complete and make it useless, so they stay empty.
The same rule governs partial captures. Where a stream overlay, webcam or alert covers part of a menu, the covered field is marked rather than inferred from the rows around it.
Reading a capture date
Every populated section carries the date the values were seen and the game they were seen in. A sensitivity captured in Black Ops 7 and one captured in the Modern Warfare 4 beta are different claims about the same player even when the number is identical, because there is no guarantee the aim curves behave the same way across titles.
Pros also change settings mid-season, often after a bad event. A page dated four months ago is not wrong, but it is old, and the date is there so you can weigh it yourself instead of assuming everything on the site was checked this morning.
Hardware is described, not guessed
Controller entries are the field most often reported wrongly elsewhere, because two different things get collapsed into one name. A builder is the company that assembles the pad — Battle Beaver, SCUF, Demonwork. A board is a component fitted inside it, and a Marius board is what gives a controller native 8 kHz polling. A pad can have both, one, or neither, and calling a controller a “Marius” says nothing about who built it.
We record them separately for that reason. Where a team is sponsored by a builder, the whole roster is listed on that builder's pads and the entry says the source is the sponsorship rather than an individual capture, so you can tell the difference between a player who showed the pad and a player whose team supplies it.
Corrections
A correction needs something checkable attached — a clip, a VOD with a timestamp, a stream link, a league post. With that, the change goes up the same day and the page’s updated date moves. Without it we cannot use it, however confident the report is.
Send anything you find to the contact page. A report that a value has gone stale is as useful as one saying it is wrong.