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

New parameter for /get-user : type=rank #181

Open
Stalzak opened this issue Apr 15, 2017 · 2 comments
Open

New parameter for /get-user : type=rank #181

Stalzak opened this issue Apr 15, 2017 · 2 comments

Comments

@Stalzak
Copy link

Stalzak commented Apr 15, 2017

Hey, how about allowing to select a user not by name or id, but by their current rank ? I saw a lot of guys asking for leader boards, top x players or other whatnots, but that might be an easy solution.

I'm trying to build a side project in which I'd draw a line chart of pp versus rank.
Wait was that proper English ? I don't know, I found the saying on Wikipedia. Anyway, the idea would be to build a graph showing how much pp is worth ranks as of now, and allowing to pinpoint users and ranks on it. It would be the representation of the figurative mountain the user's badges talk about, and that'll allow to see how much pp you need to get to a given rank, or the skill gap between two users and so on.

For that, I would need the ability to get user information at a given rank. Say, if I want to see how much pp has the guy currently #10000, I would use u=10000 and type=rank. Would that be possible ?

(By the way, I just looked into GraphQL since an issue talking about a only parameter got linked to that. Are you using that peppy ? Since I might need to do a lot of request once every day to build the graph, I might as well only ask for what I need)

@jxu
Copy link

jxu commented Jan 22, 2018

Agree 100%. I speculate it's possible to get significantly more information using country rankings (the 10,000th US player is rank #63,604, and theoretically going through all leaderboards for all 234 "countries" should get everyone) but this should really be in the API.

@jxu
Copy link

jxu commented Jan 31, 2018

#102

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

2 participants