ceari
commented
10 years ago Regarding 4): I'm not sure if it's worth it when there's a web page out there that tracks that already: http://wotcs.com/clan.php?wid=500014725 But it might be interesting to implement it to combine it with data known from replays, e.g. track the tank locking duration. Anything else you can think of in that direction? It probably would be best to just get the data from the WG API then.
1), 2) and 3) should be fairly straight-forward since all the information is basically already available from the replays. The available data for each player looks like this: https://gist.github.com/ceari/5e0529ee2de64c68c586 https://gist.github.com/ceari/541aba4dc1d7468e06ba
From a technical perspective it might be worth it to store that information in a separate database tables for performance instead of having to decode the JSON every time in Python. But maybe that can wait until it actually becomes a problem.
Could you please try to come up with some UI mockups or ideas how the data should be shown?
Gucioo
I could elaborate on it but how do you feel with the implementation of tanks to the tracker?
ATM my perspective: 1) track who played which tank from "our team" 2) track his stats on that tank (sum them to the global stats) 3) track the tanks of enemy team, group them per map/date. We don't need individual stats and to remember who played which tank but it might be useful to see that in 30 battles on Westfield, PSQD had 100x110E5 with the average of 8 of them per battle (don't check my math here ;) 4) Show all tanks in clan (based on the replays if easier to do rather than thru the API/deduction) - maybe players should edit their profiles and add tanks?
What do you think?