FAQ / Data Caveats / Attribution
Quick answers to common questions about coverage, updates, and data quality.
FAQ
Where does the data come from?
Public tournament data from TopDeck.gg.
How current is the data?
Daily refresh with a rolling update window.
Why is my latest event missing?
Events only appear once they are completed and published.
Why are some commanders missing?
Decklists only appear when organizers enable "Show Decks"; we use deckObj when available.
Why do my stats differ elsewhere?
Filters, missing rounds, and organizer settings can change aggregates.
How do you handle duplicate player names?
We use a hybrid identity resolution flow with user confirmation.
Data Caveats
Incomplete rounds data
Some events omit rounds or table data, which affects seat order and rival stats.
Why it matters: player trends can look softer or stronger than reality.
Decklists are optional
Decklists only appear when organizers enable "Show Decks" and after events end.
Why it matters: commander history can be partial or missing.
League win rates vary by field
Some events use a successRate field instead of winRate.
Why it matters: comparisons across formats need normalization.
Player identity is inferred
We resolve duplicate names using context and confirmation, but errors can happen.
Why it matters: mis-links can skew aggregate stats.
Organizer settings affect visibility
Discord tags and some metadata are only present when enabled by organizers.
Why it matters: missing fields do not imply missing participation.