It's been a while since I posted something controversial seriously, but here we are.
-------------------------------------------------------------------------------------
This proposes a new way to determine beatmap ranking. This does require big changes in osu! infrastructure, and by no means simple nor easy. The point is to discuss this as a possible alternative and what this might result in. TL;DR:-------------------------------------------------------------------------------------
The current ranking model is doomed to fail, and we observe how it is failing every month or so. Yes, maps are produced, but at the expense of a lot of unneeded headaches and drama. Mappers prefer if they can get their maps ranked despite issues and players prefer that they have new quality maps to play. The method used to balance this out right now is just too chaotic.
The only solution to this is abolish the source of subjective judgment responsible for deciding which map gets to pass and which doesn't. There needs to be a system that is not subjective and is always consistent. The ranking criteria is such system, but it is interpreted by people, which introduces layers of subjectivity. There just needs to be a thing coded up that tells if the map can or cannot be ranked, which would be specified by the ranking criteria. The ranking criteria guidelines would need to go as it is impossible to interpret them without subjectivity. It is impossible to code guidelines without getting differing opinions regarding those person-to-person on various maps. They are not be needed anyway as you will see.
The next source of failure is all the arguing between modders and mappers that happen in the modding sections. Currently you need mods to get the beatmap ranked, which often introduces disagreements between how things should be done. For the map to be of "high quality" it needs to agree with a lot of people, and this often sacrifices mapper's creative intentions in the process. I can't say that there is a way to fix that completely, and I almost sure there is not, but most of it can be redirected into other points of judgments and decisions which can significantly reduce the arguing and allow mapper creativity to stay intact.
To accomplish this, all maps would need scoreboards from the get-go. So every map is basically loved. People who like the map are likely to not delete it and possibly put it up in multi to share it with others. This is how a map can get popular and gain a bigger scoreboard. When the scoreboard for a certain difficulty is sufficiently big enough, it shows people like the difficulty and it becomes almost becomes ranked if the ranking criteria are met. Almost, because the only other thing that should prevent maps from getting ranked are issues on the moddingV2 page. The mapper has the freedom to address mods by agreeing and fixing stuff, or by disagreeing. Closing all the issues would then trigger the ranking of the map.
The only thing the automated system can't cover is the metadata. That needs to be checked and approved manually. So a dedicated group for checking metadata needs to be created. Also, updating metadata right now would essentially be changing the map. It is best to avoid that as much as possible, so there needs to be a separate file for metadata. This file then can be changed to apply to the entire beatmapset without affecting the difficulties themselves. If there has been a change to the metadata online, the client would automatically grab it. An issue is automatically created when a map is triggered for ranking. This serves as a notification to the mapper and the relevant parties. The metadata checking group would receive this as a new issue on their list to go check and provide the correct metadata, make sure the beatmap is not infringing on copyright, and is suitable for all ages.
Since the entire thing is based on scores, wiping scoreboards when the beatmap qualifies for ranking is unfavorable. The issue of wiping a scoreboard should be only relevant if a difficulty is updated. However, if the ranking status is dependent on number scores, mappers will opt to not update the beatmap to not trigger a scoreboard wipe. The component needed to solve this is beatmap version control. It would allow to play past versions of the map and not worry about wiped scoreboards. While only the latest version would be suitable for ranking, ranking status should be determined by the number of unique users on scoreboard for all versions of the difficulty. Otherwise, if you consider just the latest version, it is no different than the wiped scoreboard scenario. To avoid replays taking up too much space, perhaps make replays for past versions available if it is top 50 and is a good score, where what qualifies as a good score will need to be discussed.
Finally, we have the ranking criteria management. Further changes to the ranking criteria are determined when a ranked map is identified to not be suitable for rank by the players. Yes, a ranked map and the concept of this is important. The players need to be sufficiently unhappy about it to warrant a scoreboard wipe. It will no longer be a decision where one can wave a finger and propose this and that without having something at stake. When such event does occur, QATs come in to identify whether the map is truly not suitable and proceed to compose a rule in a manner such that it can be translated in to code. For example, if the criteria mentions "blanket sliders", that would require a technical definition that describes such sliders. The code should be tested against all relevant maps to make sure it is consistent with maps acceptable for ranking. Then there would be a wait period where players would see if the new rule is what is indeed desired. New rule gets merged in, and gets applied such that AIMod and ranking trigger can then use it.
The last bit is to properly fix pp so the map don’t wreak havoc on the leaderboard. This is done by fixing star rating or implementing a new skill worth system that is good enough to remove fears of extremely overrated and underrated maps. This is easier said than done, I don’t know how it will be done, and this is a subject for an entirely different thread.
-------------------------------------------------------------------------------------
FAQ:
This proposes a new way to determine beatmap ranking. This does require big changes in osu! infrastructure, and by no means simple nor easy. The point is to discuss this as a possible alternative and what this might result in. TL;DR:
- Replace BN with an automatic system capable of determining whether a beatmap is suitable for ranking according to the ranking criteria rules
- Allow beatmap metadata information to be in a separate file, allowing change after ranking
- Create a group for people who do metadata checking, and verify DMCA and NSFW status of the map, that is notified of any unchecked maps which become ranked
- Remove guidelines in ranking criteria and only keep rules
- QAT's role would remain mostly as is now - Managing ranking criteria, unranking maps that many feel should not have been ranked, and identifying what needs to change in the ranking criteria to prevent more of such maps being ranked
- Make every beatmap loved - so beatmap popularity can be accurately reflected via how many scores are on them
- Make individual difficulties automatically go to ranked when it reaches a certain amount of scores
- Beatmap versioning system - so beatmaps can be updated without scoreboard wipes, allowing players to play older versions
- Fix star rating
The current ranking model is doomed to fail, and we observe how it is failing every month or so. Yes, maps are produced, but at the expense of a lot of unneeded headaches and drama. Mappers prefer if they can get their maps ranked despite issues and players prefer that they have new quality maps to play. The method used to balance this out right now is just too chaotic.
The only solution to this is abolish the source of subjective judgment responsible for deciding which map gets to pass and which doesn't. There needs to be a system that is not subjective and is always consistent. The ranking criteria is such system, but it is interpreted by people, which introduces layers of subjectivity. There just needs to be a thing coded up that tells if the map can or cannot be ranked, which would be specified by the ranking criteria. The ranking criteria guidelines would need to go as it is impossible to interpret them without subjectivity. It is impossible to code guidelines without getting differing opinions regarding those person-to-person on various maps. They are not be needed anyway as you will see.
The next source of failure is all the arguing between modders and mappers that happen in the modding sections. Currently you need mods to get the beatmap ranked, which often introduces disagreements between how things should be done. For the map to be of "high quality" it needs to agree with a lot of people, and this often sacrifices mapper's creative intentions in the process. I can't say that there is a way to fix that completely, and I almost sure there is not, but most of it can be redirected into other points of judgments and decisions which can significantly reduce the arguing and allow mapper creativity to stay intact.
To accomplish this, all maps would need scoreboards from the get-go. So every map is basically loved. People who like the map are likely to not delete it and possibly put it up in multi to share it with others. This is how a map can get popular and gain a bigger scoreboard. When the scoreboard for a certain difficulty is sufficiently big enough, it shows people like the difficulty and it becomes almost becomes ranked if the ranking criteria are met. Almost, because the only other thing that should prevent maps from getting ranked are issues on the moddingV2 page. The mapper has the freedom to address mods by agreeing and fixing stuff, or by disagreeing. Closing all the issues would then trigger the ranking of the map.
The only thing the automated system can't cover is the metadata. That needs to be checked and approved manually. So a dedicated group for checking metadata needs to be created. Also, updating metadata right now would essentially be changing the map. It is best to avoid that as much as possible, so there needs to be a separate file for metadata. This file then can be changed to apply to the entire beatmapset without affecting the difficulties themselves. If there has been a change to the metadata online, the client would automatically grab it. An issue is automatically created when a map is triggered for ranking. This serves as a notification to the mapper and the relevant parties. The metadata checking group would receive this as a new issue on their list to go check and provide the correct metadata, make sure the beatmap is not infringing on copyright, and is suitable for all ages.
Since the entire thing is based on scores, wiping scoreboards when the beatmap qualifies for ranking is unfavorable. The issue of wiping a scoreboard should be only relevant if a difficulty is updated. However, if the ranking status is dependent on number scores, mappers will opt to not update the beatmap to not trigger a scoreboard wipe. The component needed to solve this is beatmap version control. It would allow to play past versions of the map and not worry about wiped scoreboards. While only the latest version would be suitable for ranking, ranking status should be determined by the number of unique users on scoreboard for all versions of the difficulty. Otherwise, if you consider just the latest version, it is no different than the wiped scoreboard scenario. To avoid replays taking up too much space, perhaps make replays for past versions available if it is top 50 and is a good score, where what qualifies as a good score will need to be discussed.
Finally, we have the ranking criteria management. Further changes to the ranking criteria are determined when a ranked map is identified to not be suitable for rank by the players. Yes, a ranked map and the concept of this is important. The players need to be sufficiently unhappy about it to warrant a scoreboard wipe. It will no longer be a decision where one can wave a finger and propose this and that without having something at stake. When such event does occur, QATs come in to identify whether the map is truly not suitable and proceed to compose a rule in a manner such that it can be translated in to code. For example, if the criteria mentions "blanket sliders", that would require a technical definition that describes such sliders. The code should be tested against all relevant maps to make sure it is consistent with maps acceptable for ranking. Then there would be a wait period where players would see if the new rule is what is indeed desired. New rule gets merged in, and gets applied such that AIMod and ranking trigger can then use it.
The last bit is to properly fix pp so the map don’t wreak havoc on the leaderboard. This is done by fixing star rating or implementing a new skill worth system that is good enough to remove fears of extremely overrated and underrated maps. This is easier said than done, I don’t know how it will be done, and this is a subject for an entirely different thread.
FAQ:
- Q: Then maps like Levan Polka 20 second spinner will be ranked. How is that quality?
A: Then specify it in the ranking criteria. It serves to filter out shit like that. Simple fix would be to add the minimum required note to spinner ratio
Q: Rip CtB and Taiko. There is no chance they would get as popular as other gamemodes
A: The threshold to which the beatmap becomes ranked will need to be gamemode dependent
Q: What about NSFW maps? How do you put that into code?
A: You don't. Either metadata checking group stops them or you report inappropriate content
Q: What about plagiarized maps or maps with unapproved skins?
A: Metadata checking group stops them or you report them
Q: What happens to loved section?
A: The maps that satisfy ranking criteria are ranked. The rest remain equivalent to loved like everything else.
Q: This is a horrible idea. Maps will be ranked so rarely
A: I doubt that will happen because popular mappers will always bring about their new maps and people would generally flock to play them. If it does for Taiko or CtB, you got map leaderboards, which are everywhere. You are only missing pp, which is flawed to begin with compared to now. It's not the end of osu!
Q: What if I don't want my map to be ranked?
A: Just make an issue on moddingV2 page, halting the the process
Q: So the mapper can now just ignore any issues and trigger ranking? Wtf?
A: Actual issues will not allow the map to by the automated system that checks whether the beatmap passes the ranking criteria. If the map is ranked before metadata is fixed, it can still be fixed while ranked. For other opinionated issues, it's mapper's discretion.
Q: Individual difficulties being ranked will make it a pain to download the beatmap, much less with this version control thing you mentioned.
A: This is not something that can be done without changing osu! and the website. A fair bit of this to be done without inconveniences would require work on the dev part to get things user friendly to accommodate the change. Also beatmap preview comes in mind as a handy feature.
Q: Likes and favorites should also determine ranking
A: I don't like those because they are easy to brigade. For both, a friend or anyone can tell anyone else to like and favorite just to promote the beatmap, or even doing so without playing it. If the map has many unique plays, then the community must like it, right? Even if it is a shitty meme map, you can like a shitty meme map.
Q: What happens to kudosu/hype?
A: Obsolete
Q: Modders mod to gain kudosu to promote their maps. What does the metadata checking group gain by doing the work?
A: They do just because they want to. Because they want correct metadata on maps.
Q: What is essentially doing is going back to when the ranking criteria was more strict. We recently rewrote it make it less strict
A: Let's try this again, but less arbitrarily this time. All rules added ensure that many players are involved with the decision. It's no longer a proposal based system, but a complaint based one. A ranked map needs to be identified, and the players will really need to be unhappy with it. Unhappy enough to wipe the scoreboards and make a change in the criteria to prevent it from happening again.
Q: The maps are ranked so they stand out and not among piles of other shit. What you are doing defeats the whole purpose of beatmaps being ranked.
A: Living with majority of the good maps being unranked is not that bad, guys. Majority of the good mania maps are unranked. We just follow the mappers and share the good maps we find via favorites or multi. No name mappers actually have a better chance in this because they can always go to multi and put up their maps, playing and sharing them with everyone else. If the people who played the map actually like it, then they themselves would put it up next time. They no longer need to argue with someone else to get it ranked. If the map is bad, they would have a hard time getting it shared, period.
Q: Only PP maps will get ranked then
A: First, the intent is to solve the instability of the system. Fix all the trouble the modders and mappers cause for each other. The solution to this question is mostly a matter of fixing star rating. In terms of the modder and mapper trouble, right now modders can take pp maps and can reject possibly creative ones. In fact, modders would preferably avoid creative ones because they are sometimes so weird and fall into the grey category as far as their subjective opinions go. Instead of that, let's have: Either people like the map and make enough scores to get it ranked or they don't. This doesn't guarantee a decrease in pp maps, but it will offer a chance for more creative ones.
Q: How can you talk about the ranking process when you don't even have a ranked map. You are so ignorant about things and blame bn. This is just an excuse so you can rank your shit map. This is a joke.
A: A mapper spends time making a map and is proud of it. He/She seeks mods and a few mistakes are corrected. One modder comes around and says a slider is shit and is unrankable. Maybe it's a weird curvy slider that follows the music in a way only the mapper can see, idk. So the mapper argues it is perfectly fine and explains why. Still backlash, and even more when other modders come. The mapper really wants to keep the slider because it expresses his/her creativity. This means something to the mapper that doesn't to others. Telling that your thing is shit and needs to change imo is the worst form of respect, and what the entire modding process encourages. I opt for a system where the mapper can have his/her ways and let agreement with the mapper be reflected by how many scores are set on the map. It's better for the mind to not see the work gain traction rather than get told to change the work you are proud of.
Q: What is the point of this if nothing can be done now? All of this relies on features not implemented
A: Let’s first make sure we fix any flaws we find within this. During which time, it will probably take 5 years to convince peppy of if we happen to agree.