Known limitations
The honest list: what Clashest does not track yet, and why.
Honesty cuts both ways: here is what Clashest's data can and cannot tell you today.
2v2 is not ingested
Only 1v1 battles enter the stats corpus. In 2v2, two players share towers, so a single deck's "win rate" would be half someone else's game. Live pages (like a player's battle log) still show whatever the API reports.
Tower troops are not backfilled
A battle's tower troop is stored only when the API reported it at ingestion time. Older battles without a recording are never guessed — which means tower-troop shares cover only the battles that recorded one.
The battle-log window
The API exposes roughly the last 25 battles per player, so the corpus grows forward from when tracking began. Long-gone metas are not retroactively reconstructible.
Coverage skew
The tracked pool seeds from top-ranked and searched players and snowballs through their opponents. Coverage is strongest near the top of the ladder and broadens over time.
Event-mode samples
Limited-time modes run for days, not months. Their stats are real but small — check the battle counts.
API availability
When the official API rate-limits or is briefly down, live pages say so and stats pages serve their latest computed aggregates. Nothing is silently substituted.