Skip to content

Conversation

@SisypheOvO
Copy link

@SisypheOvO SisypheOvO commented Nov 20, 2025

Main Changes:

  • The two articles improved. Details:
    • Beatmap_ranking_procedure:
      • Added two See also for readers to better understand two frequently mentioned concept below Article Title.
      • Improved how "how many nominations are needed for qualification" is explained with article content and Notes at the bottom.
      • Moved things unrelated to "Qualification" to right places ( e.g. things about DQ changing the rank timer are moved to /Ranking_queue, things about problems are moved to #nomination-resets, things about "qua to rank" are moved to #rank )
      • This article is about all "moments" through out the ranking process. So the Nomination reset/DQ/Veto moments need to be clarified. Created a new section for all obstructions a beatmap may meet during the Qualified status.
      • The Nomination resets part is improved: tell what it is and then what it ensures. Also improved explanation in more details.
      • Created a sub -ection for briefly explaining veto.
      • Changed #ranked to #rank to emphasize it as a process.
      • Added more Wiki links for readers to click for more information.
    • Beatmap_ranking_procedure/Ranking_queue:
      • Things about DQ changing the rank timer are moved here from Beatmap_ranking_procedure
      • Explain clearly how the qualified time works counting down for the beatmaps to get ranked.

Other Changes:

  • Fixed links pointing to Beatmap_ranking_procedure#ranked which is changed to #rank by me.
  • Improved Beatmap/Category slightly: nominations needed to qualify a map need clarification.

SKIP_OUTDATED_CHECK

SisypheOvO and others added 2 commits November 21, 2025 00:49
…nking_queue`

* The two articles improved.

* Fixed links pointing to `Beatmap_ranking_procedure#ranked` which is removed by me.

* Improved `Beatmap/Category` slightly: nominations needed to rank a map need clarification
@osu-wiki-observatory
Copy link

Someone else has edited same files as you did. Please check their changes in case they conflict with yours:

@github-actions
Copy link
Contributor

Thank you for contributing to the osu! wiki.

Please take note of the following:

  • Make sure you've read this self-check checklist.

  • Translations that have not been reviewed by a native speaker will be merged after a minimum of 1 week. If there are no reviewers for your language, please mention it explicitly.

  • Refrain from spamming the Update branch button. A maintainer will do this before merging anyway.

  • Apply review suggestions in batches from the Files changed tab like this:

    Demo GIF

See the contribution guide for more information.

All changes are run through continuous integration checks, which provide automatic detection of common errors. If you need help with decrypting CI check error messages, or with any other issues, ask in the #osu-wiki channel on the osu! Discord server.

@SisypheOvO
Copy link
Author

Reminder: articles that are changed alot need their translations edited as"outdated-translation" and give the commit hash😌

@Hiviexd
Copy link
Member

Hiviexd commented Nov 20, 2025

manually outdating translations is no longer needed and is automated, so no need to worry about it.

@SisypheOvO
Copy link
Author

manually outdating translations is no longer needed and is automated, so no need to worry about it.

ok thanks for that info! I learnt that from commits from like four years ago sorry abou that 🥲

SisypheOvO and others added 3 commits November 21, 2025 04:34
…g_queue`

A sentence in `Beatmap_ranking_procedure` misses some part.

And it should be linked to `Ranking_queue#dq-and-re-qualification`
Copy link
Member

@peppy peppy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine? Would want a second opinion though.

@MChecaH MChecaH self-assigned this Nov 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants