-
Notifications
You must be signed in to change notification settings - Fork 394
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
The matches are not counted (priority support fee) #3209
Comments
When was the Dota public match setting changed? We cannot currently backfill old matches from before this was set (but hope to be able to do so again if Valve fixes the GetMatchDetails endpoint) |
No, we opened the account before matches |
We've investigated this issue and new matches appear to be populating correctly. |
And what we can do with the old matches? Try to redownload the page? @howardchung |
As mentioned already there is currently no way to backfill these matches. We are looking into alternative solutions if Valve does not fix the endpoint in the future. |
But we have several issues |
I hope you can fix this asap. |
Current Behavior
Case 1: had the match at 17/09 but at OpenData it doesn’t showed at all. The account is opened. But here we have nothing: https://www.opendota.com/players/202126933. What you can advise to do? Attached the screenshot as a prove of the made match
Case 2: also played the match but it didn’t count. Account is opened. https://ru.dotabuff.com/matches/7938885479. But we can see the matches here: http://api.steampowered.com/IDOTA2Match_570/GetMatchHistory/v1/?key=F72B910F69EF897210FC4C18C9AB0426&account_id=297569660. How to count them at opendota? Tried to redownload - didn’t work
Expected behavior/code
Case 1: if i play match it counted at opendota
Case2: if i play match it counted at opendota
Console Output
Case 1: will be able to send this info a bit later
Case 2: the same
Environment
Possible Solution
Additional context/Screenshots
Case 1: attached (first)
Case 2: also attached
(second third fourth)
The text was updated successfully, but these errors were encountered: