Beatmap quality control plan by strager Purpose Rate

Beatmap quality control plan by strager

Purpose �Rate maps based on quality �Add maps which have a high quality �Remove maps which have a lower relative quality �Secondary: Find the best map for the player �Difficulty ratings �Map style

Proposed map process Creation by Mapper Rating by Rating Approval by Team Submission Submissi Team on by User Quality! (“Ranked” )

Normal user �Likes/dislikes maps �Favourites maps �Comments and reports maps �Community choice awards? ? ? �Can view ST-approved and RT-approved maps

Submission Team (ST) �Reviews user- submitted maps �Approves or denies � 3/3 ST approvals required to promote map Normal user Beatmap submission ST review ST approval or denial

Rating Team (RT) �Rates maps for quality and difficulty �Per-difficulty, not perset �Manages reported maps � 5/8 RT approvals required to keep map unflagged � 2/8 RT approvals required to keep map ST-approved beatmap RT approval or denial

Management Team (MT) �“Administrators” �Manages the system �Promotes ST to RT �Promotes user to ST �Manages comments and other abuse-able privileges �Reviews reported and flagged maps Normal user ST ST application RT application MT review ST approval or denial RT approval or denial

RT rating criteria Map quality Map difficulty and style �Fun �Jumps �Matches music �Speed �Timing �Beat complexity �Aesthetics �Stamina �Storyboard (if applicable) �Skin (if applicable) �Readability �Accuracy (? ) �Style? �? ? ?

Misc. notes �MT’s can function as RT’s and ST’s �RT’s can function as ST’s �Few MT’s and ST’s; many RT’s