Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add timestamps for Boots of Travel combination #2303

Open
Galvain opened this issue Jan 5, 2021 · 10 comments
Open

Add timestamps for Boots of Travel combination #2303

Galvain opened this issue Jan 5, 2021 · 10 comments
Assignees

Comments

@Galvain
Copy link

Galvain commented Jan 5, 2021

In match info there is no timestamp for Boots of Travel 1 or 2 combining.

@howardchung
Copy link
Member

What combining are you referring to? The item is considered purchased when the recipe is bought, right?

@Galvain
Copy link
Author

Galvain commented Jan 8, 2021

I'm referring to when the hero gets both combines both components in their inventory.

eg in: https://www.opendota.com/matches/5772722561/purchases

Last component for pudge's aghanim's scepter is purchased at 28:29, but the full item is combined in the inventory at 28:45

There is no timestamp for either the Boots of Travel 1 or 2 upgrades for the same hero.

@howardchung
Copy link
Member

Hmm, looks like there is no new item logged in the purchase logs when travels are created. We usually filter out recipe purchases, but might have to make an exception in this case

@builder-247 builder-247 self-assigned this May 12, 2021
@builder-247
Copy link
Member

builder-247 commented May 12, 2021

Hmm, looks like there is no new item logged in the purchase logs when travels are created. We usually filter out recipe purchases, but might have to make an exception in this case

Perhaps we should just add purchase event for the respective boots of travel?

@howardchung
Copy link
Member

How do you proposed we do that?

@builder-247
Copy link
Member

How do you proposed we do that?

Adding an else if contains boots of travel id here, and then replacing the recipe part of the ID

if (key.indexOf('recipe_') !== 0) {

@howardchung
Copy link
Member

hmm yeah I guess that would work. It might cause a duplicate event if we ever reparse old pro games?

@builder-247
Copy link
Member

hmm yeah I guess that would work. It might cause a duplicate event if we ever reparse old pro games?

What are you referring to?

I tested on a recent match and it works as intended, can do further tests as well.

@builder-247
Copy link
Member

On a second thought it might be better to just include the recipe, since there are many edge cases - making this more suitable for web to sort out.

@howardchung
Copy link
Member

What I mean is that old replays emitted a purchase event for boots of travel. So if we converted the recipe purchase to an item purchase we would see two purchase events

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants