Mapping and modding timeline 6j4y5r

Mapping and modding systems are constantly improving. The Mapping and modding timeline aims to document the biggest system changes and to serve as a reference tool when s are incorporating new changes. 4j3nk

2007 1a4ql

September 2l3l55

• 2007-09-17: osu! was publicly released.

October 4b5l1j

• 2007-10-21: Ranking Criteria launched.
• 2007-10-29:: Forum thread icons were standardised for the ranking process.

  • A star () icon marked good maps that need more work.
  • A bubble () icon marked beatmaps considered for ranking.
  • A heart () icon marked ranked beatmaps. These could only be placed after a beatmap was bubbled, ensuring two nominations per beatmap.
  • A nuke () icon marked beatmaps that could not be ranked under any circumstances.

200 beatmaps were ranked in 2007.

2008 lb3g

March 1n5470

• 2008-03-11: Graveyard beatmap category was implemented to house inactive beatmaps.

  • The community expected every pending map to be ranked, but maps were being frequently abandoned and needed to be separated.

July 1s6u33

• 2008-07-31: Approved beatmap category was implemented to provide leaderboards to beatmaps inappropriate for ranking.

  • Common reasons for approval initially included length above 5 minutes and scores above 20 million, neither of which were allowed for ranked content.
  • A flame () icon marked approved beatmaps after two bubbles.

December 1le17

• 2008-12-20: Requirements for ing the Beatmap Approval Team (BAT) were published.

  • were hand-picked based on criteria outlined in the announcement's forum post.
  • BAT had a red title on the forums.

690 beatmaps were ranked in 2008.

2009 5l5c21

February 3v2h6y

• 2009-02-04: Ivalset was promoted as the first BAT manager.

  • His primary role was to organise new BAT promotion and improve the current BAT's activity/proficiency.

March 1n5470

• 2009-03-04: Ivalset launched the first Delegation of the Beatmap Approval Deciding Authorities; Submission Squad (BADASS).

  • This change was launched because prior BAT were added based on an informal vote from osu!'s #bat IRC channel, which wasn't visible to enough s.

November 5k4z24

• 2009-11-10: Pasonia was appointed as BAT manager after Ivalset stepped down.

  • He continued promoting new BAT and maintaining the current BAT.

December 1le17

• 2009-12-27: The Mapping Assistance Team (MAT) launched.

  • MAT could mark beatmaps with proto-bubbles which indicated quality beatmaps that BAT should review.
  • Ephemeral was the group's first MAT Leader.
  • MAT had a purple title on the forums.
  • The MAT was initially titled the "intermediate modding team" consisting of established modders who weren't ready to enter the BAT yet.
  • The MAT's goals were to reduce BAT workload, identify maps that were slipping between the cracks in the ranking cycle, and increase quality control, both of which were pressing issues at the time. In hindsight, none of its goals were fully realised.

1400 beatmaps were ranked in 2009.

2010 4y245w

July 1s6u33

• 2010-07-24: The first iteration of the Community Mentorship Program was launched.

  • s could apply to learn about mapping and modding directly from volunteer MAT and BAT .
  • The program was discontinued in 2013.

August 32593q

• 2010-08-27: ztrot was appointed as MAT leader after Ephemeral stepped down.

  • Leadership was tentatively ed between the two s until ztrot held control in February 2011.

October 4b5l1j

• 2010-10-03: MAT were granted permission to nominate beatmaps for ranking with normal bubble () icons, as opposed to proto-bubbles.

  • Proto-bubbles were ignored by most BAT , so the MAT had no purpose without this change.
  • This gave MAT considerably more influence in the ranking process.
• 2010-10-10: MAT were no longer allowed to nominate or vote on new additions to their team.

  • Having gained bubbling permissions, it was assumed that the MAT would vote for personal gain, so this was prevented before damage could be done.
  • The BAT gained full responsibility for MAT additions.

December 1le17

• 2010-12-31: Derekku was appointed as BAT leader after Pasonia stepped down.

  • Like his predecessors, he continued handling new BAT promotion and maintaining the current BAT.

1864 beatmaps were ranked in 2010.

2011 5b2l5i

March 1n5470

• 2011-03-09: MAT were granted permission to bubble Approval beatmaps.

  • Only one of an approved map's two bubbles could be placed by a MAT member.
  • This change was implemented because approved beatmaps were becoming more common.
• 2011-08-23: "Beatmap Approval Team" was renamed to "Beatmap Appreciation Team".

  • The purpose of the new name was to unite s involved in beatmap approval and s involved general moderation (essentially the Global Moderation Team) under the same name, which "Beatmap Approval Team" did not effectively represent.

October 4b5l1j

• 2011-10-08: Ranking Criteria subforum opened for public discussion on Ranking Criteria proposals.

  • These discussions were previously held by BAT in a private subforum.

1368 beatmaps were ranked in 2011. This was the first decline after 4 years of consecutive growth.

2012 3y515v

July 1s6u33

• 2012-07-22: The first iteration of Performance Points known as ppv1 was established, replacing total ranked score leaderboards.

August 32593q

• 2012-08-21: Approved beatmaps began rewarding Ranked score.

  • Ranked score was no longer used as the primary scoring metric, so Approval beatmaps could no longer be abused for player rankings.

1460 beatmaps were ranked in 2012.

2013 3g2eq

March 1n5470

• 2013-03-20: The BAT was split into the BAT and Global Moderation Team (GMT).

  • Many of the BAT were on board solely for moderation duties, so this clarified the roles of modding and moderating .
  • of the new GMT were previously known as "Green BAT".

April 19673t

• 2013-04-23: The MAT was dismantled.

  • All MAT were added to the BAT.
  • This change was made because the line between MAT and BAT had become too thin. A MAT member was effectively a BAT member who couldn't rank beatmaps, which did not align with the initial goals of the MAT as a new group.
  • The BAT was also fairly inactive at this time, so a large influx of new solved this problem.

May 1q3i2l

• 2013-05-15: The Triumvir Conglomerate was formed.

  • The role of BAT manager was split between 3 s from different regions in an attempt to promote equal input among mapping subgroups. Garven represented North America, NatsumeRin represented Asia, and Kurai represented Europe.
  • Prior to this, Asian subgroups were often neglected because they communicated mainly outside of osu!'s IRC/forums.
  • When the 3 did not agree on a decision, it needed to be decided by a higher-up (most often Ephemeral).

August 32593q

• 2013-08-01: Beatmap unranking policy was implemented, allowing BAT to unrank a beatmap within 1 week of ranking.

  • This change was a test for the later implemented Qualified category.
• 2013-08-02: The first osu!taiko BAT were added, signifying a separation of game mode permissions in the group.

  • Any BAT could theoretically nominate beatmaps of any mode before this time, however the growth of different game modes made the distinction necessary.

December 1le17

• 2013-12-12: Beatmaps with two nominations began being promoted to the Qualified category instead of Ranked.

  • Qualified beatmaps could be disqualified within 1 week, replacing the option of unranking a beatmap within 1 week.
• 2013-12-22: The Triumvir Conglomerate cycled its regional leaders to avoid burnout.

  • Charles445 represented North America, popner represented Asia, and Loctav represented Europe.

1327 beatmaps were ranked in 2013.

2014 5ja5

February 3v2h6y

• 2014-02-10: To improve organisation, mapping and modding system internal management shifted from the forums to Trello.
• 2014-02-18: Approved beatmap category was retired.

  • Marathon beatmaps were promoted to Ranked with 3 BAT nominations (2 bubble () icons + 1 flame () icon).

August 32593q

• 2014-08-21: The Quality Assurance Team (QAT) splits off from the current BAT.

  • The BAT (often called newBAT at this time) nominated beatmaps for rank.
  • The QAT ensured qualified beatmaps were of sufficient quality. Beatmaps that did not meet quality standards were disqualified.
  • This essentially reversed the merging of the BAT and MAT last year.
  • The split was implemented as part of a manual trial for modding v2 attempting to automate BAT promotion and retirement.
  • Despite attempts at framing disqualifications as a positive change for mapping quality, the community viewed them negatively. This was especially apparent in cases of controversial beatmaps like the disqualification on Halozy - Genryuu Kaiko

October 4b5l1j

• 2014-10-15: The Beatmap Management subforum replaced Trello.

  • Public accessibility to the BAT increased, which was the goal of modding v2.
  • Issues related to nominated/qualified beatmaps were posted here, along with any announcements related to mapping/modding systems.

November 5k4z24

• 2014-11-14: New BAT promotion was held via public votes among current BAT/QAT.

  • s with 15 or more votes and automatically calculated modding activity would be promoted to the group intermittently.
  • This was handled on Trello in the past.

1381 beatmaps were ranked in 2014.

2015 5a76y

February 3v2h6y

• 2015-02-01: Red names were removed from BAT and BAT was renamed to Beatmap Nominators (BN).

  • These changes intended to make the BN more closely associated with the average , which was the goal of moddingv2's community-driven design.
  • The team was initially renamed to Beatmap Appreciators, however it was quickly renamed to Beatmap Nominators by community suggestion.
  • Beatmap Nominators generally disagreed with this change and heavily argued against it in this forum thread.
• 2015-02-24: New BN applications replace BN voting.

  • This was done to promote moddingv2's community-driven design and to avoid the nepotism that was involved in public voting.
  • The only criteria was an applicant's automatically calculated modding activity.

June 346z3r

• 2015-06-04: Realtime Beatmap Nominator Ranking was introduced to automatically assess BN nomination quality/activity.

  • The system was dropped soon after its announcement due to implementation concerns by osu!'s developers.
• 2015-06-06: QAT disqualifications were anonymised on the forums.

  • All posts were written under a named "Quality Assurance Team".
  • This was set up in response to frequent attacks on the QAT's disqualifications, often relating to removing high performance points scores (e.g. the disqualification on Dragonforce - The Last Journey Home) or relating to forced opinions (e.g. the disqualification on Reol - Asymmetry).
  • The community referred to the anonymous QAT as the "QAT bot".
  • This change encouraged the growing opinion that the QAT was trying to hide from the consequences of their actions, hurting the reputation of disqualifications and the QAT in general.

August 32593q

• 2015-08-25: Qualified beatmaps no longer rewarded players with Performance Points.

  • This was done in response to widespread complaints about Performance Points losses on qualified beatmaps.
  • Tension between players and the QAT was relieved after this change.
• 2015-08-26: Anonymous QAT disqualifications were discontinued.

  • With less tension between players and the QAT, anonymization was deemed unnecessary.

December 1le17

• 2015-12-27: BN tests were implemented for BN applications.

  • These tests required s to answer a multiple choice form and mod a problem-filled beatmap.

1934 beatmaps were ranked in 2015. This was the first year of growth after 4 years of consecutive stagnation.

2016 l3m60

February 3v2h6y

• 2016-02-13: Ranking Criteria Council was created to reform the Ranking Criteria.

  • Public proposals on the Ranking Criteria subforum were no longer considered.
  • Taking a stance similar to the Triumvir Conglomerate, the Ranking Criteria Council involved to represent major mapping subgroups by region. Each game mode had 1 mapper and 1 player from the Americas, Europe, and Asia, along with 2 of the QAT.
  • Each game mode's goal was to create a general/difficulty-specific Ranking Criteria for their respective mode. osu!catch was the only game mode that achieved this goal under this system.
  • The collective goal of this group was to rewrite all sections of the general Ranking Criteria.
• 2016-02-24: Mapset and spread restructure was introduced to limit the number of difficulties in each difficulty tier per beatmap.

  • Negative public reception caused this to be rolled back immediately and its forum thread accumulated 614 responses in 24 hours, making it osu!'s fastest moving thread.
  • This attempt at undemocratic change caused the Ranking Criteria Council to immediately have a negative reputation.

April 19673t

• 2016-04-25: The QAT began checking qualified maps for issues reactively rather than proactively.

  • s reported qualified beatmaps to the QAT for disqualification. The QAT checked confirmed or denied reported issues in their respective beatmap forum threads.
  • This change was made in response to the consistently negative view of disqualifications by the QAT. The QAT mostly distanced itself from Quality Assurance related tasks at this point.
  • Metadata checks were still done proactively by the QAT, headed by IamKwaN.

July 1s6u33

• 2016-07-20: The United Beat-Knights of Ranking Criteria (UBKRC) was created to replace the Ranking Criteria Council.

  • The UBKRC's goals were the same as the Ranking Criteria Council, but it was more widely accepted because it was open to community influence.
  • Teams of experts were chosen for each subsection of the Ranking Criteria (e.g. one team of storyboarding experts, another team of skinning experts, etc.).
  • The group was managed by Okoratu and pishifat.
  • The UBKRC's name was chosen because it was ridiculously stupid. Its aim was to appear less authoritative than the Ranking Criteria Council.

August 32593q

• 2016-08-05: The Quality Assurance Team blog was created.

  • The QAT was receiving criticism about being too closed-off from the rest of the mapping community, so this blog was created to increase transparency for QAT decision making and community activity.
• 2016-08-26: The Code of Conduct was implemented to establish modding behaviour expectations.

  • These rules and guidelines were treated as common sense up until this point. By documenting them, moderation could be made more consistent.

September 2l3l55

• 2016-09-30: The Community Mentorship Program re-launched after a long hiatus.

  • Its new structure was centred around Discord communication and seasonal cycles.
  • The program was led by Okoratu and Yuii-

October 4b5l1j

• 2016-10-17: Loved beatmap category was created.

  • The category provided leaderboards for popular maps that could not be ranked for various reasons.
  • See History of Loved for a detailed timeline of Loved system changes.

November 5k4z24

• 2016-11-01: The Beatmap Veto system was implemented.

  • Beatmap Nominators could halt a beatmap in the ranking process for subjective reasons by resetting a nomination. This was done with a bubble pop () icon.
  • Vetoes could be overwritten by the nominations of Beatmap Nominators previously uninvolved with the beatmap.
  • To allow adequate time to veto, consecutive nominations could not be set within 24 hours of each other.
  • Inconclusive vetoes were mediated by the QAT shortly after this system's implementation.
• 2016-11-02: Beatmap Nominator files were created to keep tabs on all individual BN .

  • These files included modding/nomination activity, disqualifications, and behaviour issues.
  • of the BN with 3 or more "strikes" logged in these files would be removed from the group.

1720 beatmaps were ranked in 2016.

2017 591q6j

April 19673t

• 2017-04-06: Beatmap Nominator Tiers were implemented, splitting the BN into two subgroups called "tiers".

  • Because the QAT was no longer acting as a quality control gate, this system was implemented to improve the quality of beatmaps entering Ranked.
  • This system mimicked the later stage of the Mapping Assistance Team.

    • Tier 1 nominators could bubble maps.
    • Tier 2 nominators could bubble and qualify maps.
  • Tiers were decided by a BN test designed around identifying overarching issues in beatmaps. Test results were terrible, revealing that the test's design was flawed.
  • Contrary to its goals, this system lowered motivation for all tier 1 nominators and overworked the few motivated tier 2 nominators. Mappers had fewer BN resources and the total maps ranked during the tiers period diminished.
  • No Beatmap Nominators were added to the 2nd tier for the 5 months this system was active, which hugely bottlenecked ranking speeds.

May 1q3i2l

• 2017-05-22: Beatmap Nominator Discord server was created for BN subdivisions.

  • Subdivisions were designed as focus groups of randomly selected nominators from both tiers led by a member of the QAT.
  • Most QAT management shifted to this server despite resistance from osu! higher-ups.
• 2017-05-23: Discord bot Aiess was created by Naxess.

  • This provided a feed of mapping related events in osu! Discord servers, starting with nomination and disqualification feeds.

June 346z3r

• 2017-06-02: Marathon beatmaps began to require 2 nominations instead of 3.

  • They previously required 3 nominations because it was expected that marathons had more content to check than a normal mapset, but this was no longer true.
  • The flame () icon discontinued use.

September 2l3l55

• 2017-09-10: The "QAT Upheaval" was implemented. This was a series of changes in response to dissatisfaction from the mapping community under leadership by osu! team higher-ups. Following this change, the QAT began self-leadership without higher-up intervention.

  • BN Tiers were replaced with Probationary Beatmap Nominators. Two probationary BN could not nominate the same beatmap and s could not be in Probation for more than two months at a time.
  • Beatmap Nominators were given purple titles on the forums.
  • Okoratu and JBHyperion were appointed as QAT leaders by a vote of BN/QAT . Their responsibility was to work with the osu! team to maintain the mapping and modding communities.
  • Tenure based Beatmap Nominator and Quality Assurance Team profile badges were created. This and other Beatmap Nominator rewards were planned to re-motivate the currently dissatisfied team.
  • With less authoritative leadership and more s capable of nominating beatmaps after these changes, mapping standards stopped being strictly controlled. Controversial beatmaps that would have likely not been ranked under the previous system (e.g. FELT - Rendezvous) reached ranked status.

October 4b5l1j

• 2017-10-01: BN tests were replaced with the QAT reviewing each BN applicant's anonymised mods.

  • This change was made because BN test cheating had become unrealistic to avoid.

December 1le17

• 2017-12-17: Loctav stepped down from involvement in the osu! team, including his heavy participation in the QAT.

1847 beatmaps were ranked in 2017.

2018 4o5a65

February 3v2h6y

• 2018-02-08: The Mappers' Guild was opened to public applications for widespread Featured Artist beatmap creation.

March 1n5470

• 2018-03-01: QAT separated its tasks into branches: BN evaluation, disqualifications, metadata, spotlights, blog, Ranking Criteria, and general leadership.

  • QAT could be involved in multiple branches.
  • This aimed to give purpose to some QAT who felt that they had no specific roles in the mapping/modding community. This feeling was largely relevant because the QAT had little involvement with Quality Assurance anymore.
• 2018-03-03: #modding channel was created in the osu! Discord server.

  • While its goal was to shift mapping discussion away from the BN Discord server, this discussion centre was rarely used apart from scheduled QAT meetings.
• 2018-03-24: Ranking Criteria subforum was re-opened for public proposal discussions and the UBKRC was discontinued.

  • The UBKRC was discontinued at this time because all subsections of the general and game mode Ranking Criteria were finalised.

April 19673t

• 2018-04-01: The QAT began evaluating BN applications by reviewing non-anonymous mods, as opposed to previously anonymous mods.

  • This change was made because the QAT believed out of context anonymous mods could not effectively determine a modder's capabilities.
  • Through this change, the QAT determined that bias could not be avoided when evaluating Beatmap Nominators.
• 2018-04-22: The QAT held its first meeting on the osu! server in an attempt to increase transparency of QAT affairs and migrate internal discussions away from the BN Discord server.

  • Despite this attempt, most internal discussion was still handled on the BN Discord server.

May 1q3i2l

• 2018-05-22: Mao became a QAT leader after Okoratu stepped down.

  • Like his predecessor, he continued working with the osu! team to manage the mapping/modding scenes.

June 346z3r

• 2018-06-21: The Quality Assurance Helper initiative was created.

  • This was designed to ensure that all qualified beatmaps were reviewed by at least 2 BN or QAT before rank.
  • The program was managed via Trello and automated by Naxess through Aiess.
  • This change was one of the primary reasons that the QAT was later renamed.

July 1s6u33

• 2018-07-29: New beatmap spread rules were implemented, completely reshaping how many difficulties were created in ranked mapsets going forward.

  • Prior to this change, any map with a drain time shorter than 5 minutes required a full difficulty spread. After the change, difficulty spread requirements were more lenient for longer beatmaps below 5 minutes of drain time.
  • For more details on this change, read its forum thread.

December 1le17

• 2018-12-12: The osu! team took a negative stance on beatmap commissions.

  • The team acknowledged that commissions will happen, but pledged to take no action unless of the BN or QAT were involved.
• 2018-12-17: -Mo- became a QAT leader after JBHyperion stepped down.

  • Like his predecessor, he continued working with the osu! team to manage the mapping/modding scenes.
• 2018-12-17: The QAT was declared as having no future in its current state and ideas for reform were encouraged.

  • This decision was made because the QAT had not been involved in anything Quality Assurance related for years, however a system needed to exist to maintain the Beatmap Nominators and mapping community in general.
  • Some concerns at the time about the QAT included:

    • Little QAT engagement in controversial maps.
    • Limited accessibility for new s to enter the team, causing stagnation.
    • The role of the QAT in the mapping community was unclear.

2749 beatmaps were ranked in 2018. This year's impressive growth can be largely attributed to the QAT's discontinued Quality Assurance role and higher initiative from Beatmap Nominators.

2019 3g4bk

January 405i2h

• 2019-01-29: A proposal for QAT reform was created as a conglomeration of other s' proposals.

  • The Nomination Assessment Team (NAT) was introduced through this proposal, and was implemented later this year.

March 1n5470

• 2019-03-01: The Mappers' Guild transitioned from application-based entry to automatic entry for anyone with 3 ranked maps.

  • Featured Artist beatmaps became more frequently created and ranked.
  • #mappers-guild channel was created in the osu! Discord server.
• 2019-03-13: Rule requiring consecutive nominations to be set at least 24 hours apart from each other was removed.

  • This rule was a major complaint from mappers and Beatmap Nominators because it felt like it was unnecessarily wasting everyone's time. If an issue was found after the first nomination, the second nominator would often avoid pointing it out to avoid an extra 24 hour wait.
  • Along with this change, Beatmap Nominators could veto qualified beatmaps. The rule originally existed because Beatmap Nominators needed 24 hours to potentially apply vetoes to maps with one nomination.

May 1q3i2l

• 2019-05-05: The BN/QAT restructure was finalised.

  • The Quality Assurance Team was renamed to the Nomination Assessment Team.
  • Beatmap Nominators became responsible for disqualifications and veto mediation. Veto mediation was handled through a blind vote rather than a discussion.
  • The Beatmap Nominator website was published to automate many BN/NAT tasks.

    • Through the website, s could apply to the BN at any time as opposed to the previous cycle-based application system. This resulted in Beatmap Nominators being added at irregular times instead of in large waves.
    • Reports for inappropriate beatmaps and BN/NAT misconduct were shifted from a Google Form to the BN website.
    • Statistics and evaluations for BN modding/nomination activity and proficiency shifted from painfully inefficient Google Spreadsheets to the BN website, hugely increasing productivity for Beatmap Nominator management.

August 32593q

• 2019-08-05: Naxess released the Mapset Verifier tool, automating a significant portion of beatmap checking processes for Beatmap Nominators.
• 2019-08-06: Beatmap Nominators became able to participate in BN application evaluations.

  • BN input is visible to the NAT when trying to reach a consensus, though they are rarely used to sway a vote.
  • The NAT often use BN input to help determine future NAT .

October 4b5l1j

• 2019-10-22: Ascendance became a NAT leader after Mao stepped down.

  • Because NAT leaders had often been ive towards negative decision making, Ascendance took an active controlling role and delivered bad news regarding NAT removals.

3217 beatmaps were ranked in 2019.

2020 4u86k

February 3v2h6y

• 2020-02-07: The first Elite Nominator profile badges were awarded to recognise continued exceptional performance from of the BN team.

  • These were originally planned in the QAT Upheaval two years prior.
• 2020-02-21: NAT leadership as a concept was discontinued as Ascendance stepped down as NAT leader.

  • Tasks specific to NAT leaders were delegated to the whole team.
• 2020-02-24: The Quality Assurance Helper system was transferred from Trello to the Beatmap Nominator website.

  • This change was made to for Quality Assurance activity in Beatmap Nominator evaluations.

April 19673t

• 2020-04-11: The Mappers' Report led by Feerum was created to summarise mapping community events via front page news posts.

June 346z3r

• 2020-06-09: The Content Usage Guidelines article was added to the wiki and promoted in the Beatmap Submission System to encourage appropriate permission for all assets in new beatmap submissions.

October 4b5l1j

• 2020-10-02: Beatmap Nominator Expectations were established to combat behaviour concerns within the group.

  • Concerns included low approachability, uncivil actions in community settings, and questionable ranking quality standards.
  • This resulted in the immediate removal of 5 Beatmap Nominators.
• 2020-10-29: Beatmap Nominator game mode proficiency became visible on osu! web.

November 5k4z24

• 2020-11-30: Hybrid beatmaps were reworked to require 2 nominations per game mode.

  • Nominators proficient in multiple game modes could select one or more game modes to nominate on applicable mapsets.

December 1le17

• 2020-12-17: Inappropriate content review submission and evaluation were moved from Discord discussions to blind votes via the Beatmap Nominator website.

3580 beatmaps were ranked in 2020.

2021 21s3r

January 405i2h

• 2021-01-05: Explicit label for beatmaps was implemented to clean up inappropriate old ranked content and permit previously unacceptable song content.

  • This change did not apply to visual content in pending beatmaps. These continue to follow Visual Content Considerations.
• 2021-01-30: In-game chat channel #modhelp was replaced by #mapping because the original channel was primarily used for mapping discussion.

March 1n5470

• 2021-03-09: In conjunction with the Content Usage Guidelines, an addition to the Ranking Criteria began requiring mappers to source their background images and other media in their descriptions.
• 2021-03-15: Requirements for re-ing the Beatmap Nominators were loosened.

  • All applicants needed to undergo the application, but returning group had shorter cooldown options and were allowed to provide 1-2 months of modding activity instead of the previous 3 month standard.
• 2021-03-16: Beatmap Nominators were given automatically renewing osu!er.

  • This change was made in response to a lack of incentives for dedicated of the mapping scene.
• 2021-03-16: The limit of ranked maps per day per mode was increased from 8 to 10 to compensate for an overflowing Qualified beatmaps category.

April 19673t

• 2021-04-08: A Ranking Criteria Rule disallowing multiple Qualified beatmaps of the same song was removed.

  • Concerns about malicious disqualification practices were relieved by this change.

May 1q3i2l

• 2021-05-12: The Nomination Assessment Team began a trial for new Beatmap Nominator evaluations.

  • This trial only included osu! and concluded in August.
  • A subset of Beatmap Nominators were given evaluation roles equal to the NAT, allowing them to contribute to and decide the outcomes of BN applications and current BN evaluations.
  • The first batch of trial included ~10 s, while the second batch included ~20 s.
• 2021-05-13: An option to change difficulty owner was added to the Beatmap Discussion page.

  • This allowed guest difficulty creators to resolve issues on their beatmaps. Only the mapset host could resolve issues prior to this change, which was a major frustration to mappers.

June 346z3r

• 2021-06-14: The Global Moderation Team began accepting applications from mapping-focused s to bridge the growing tension between the GMT and mapping/modding scenes.

August 32593q

• 2021-08-14: osu!taiko began a trial of Beatmap Nominator evaluations mimicking osu!'s trial from 2021-05-12.

September 2l3l55

• 2021-09-11: peppy changed Ranking Criteria rule about the Source field.

  • Mapping community were unhappy with the lack of public discussion behind this change and later made adaptations to close new loopholes.
• 2021-09-18: After a decade-long hiatus, the osu! community meetings returned in the form of stage voice chats on the osu! Discord. The first primary topic addressed was concerns with osu!mania's Ranking Criteria, along with other issues like general Ranking Criteria complexity, engaging with newer mappers, and more.

  • osu!mania Ranking Criteria changes were put up for discussion and, if agreed upon, may take effect soon.
• 2021-09-24: Quality Assurance checks no longer counted towards Beatmap Nominator activity.

  • This was implemented because it seemed like some s were using this as a loophole to avoid actively contributing as a Beatmap Nominator.
  • Prior to this change, every QA check was considered equal to 1/4 of a nomination.

October 4b5l1j

• 2021-10-12: Former Beatmap Nominators, who resigned on good within the past year, can now become full immediately upon reing.
• 2021-10-13: osu!mania beatmaps do not require hit sound additions anymore.

  • This was done in response of a popular request from the community to increase approachability for osu!mania mappers who come from various upbringings.
• 2021-10-18: Spread rules for osu!mania beatmaps have been relaxed.

  • This was done upon request from the community via a Ranking Criteria proposal in order to make the under-utilized Ranked section more approachable to mappers.

December 1le17

• 2021-12-04: Following this Ranking Criteria proposal, Shokyuu is now officially adopted as the official name of Beginner difficulties for osu!taiko.
• 2021-12-14: The burai sliders rule has been loosened per this proposal.

  • This was done to accomodate for new mapping styles by making specific criteria for each difficulty, instead of making it a general rule.

4500 beatmaps were ranked in 2021.

2022 5ul4q

January 405i2h

• 2022-01-21: A new feature dedicated to making BN requests more convenient has been deployed to the Beatmap Nominators website, called BN Finder.

  • Anyone can submit maps in the BN Finder queue that's present on the home page of the website.
  • Matches are made based on the preferences BNs/NATs can set.
  • BNs/NATs can review potential matches below the submission form.
  • After a match is accepted or denied, the mappersguild bot will send a message to the requester informing them of the consensus.

February 3v2h6y

• 2022-02-03: Following this discussion about Beatmap Nominator activity, a bottom line has been added where the warning step would be skipped for activity checks if someone falls below it.

  • Falling below the 90 day requirements with more than 60 days worth of nominations will result in an activity warning.
  • Falling below 60 days worth of nominations in a 90 day period will result in a removal when activity is checked.
• 2022-02-03: osu!staff took Community Contributors nominations from the public for the first time via a form.
• 2022-02-23: ModScore activity over the past 3 months is no longer required to apply to the Beatmap Nominators in the osu!taiko, osu!catch, or osu!mania game modes.

March 1n5470

• 2022-03-01: The osu!mania Nomination Assessment Team started adding more Asian in order to improve the Asian represenation and accessibility to the Beatmap Nominators.

  • In total, 3 new NAT were added across the following months.
• 2022-03-01: Based on notable community interest and a lengthy discussion, the osu!taiko Muzukashii break guideline has been reworked to allow for more freedom by adding a substitute to 3/2 breaks.

  • This change has greatly increased the accessibility of mapping Muzukashii difficulties for many mappers.
• 2022-03-23: 15 Beatmap Nominators across all game modes were added to the 2021 Elite Nominators.
• 2022-03-31: Beatmap Nominator applications for the osu! game mode have closed for the first time, since the adoption of the new application system from the BN/QAT restructure.

  • This was done in order to catch up with the constantly growing backlog.

April 19673t

• 2022-04-22: Ranked/Loved guest difficutly maps now appear on pages, and they have guests retroactively assigned to them, while giving NATs/GMTs the ability to assign them manually on all Ranked/Loved maps.

May 1q3i2l

• 2022-05-01: Following the recent addition of 4 new NAT , Beatmap Nominator applications for the osu! game mode have opened again.
• 2022-05-16: Beatmap Nominators who are performing well will get their future evaluations in intervals of a longer 6 months, where historically the default was everyone being evaluated every 3 months.
• 2022-05-16: The nomination cap for osu!taiko has been increased from 75 to 100 unique nominations within 90 days.

  • This was mainly done because it's easier to reach the nomination cap in osu!taiko while performing well due to the simplicity of the game mode.
  • This change was temporarily met with opposition because of concerns regarding the amount of Ranked osu!taiko maps being notably out of proportion with the amount of people actually playing them.

June 346z3r

• 2022-06-30 Community Contributors: 2021 were revealed, featuring 15 s for their outstanding contributions to the game.

July 1s6u33

• 2022-07-01: The Nomination Assessment Team has added 12 new Beatmap Nominators to the evaluators trial in order to look for new NAT candidates and to assist with clearing current workload.

  • This evaluator trial is very similar to the trial from 2021-05-12.
  • This trial only included osu! and concluded in 2022-07-31.
  • This batch of evaluators included 12 s.
• 2022-07-04: An osu!mania Beatmap Nominator was retroactively added to the 2021 Elite Nominators after an internal discussion within the Nomination Assessment Team.
• 2022-07-14: osu!taiko has also added 2 Beatmap Nominators to the evaluators trial, mimicking osu!'s ongoing trial.