-
Notifications
You must be signed in to change notification settings - Fork 16
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
Plays and Success Rate in get_beatmaps #17
Comments
Definitely feasible. What's the use case? |
One rank system is impossible to satisfy everyone, so my friend @hypercross wanted an API so that players can set up their own ranking rules. I searched and saw there's really an API so I might try to implement hypercross's idea. This custom rank need not to be updated frequently (let alone real-time), so I won't need a very high rate. Also I'd like to consider user-rating so I can exclude old and low-quality maps while not missing awesome maps like this(http://osu.ppy.sh/s/13223). |
I can't really say I support this idea, and am not sure how the information you provided would help. |
lol @ibicdlcod I think that's more of a rant than serious suggestion... So, formally, I want to say that creating an ultimate ranking system is equivalent to solving the cake-cutting problem. It's just impossible. Especially as we have a five or six year old database that we have to be compatible with. And that's not the developer's problem. In fact, the effort of trying to provide a "fair" performance assessing system has distracted too much of the developer's attention. The developer has been a coordinator for too long. If people have rants about FL being underpowered, someone else can listen and make a FL-focused ranking, and the popularity of that ranking will faithfully reflect how people value a FL play. The developer can simply provide the functionality for the coordinators, he doesn't have to guess through a whole bunch of hefty math and ship a brittle ranking system that he has to fix every now and then. I personally doubt how Success Rate can help in ranking players, but as someone might care, I think it's fair enough to ask for it in api.... I actually prefer the former Ranking Score system over pp. It reflects how dedicated the player is, instead of how good he is. As a casual game that is a more proper number to be written on the player's face imo. |
I think you have completely missed the development of pp and ppv2. If you wish to make your own ranking system, you may do so by making your own game :). I plan on continuing to refine the one in osu!. Please don't make assumptions about my development process and history :). |
On the actual topic at hand, all of this info is available on the beatmap page, so why not in the API response? |
The API is meant for use for external services. The information on the beatmap page is for consumption of osu! users. Very different purposes. |
I think you misunderstood my intent: my rank (if it ever comes to existence) will solely be advisory, not assuming authority over pp (on the other hand, osu!tp(http://osutp.net) encourages players to display it on his/her userpage, and a lot of high-ranked players did). Note that I sincerely believe a rank calculated from all available data will be better than a rank calculated from only top50—As a college student majored in statistics I’m actually willing to give feedback and help improve ppv2 (but ppv2 testing thread is temporarily locked). To @hypercross: score rank is NOT an accurate reflection of player’s dedication, it favors easy and long maps over harder and shorter maps (combo is often the primary source of score), and focusing on one map (to improve skill and get full combo and/or accuracy) will have little reward. Total score may be better, but it’s already reflected in “level” which is also “written on the player’s face” and easily verified in multiplayer. Please don’t rush to define what osu! is. |
ppv2 is going to be completely open, so you are welcome to provide feedback in that way. |
Is it feasible?
The text was updated successfully, but these errors were encountered: