Trends for item purchase time

[dartharaknus]

Item timing trends might be possible, but we need to think about how to do it. Each player_cache currently has some fields tracking item purchase times per match. We could extract a particular item from each and plot that, I guess.

Example:
https://api.opendota.com/api/players/88367253/matches?project=purchase_time&project=purchase&limit=10
Note that purchase_time is the sum of the purchase times. We can divide by the key in purchase to get the average purchase time. Typically what the user expects to see is first_purchase_time, so this might be messed up if the user has multiple purchases of the same item in the same match.

[howardchung]

They already are?

[dartharaknus]

Hmm.. There was some feedback on this in reddit. I forgot what exactly it was though.

[howardchung]

In that case, reopen if you remember what it is :)

[dartharaknus]

Such that it would show trends per role as well as trends per hero. Per hero there are also a lot of other interesting things that could be added to trends such as skill builds and item builds and average timings to reach them.

That was the reddit comment.

[howardchung]

Per role/hero I think is satisfied by applying a filter.

Skill builds are non-numeric so I'm not sure how they could be plotted on a graph.

Item timing trends might be possible, but we need to think about how to do it. Each player_cache currently has some fields tracking item purchase times per match. We could extract a particular item from each and plot that, I guess.

Example:
https://api.opendota.com/api/players/88367253/matches?project=purchase_time&project=purchase&limit=10
Note that purchase_time is the sum of the purchase times. We can divide by the key in purchase to get the average purchase time. Typically what the user expects to see is first_purchase_time, so this might be messed up if the user has multiple purchases of the same item in the same match.

[dartharaknus]

I will leave you to create/open issues for that comment.

[howardchung]

I'll just reuse this one and rename it