Mapping Ecosystem Changes
The following changes serve to make contributing more easily accessible to the community, which consequently improves upon and simplifies all current systems in place for the mapping and modding community.
Mapping Ecosystem Changes - BN Ecosystem
Mapping Ecosystem Changes - Vetoes
Mapping Ecosystem Changes - NAT Additions
Simplifying BN activity requirements
BN activity requirements have grown increasingly complex with unconventional exceptions that tackle niche scenarios, so we want to simplify it!
Proposed rules are as followed:
- A BN must nominate at least two maps per month.
- If they have fewer nominations in one month, they will be warned.
- If they get consecutive activity warnings, they will be removed.
- A Hybrid BN must have at least 1 nomination per proficient game mode.
This also removes the maximum activity limit.
Important clarification:
To elaborate on how this will work, a user will only be removed if they get two consecutive warnings, and the amount of non-consecutive warnings does not matter, so as long as a BN is not below the requirements for 2 months in a row, they are fine.
If a BN's potenial absence would exceed a month, they are encouraged to resign and re-join whenever they are able to comfortably operate as a BN, given that a good terms resignation is relatively easy to attain if a user doesn't have any outstanding or upcoming punishments (that are not activity-related).
Examples:
Number is nomination count per month.
Green = pass; Orange = warning; Red = kick
3-1-2-5-0-2-1-0: user is kicked at this point
3-0-2-1-2-0-1: user is kicked at this point
15-0-2-0-0: user is kicked at this point
7-4-1-1: user is kicked at this point
Repurposing probation
Probation never really made sense as a demotion position, and often served as a public shaming tool with its limitations being irrelevant to the intended warnings.
So, probation will only be used for new BNs who have no past BN experience, and users will no longer be in probation after a month regardless of their evaluation consensus. That way, it can serve its original purpose of being a technical safeguard and a learning period for new BNs.
Removal of mock evaluations
Mock evaluations became pretty much unused because they turned out to be redundant with NATs focusing more on BN evaluator rounds due to the added benefits from that (involving BNs with the full evaluation process, getting to work with them directly, etc.).
Note: This does not apply to osu!catch
Simplifying cooldowns
In an effort to reduce overcomplications and obscure use cases, we noticed that most non-default cooldowns are rarely used, and don't serve any meaningful difference.
Hence why we will be setting a 60-day cooldown for anything relevant (namely application rejections, BN removals, standard terms resignations), while having no cooldown for BNs who have resigned on good terms.
Early evaluations for highly active BNs
Evaluations for BNs who are extremely active can end up overlooking large percentages of maps in the eval period and also cause the system to be too retroactive.
Therefore, the NAT will evaluate users once 3 months pass (as usual), or when they reach 30 nominations since their last evaluation, whichever comes first.
Giving BNs a say in mapping system developments
We want BNs to be more involved with deciding what's best for our beloved circle game, and since there hasn't been a straightforward way to do this until now, we'll be re-kindling the Beatmap Management subforum!
It will be a space for BNs to propose and discuss potential changes to the mapping ecosystem, with the NAT actively monitoring said discussions in order to make sure everyone's voice is heard and to implement whatever changes the community desires.