Ranking criteria/BN rules updates #2078
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cl8n
reviewed
Feb 22, 2019
cl8n
requested changes
Feb 22, 2019
| + **You can veto a beatmap set by placing a bubble pop icon or a problem stamp on the set that you disagree with being fit for being Ranked.** Placing a beatmap veto over any kind of quality issues that you think need to be addressed before the map can move anywhere is one of your main responsibilities. A proper discussion with attempting to reach a mutual agreement by both sides of the argument has to follow. | ||
| + **You can veto a qualified beatmap set by posting the issues you think need to be addressed before reaching ranked, and then contacting a member of the QAT.** You must participate in the resulting discussion and attempt to reach a mutual agreement. The following conditions must be met before the veto is applied and the set is disqualified, however: | ||
| + The veto post must include a clear problem and reasoning for pausing the beatmap set's ranking process. | ||
| + The veto post must be at least 1 day old to allow for observation of test plays and additional feedback. |
There was a problem hiding this comment.
just to clarify, does this mean it's impossible to veto a map when it's less than one day away from ranking? that seems wrong
There was a problem hiding this comment.
no that's meant to be an exception, think I may have forgotten to include that bit:
"/.../ at least 1 day old (unless there is less than 1 day left until rank) to allow for /.../".
Raidencio
reviewed
Feb 22, 2019
wiki/Ranking_Criteria/en.md
Outdated
| @@ -92,6 +92,7 @@ Glossary | |||
| ### Guidelines | |||
|
|
|||
| - **Letterboxing and countdown options should be consistent between difficulties of a beatmapset.** | |||
| - **Avoid directly re-using your own ranked beatmaps in other ranked beatmaps.** This is to avoid unnecessary bloating of Ranked content. | |||
There was a problem hiding this comment.
Suggested change
| - **Avoid directly re-using your own ranked beatmaps in other ranked beatmaps.** This is to avoid unnecessary bloating of Ranked content. | |
| - **Directly re-using your own ranked beatmaps to rank other beatmaps is discouraged.** This is to avoid unnecessary bloating of Ranked content. |
"avoid" redundancy waffles
There was a problem hiding this comment.
adjusted (and made "ranked" --> "Ranked" everywhere for consistency)
cl8n
approved these changes
Mar 14, 2019
WalterToro
approved these changes
Mar 14, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
veto rule for beatmap nominators: https://osu.ppy.sh/community/forums/topics/833598
common sense clarification: https://osu.ppy.sh/community/forums/topics/844073
hybrid set bn rule: https://osu.ppy.sh/community/forums/topics/872345