Battle Beaver is the most common named builder in CODLOCKER’s recorded controller sample. It appears in 18 of the 47 entries, compared with nine for SCUF.
That gives Battle Beaver twice as many recorded entries as the next named builder. There’s also a sizeable gap in the information: 15 controllers don’t have a confirmed builder.
| Recorded builder | Controllers | Share of all 47 records |
|---|---|---|
| Battle Beaver | 18 | 38.3% |
| SCUF | 9 | 19.1% |
| Sony / DualSense | 4 | 8.5% |
| Demonwork | 1 | 2.1% |
| Builder unconfirmed | 15 | 31.9% |
Among the 32 entries with a named builder, Battle Beaver accounts for just over 56%. Across all 47 records, its share is 38.3%. Both figures are correct, but they describe different groups. Nearly a third of the full sample still has an unconfirmed builder, which limits how precisely we can describe the wider picture.
Boards are not builders
That distinction becomes useful when you’re trying to understand a player’s setup. “PS4 custom” tells you something about the controller platform. “Battle Beaver” names a builder. “Marius” identifies a board. None of those descriptions, by itself, tells you the full button configuration, stick setup or modifications.
Even controllers from the same builder can be configured differently. Back buttons, trigger options and stick choices can change how a pad feels and how you use it. Matching the brand on a pro’s page doesn’t necessarily mean you’re holding the same configuration.
Popularity also leaves the reason for a player’s choice unanswered. Familiarity, available support, sponsorship and personal preference are all possible influences, but the count doesn’t tell us which mattered for any particular player.
Using the database for research
Start with what you want to change about your current controller. Do you want to jump without taking your thumb off the aiming stick? Would a different shape be more comfortable? Are you looking for a particular button arrangement? Those questions give the player records a practical use.
Battle Beaver leads the named entries in this sample. The individual profile details are where you can see whether a particular setup has the features you’re actually interested in.
Sources
- CODLOCKER settings database, 47 recorded controller entries. See How We Verify.
- Builder and board fields are recorded separately on each player profile.
CODLOCKER