This is a t proposal with Basensorex, as this matter is something we've been discussing since I started modding and applying for the BNG.
We planned on making separate proposals for each topic, but we realized that the issues we mentioned were all correlated and the solutions all affect one major aspect. The BN application system.
--------------------------------------------------
With the recent changes of NAT and BN viewpoints on ranked maps' quality (community/forums/topics/1930032) from last year, many things in the mapping and modding scene have changed, particularly quality standards which have overall become much more lenient.
Subjective concerns are now far less relevant when ranking a map, allowing maps that couldn't be ranked before get ranked, like older sets and loved maps. The veto system now has a higher uphold threshold which has resulted in overall lower BN anxiety on evaluations, since you are now only punished by upheld vetoes and serious disqualifications/unrankables.
That all changed, but something really important didn't. The BN application process.
--------------------------------------------------
--> Issue #1) BN applications are still the same.
As someone who has failed many BN applications before, I couldn't help but feel hopeless when trying the standard application method, making them feel doomed no matter how hard I tried.
After analyzing many failed evaluations, I can assume the standards have not changed. BN applications are still in that same state, mostly focusing on hyper subjective concerns to keep modders from getting in. There are no new applicants (that haven't been a Beatmap Nominator in the past) that have recently gotten in using the standard application method.
If the NAT/BN expectations and viewpoints have changed towards being focused on objective concerns, why shouldn't BN applications do the same? The mods you make on a BN application are definitely not the same you do on your daily BN routine.
Being aware of subjective stuff is important to differentiate a rankable map from a good map, but these things only help once you are already a BN picking the maps you want to push for ranked. Having a failed application over subjective points is just backwards to me.
That being said, the only realistic option to get into the BNG nowadays for most people is the official BN mentorship.
--> Issue #2) The BN mentorship is good, but it's also way too unfair.
The official BN mentorship is a 2-3 month program that was created to turn modders into Beatmap Nominators.
We currently have an average of two mentorship programs per year with a high acceptance rate into the BNG when compared to standard BN applications and many new BN additions each cycle.
The only issue I have with it is that something this good is so hard to have access to for the majority of the modding community.
I was told that the choosing method of mentees is randomized, but I believe that enough isn't really fair, since it pretty much just turns the most efficient application method into a gacha. There are many promising modders that try to apply for it, but sometimes don't get picked due to bad luck.
When comparing BN mentorship applications to the standard application procedure, there's an insanely wide gap in rates of acceptance. In the last mentorship cycle, 80% of standard mentees were brought into the BNG (and all performed perfectly fine too!). Meanwhile, it's been actual months (over half a year it seems?) since the last person to get in through the normal application process, not counting those with previous BN experience for obvious reasons.
While obviously they're not equal samples of modders due to the filtering that goes on when mentees are selected, that alone, in my eyes at least, can't explain this wide of a gap between acceptance ratios.
I think the BN mentorship should really try to accommodate modders from a wider range of skill levels, so they can someday become BN after some time and effort.
--------------------------------------------------
Reworking the whole application system sounds like a huge amount of work, and I don't think we are ready for such big change all at the same time.
My proposals are much simpler, realistic and I feel they should have been adjusted and implemented since the viewpoint rework.
These proposals are not mutually exclusive, they can be merged together into a new proposal as well.
----------
--> Proposal #1) Increase leniency for BN applications and resignify the Probationary BN role.
I feel like sometimes objective and subjective issues can get a little confusing as they are not black and white, and more like a gradient.
Sometimes even objective stuff is subjective sometimes (like timing simplification for gameplay) so why even make subjective stuff such a decisive thing when accepting or failing applications?
With the new ranked map viewpoint, BNs should primarily do objective checks, making sure metadata is correct, identify and fix unrankable audio files, make sure spread makes sense with progression rules, etc. Anything else subjective should just be up to mappers or not matter as much on the final decision. The subjective part should be relevant when it comes to accepting maps. Why not give modders a chance at that?
If the objective part of the application was fine, but you still have questions about the subjectivity of their mods, just give them that and guide them to their Probationary BN role.
At the moment, the Probationary BN role feels completely abandoned. We have ZERO probation BNs at the moment (in osu!std). Since you can't even get demoted from full Beatmap Nominator, why is probation not being used for something else now?
Trial BNs were created to give a chance for the barely ing/failed applicants and see if they would do a good job. Not many were successful, but with the new NAT and BN viewpoints, it is clear that it's something that can be brought back.
My main proposal is to try lower standards for standard BN applications and use probation for what it should be used for, similar to how Trial BNs worked. For people to learn how to be a BN.
Evaluations of Probationary BNs should mainly focus on the objective checks that everybody must get right, with lesser emphasis on subjective checks aside from perhaps just your typical housekeeping mods that have relevant intersubjective agreement between mappers (e.g. broken stacks, broken colorhax, grouping, etc.).
If we apply our new standards, more applications should be ing and new should be entering the team.
This of course should still come with the caveat that mistakes made during your probationary period will be punished far more strictly than those same mistakes committed by full BNs, to ensure that these new BNs have the capability to be responsible when they become full BNs.
----------
--> Proposal #2) Make the BN mentorship more frequent and create more classes.
Having more mentors, not only NATs, but also experienced BNs would be something extremely positive.
With more mentors, you can have more mentees per cycle. It's rather simple.
I understand there are other factors like availability, how willing and how good at teaching a mentor can be, but these are internal discussions among the organization team, I'm just bringing it up as a possibility so something can be discussed or done about it. Perhaps having an application period for BNs interested in becoming mentors can be held and those with promise can be handpicked by NAT to assist in the mentorship cycle.
Making the mentorship more frequent would be cool, with the addition of more mentors.
NATs could also manually redirect failed applications from the standard application method that are still promising to the official BN mentorship (or, at least, more often than is done now).
Another thing that could help is to make the basic classes and guides be something more automated through recorded classes and leave more specific subjects to the mentors. Maybe even teaching how to use programs like Mapset Verifier and integrating it as an official tool for Beatmap Nominators?
Then, after some classes, you could have a small test about the overarching stuff you learned.
However, this should not be the most relevant part of their application, since they would be receiving , and applying that as a Probationary Beatmap Nominator.
--------------------------------------------------
--> Counter-Argument #1)
"Current BN application standards are the only real line of defense for having some amount of quality standards in new BNs."
Please note that despite application standards being made more lenient under this proposal, I still maintain that Probationary BNs *should* have strict evaluations (far stricter than full BNs) for any issues that do come up in their nominations, including those subjective issues enforced through vetoes.
I believe the "line of defense" for quality standards in BNs *should* be during this probationary period since it gives far more modders a shot at being BNs in the first place, which gives them the experience needed to do great work as full BNs, something far more important than the overly subjective wall that is the current BN application process.
----------
--> Counter-Argument #2)
"If these proposals are to be accepted, NATs would have a far higher workload in managing BN mentorship cycles, as well as enforcing strict probationary evaluations and an even higher amount of normal evaluations of full BNs."
The current NAT is capable of pretty smoothly dealing with their current workload of evaluations and mentorship cycles. I do not believe that an increase in workload is unmanageable at the current level.
However, I can definitely see how in the future these changes might lead to too much workload, the solution for which is obvious: run trial NAT cycles more regularly to increase the workforce and distribute workload more efficiently.
(Note: even if there aren't enough people wanting to become NAT at this exact moment to accommodate for a higher workload, having more people becoming BNs, in general and in the long term, will create more people who do want to become NAT, so that won't really be a concern.)
----------
--> Counter-Argument #3)
"Why do we even need more BNs? There were more standard ranked maps last year than ever, clearly having more BNs isn't needed."
Firstly, most of this proposal isn't really concerned with "increasing the amount of BNs". We're far more concerned about the fairness of both current methods of applying, since one of them is virtually useless for almost all modders while another is extremely effective at getting applicants in.
However, even given that, simply stating the fact that we've been getting more maps ranked as of late doesn't really capture the full picture. The reality is that standard's ranked map count is actually proportionally smaller to all other gamemodes when ing for active players.
While we don't have perfect numbers on the active playerbase per gamemode, you can get a rough idea by checking the active player counts of each country on the country leaderboards. Through this method we can get a decent estimate that the standard playerbase is about 3-4x the size of all other gamemodes combined.
Despite this, the amount of ranked maps last year in standard was only about 1.25x the size of all other gamemodes combined.
You might be able to make the argument that other gamemodes don't have as much depth as standard does which makes the modding workload lighter. We'd argue this doesn't really seem to be the case however, since the amount of BNs in standard versus in the other gamemodes is actually very similar, only about 1.15x as many, meaning that the same amount of work is being done proportionally based on amount of BNs.
--------------------------------------------------
TL;DR
--> Increase BN application leniency, focusing more on objective checks, since those are the most meaningful issues that BNs must know how to deal with once they're in, especially with the general shift towards less subjectivity when applying quality standards. (Something akin to Trial BNs, with a lenient application, yet strict probationary period)
--> Make official BN mentorship cycles more frequent with larger classes, to reduce amount of gacha "luck" one must have to be accepted into a class due to the randomized selection process. Create room for a wider range of modders who might not be as close to becoming a BN, to foster greater volume of experienced modders over time. Can also allow vetted experienced BNs to in as mentors for the cycles if more manpower is needed, or just have more NATs to deal with larger amounts of classes.
We planned on making separate proposals for each topic, but we realized that the issues we mentioned were all correlated and the solutions all affect one major aspect. The BN application system.
--------------------------------------------------
=== THE CURRENT SITUATION === 5dh61
With the recent changes of NAT and BN viewpoints on ranked maps' quality (community/forums/topics/1930032) from last year, many things in the mapping and modding scene have changed, particularly quality standards which have overall become much more lenient.
Subjective concerns are now far less relevant when ranking a map, allowing maps that couldn't be ranked before get ranked, like older sets and loved maps. The veto system now has a higher uphold threshold which has resulted in overall lower BN anxiety on evaluations, since you are now only punished by upheld vetoes and serious disqualifications/unrankables.
That all changed, but something really important didn't. The BN application process.
--------------------------------------------------
=== THE ISSUES === 6y2w1s
--> Issue #1) BN applications are still the same.
As someone who has failed many BN applications before, I couldn't help but feel hopeless when trying the standard application method, making them feel doomed no matter how hard I tried.
After analyzing many failed evaluations, I can assume the standards have not changed. BN applications are still in that same state, mostly focusing on hyper subjective concerns to keep modders from getting in. There are no new applicants (that haven't been a Beatmap Nominator in the past) that have recently gotten in using the standard application method.
If the NAT/BN expectations and viewpoints have changed towards being focused on objective concerns, why shouldn't BN applications do the same? The mods you make on a BN application are definitely not the same you do on your daily BN routine.
Being aware of subjective stuff is important to differentiate a rankable map from a good map, but these things only help once you are already a BN picking the maps you want to push for ranked. Having a failed application over subjective points is just backwards to me.
That being said, the only realistic option to get into the BNG nowadays for most people is the official BN mentorship.
--> Issue #2) The BN mentorship is good, but it's also way too unfair.
The official BN mentorship is a 2-3 month program that was created to turn modders into Beatmap Nominators.
We currently have an average of two mentorship programs per year with a high acceptance rate into the BNG when compared to standard BN applications and many new BN additions each cycle.
The only issue I have with it is that something this good is so hard to have access to for the majority of the modding community.
I was told that the choosing method of mentees is randomized, but I believe that enough isn't really fair, since it pretty much just turns the most efficient application method into a gacha. There are many promising modders that try to apply for it, but sometimes don't get picked due to bad luck.
When comparing BN mentorship applications to the standard application procedure, there's an insanely wide gap in rates of acceptance. In the last mentorship cycle, 80% of standard mentees were brought into the BNG (and all performed perfectly fine too!). Meanwhile, it's been actual months (over half a year it seems?) since the last person to get in through the normal application process, not counting those with previous BN experience for obvious reasons.
While obviously they're not equal samples of modders due to the filtering that goes on when mentees are selected, that alone, in my eyes at least, can't explain this wide of a gap between acceptance ratios.
I think the BN mentorship should really try to accommodate modders from a wider range of skill levels, so they can someday become BN after some time and effort.
--------------------------------------------------
=== SOLUTIONS === 2m4b2c
Reworking the whole application system sounds like a huge amount of work, and I don't think we are ready for such big change all at the same time.
My proposals are much simpler, realistic and I feel they should have been adjusted and implemented since the viewpoint rework.
These proposals are not mutually exclusive, they can be merged together into a new proposal as well.
----------
--> Proposal #1) Increase leniency for BN applications and resignify the Probationary BN role.
I feel like sometimes objective and subjective issues can get a little confusing as they are not black and white, and more like a gradient.
Sometimes even objective stuff is subjective sometimes (like timing simplification for gameplay) so why even make subjective stuff such a decisive thing when accepting or failing applications?
With the new ranked map viewpoint, BNs should primarily do objective checks, making sure metadata is correct, identify and fix unrankable audio files, make sure spread makes sense with progression rules, etc. Anything else subjective should just be up to mappers or not matter as much on the final decision. The subjective part should be relevant when it comes to accepting maps. Why not give modders a chance at that?
If the objective part of the application was fine, but you still have questions about the subjectivity of their mods, just give them that and guide them to their Probationary BN role.
At the moment, the Probationary BN role feels completely abandoned. We have ZERO probation BNs at the moment (in osu!std). Since you can't even get demoted from full Beatmap Nominator, why is probation not being used for something else now?
Trial BNs were created to give a chance for the barely ing/failed applicants and see if they would do a good job. Not many were successful, but with the new NAT and BN viewpoints, it is clear that it's something that can be brought back.
My main proposal is to try lower standards for standard BN applications and use probation for what it should be used for, similar to how Trial BNs worked. For people to learn how to be a BN.
Evaluations of Probationary BNs should mainly focus on the objective checks that everybody must get right, with lesser emphasis on subjective checks aside from perhaps just your typical housekeeping mods that have relevant intersubjective agreement between mappers (e.g. broken stacks, broken colorhax, grouping, etc.).
If we apply our new standards, more applications should be ing and new should be entering the team.
This of course should still come with the caveat that mistakes made during your probationary period will be punished far more strictly than those same mistakes committed by full BNs, to ensure that these new BNs have the capability to be responsible when they become full BNs.
----------
--> Proposal #2) Make the BN mentorship more frequent and create more classes.
Having more mentors, not only NATs, but also experienced BNs would be something extremely positive.
With more mentors, you can have more mentees per cycle. It's rather simple.
I understand there are other factors like availability, how willing and how good at teaching a mentor can be, but these are internal discussions among the organization team, I'm just bringing it up as a possibility so something can be discussed or done about it. Perhaps having an application period for BNs interested in becoming mentors can be held and those with promise can be handpicked by NAT to assist in the mentorship cycle.
Making the mentorship more frequent would be cool, with the addition of more mentors.
NATs could also manually redirect failed applications from the standard application method that are still promising to the official BN mentorship (or, at least, more often than is done now).
Another thing that could help is to make the basic classes and guides be something more automated through recorded classes and leave more specific subjects to the mentors. Maybe even teaching how to use programs like Mapset Verifier and integrating it as an official tool for Beatmap Nominators?
Then, after some classes, you could have a small test about the overarching stuff you learned.
However, this should not be the most relevant part of their application, since they would be receiving , and applying that as a Probationary Beatmap Nominator.
--------------------------------------------------
=== COUNTER-ARGUMENTS AND COUNTER-COUNTER-ARGUMENTS === 6w62i
--> Counter-Argument #1)
"Current BN application standards are the only real line of defense for having some amount of quality standards in new BNs."
Please note that despite application standards being made more lenient under this proposal, I still maintain that Probationary BNs *should* have strict evaluations (far stricter than full BNs) for any issues that do come up in their nominations, including those subjective issues enforced through vetoes.
I believe the "line of defense" for quality standards in BNs *should* be during this probationary period since it gives far more modders a shot at being BNs in the first place, which gives them the experience needed to do great work as full BNs, something far more important than the overly subjective wall that is the current BN application process.
----------
--> Counter-Argument #2)
"If these proposals are to be accepted, NATs would have a far higher workload in managing BN mentorship cycles, as well as enforcing strict probationary evaluations and an even higher amount of normal evaluations of full BNs."
The current NAT is capable of pretty smoothly dealing with their current workload of evaluations and mentorship cycles. I do not believe that an increase in workload is unmanageable at the current level.
However, I can definitely see how in the future these changes might lead to too much workload, the solution for which is obvious: run trial NAT cycles more regularly to increase the workforce and distribute workload more efficiently.
(Note: even if there aren't enough people wanting to become NAT at this exact moment to accommodate for a higher workload, having more people becoming BNs, in general and in the long term, will create more people who do want to become NAT, so that won't really be a concern.)
----------
--> Counter-Argument #3)
"Why do we even need more BNs? There were more standard ranked maps last year than ever, clearly having more BNs isn't needed."
Firstly, most of this proposal isn't really concerned with "increasing the amount of BNs". We're far more concerned about the fairness of both current methods of applying, since one of them is virtually useless for almost all modders while another is extremely effective at getting applicants in.
However, even given that, simply stating the fact that we've been getting more maps ranked as of late doesn't really capture the full picture. The reality is that standard's ranked map count is actually proportionally smaller to all other gamemodes when ing for active players.
While we don't have perfect numbers on the active playerbase per gamemode, you can get a rough idea by checking the active player counts of each country on the country leaderboards. Through this method we can get a decent estimate that the standard playerbase is about 3-4x the size of all other gamemodes combined.
Despite this, the amount of ranked maps last year in standard was only about 1.25x the size of all other gamemodes combined.
You might be able to make the argument that other gamemodes don't have as much depth as standard does which makes the modding workload lighter. We'd argue this doesn't really seem to be the case however, since the amount of BNs in standard versus in the other gamemodes is actually very similar, only about 1.15x as many, meaning that the same amount of work is being done proportionally based on amount of BNs.
--------------------------------------------------
TL;DR
--> Increase BN application leniency, focusing more on objective checks, since those are the most meaningful issues that BNs must know how to deal with once they're in, especially with the general shift towards less subjectivity when applying quality standards. (Something akin to Trial BNs, with a lenient application, yet strict probationary period)
--> Make official BN mentorship cycles more frequent with larger classes, to reduce amount of gacha "luck" one must have to be accepted into a class due to the randomized selection process. Create room for a wider range of modders who might not be as close to becoming a BN, to foster greater volume of experienced modders over time. Can also allow vetted experienced BNs to in as mentors for the cycles if more manpower is needed, or just have more NATs to deal with larger amounts of classes.