Update activity requirements in Beatmap Nominator rules #12381
+27
−22
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
aceticke
reviewed
Nov 1, 2024
cl8n
requested changes
Nov 2, 2024
| | Hybrid | 3 nominations, with at least 1 per proficient game mode | | ||
| Beatmap Nominator activity is measured via nominations[^multi-key-mode], and is evaluated during regular BN evaluations, which happen around every 90 days. | ||
|
|
||
| ### Minimum activity requirements |
Comment on lines
+26
to
+27
| - Falling below **4** nominations in a 90-day period will result in a removal. | ||
| - Falling below the **6** nomination requirement with **4** or more nominations will result in an activity warning. |
There was a problem hiding this comment.
Suggested change
| - Falling below **4** nominations in a 90-day period will result in a removal. | |
| - Falling below the **6** nomination requirement with **4** or more nominations will result in an activity warning. | |
| - An activity warning will be issued when failing to meet this rule. | |
| - Falling below **4** nominations will always result in removal from the Beatmap Nominators. |
maybe? it felt weird for me for thsi rule to be formatted like: here's a rule, actually here's a second rule, here's what happens when you break the first one
something similar would apply to the next lines about hybrid
| - Hybrid Beatmap Nominators must nominate at least **3** beatmaps per proficient game mode over a 90-day period. | ||
| - Falling below **2** nominations in a given game mode in a 90-day period will result in a removal from that game mode. | ||
| - Falling below the **3** nomination requirement in a given game mode with **2** or more nominations will result in an activity warning in that game mode. | ||
| - When warned for activity, minimum activity requirements must be met over the course of one month. |
There was a problem hiding this comment.
I don't think you mean minimum activity for the entire month because it's impossible to instantly start meeting the minimum once you've been warned
is it supposed to be, meeting the activity minimum after a month?
(also small thing but 30 days is probably easier to understand here than 1 month)
| - When warned for activity, minimum activity requirements must be met over the course of one month. | ||
| - Failing to meet the required minimum when being warned for it within a period of 1 year will result in a removal from the Beatmap Nominators. | ||
|
|
||
| When a Beatmap Nominator's evaluation is created, and they still need to meet their minimum activity requirements, they will receive a reminder via the [NAT bot](https://osu.ppy.sh/users/6616586) and will be given **7** days to meet their quota. |
There was a problem hiding this comment.
not enough details to understand how this part affects all of the warning rules above, or at least it's really confusing
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.
the following changes were a result from multiple NAT discussions and an internal VC meeting.
we've already made the required bnsite changes and have started enforcing this a short while ago
main BN page translations technically still use the correct link from their respective rules outdated translations so SKIP_OUTDATED_CHECK