odota / odota/core

Improve item timing data aggregations (histogram?)

Open
#441 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
TypeScript
Stars
1.6k
Forks
318
Avg merge
5d 16h
Merged PRs (30d)
3

Description

Was directed here by one of your guys on reddit, no idea how this place works and created an account just to type this out so forgive me if I'm doing something wrong here. To my suggestion;

The only item timing data for all games collectively (which can of course by search on a per hero basis among a couple of other options) that is available is an average item time, and the number of times that item has been bought. If an item is ever bought in a different order for a certain hero then that average item timing becomes useless in terms of trying to hit targets for items in game.

What I'm after is item timings where the only data points collected would be the ones specified by some sort of similar drop down menus to the ones currently used in other areas.

This could be done in a number of ways, taking the item example of orchid:

-Able to select items that the player already has when orchid is bought. For example ticks to 'power treads and bottle' would only select orchid timings for when the player has only these items. Perhaps items such as tango and stick could have a yes&no option whereby it wouldn't matter whether these items are owned or not in terms of what data points are selected

-Able to select items based on the cost of the current items owned when the orchid is bought. Here you would have a maximum and minimum value to be selected.

Graphs of how these item timings vary over time would also be great.

This would allow for accurate data to be used in item timings, as well as comparisons between item builds as to what helps best in networth progression of a hero - whether item timings are faster with phase boots over treads for example.

Ty for your time :)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the existing item timing aggregation and the current hero/item search and dropdown flows described in the issue. Define the data filters, comparison graphs, and completion criteria with maintainers first; no file or test is named, so the scope is not ready for a newcomer.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
analytics, data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.