-
Notifications
You must be signed in to change notification settings - Fork 301
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 minRank
and maxRank
query parameters to /publicMatches
#2662
Conversation
minMmr
and maxMmr
query parameters to /pubmatchesminMmr
and maxMmr
query parameters to /publicMatches
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure the mmr field isn't being updated anymore, average_rank
should be used instead
Oh, ok. I was just going off the response from: https://api.opendota.com/api/publicMatches In that case, avg_mmr should probably be removed from the response? To avoid confusion. Or, avg_mmr should be implemented again? Is there a reason it's not being updated anymore? |
minMmr
and maxMmr
query parameters to /publicMatches
minRank
and maxRank
query parameters to /publicMatches
@howardchung I notice the indenting in the spec description causes it to render like this: Included a fix for that |
Adds
minRank
andmaxRank
query parameters and usesavg_rank_tier
field in public_matches to filter results.