Open emb417 opened 1 month ago
The VPC API returns scores for various versions of tables using the table id. The VPS json file includes the table ids as a nested object (table files) within a larger "table" object. The larger table object includes table files and b2s files, plus other metadata specific to this named table.
The plan:
The reason for deduplicating is if someone played version 1 of medieval madness, we shouldn't expect them to play versions 2 through 7 to count towards the overall goal of playing all tables. The more difficult problem to solve is when tables go through revisions...does the counter reset? Do all revisions count towards 100%?
Show data around players high score corner tables.
Split from #15 which has background to this issue.