If a track has more than 5 artists they must be substituted with Various Artists, similarly if a track is composed of 3 or more individual tracks, the title must be substituded to <Descriptor> Compilation.

The artists of a song must be tracable to existing people.

Any form of vs. such as Vs., VS and the likes are to be written as vs. only.

...and the likes are substituded to and asterisk

Brackets within artist or title fields should be separated from the other text surrounding it, unless there is obvious reason to not do so.

Cyrillic Romanisation: Use BGN/PCGN system for Russian/Cyrillic. Е and е should be romanised as ye if it stands alone or after a, e, ё, и, о, у, ы, э, ю, я, й, ъ, ь. In other cases, it should be romanised as e. ё should be romanised to ye, however, use yo or o to avoid usage of special characters. Ignore any other rules in the file provided, these are either irrelevant or wouldn't help in the game. If an artist uses a preferred romanisation, follow it regardless of this rule. For most of the other characters, refer to the first page of this document.

Russian Romanisation: Use BGN/PCGN system for Russian. Е and е should be romanised as ye if it stands alone or after a, e, ё, и, о, у, ы, э, ю, я, й, ъ, ь. In other cases, it should be romanised as e. ё should be romanised to ye, however, use yo or o to avoid usage of special characters. Ignore any other rules in the file provided, these are either irrelevant or wouldn't help in the game. If an artist uses a preferred romanisation, follow it regardless of this rule. For most of the other characters, refer to the first page of this document.

Shiguma wrote:

I believe that TV size cuts of songs should have the (TV Size) label on them, regardless of the official source. My reasoning for this is, when you search up a song, having the (TV Size) in the metadata won't affect searching for that song, while also making it very clear that whichever set you are looking at is the short version of a song. If we're bringing common sense into metadata, I don't see why we shouldn't do this.

Pachiru wrote:

"Guest mappers and storyboarders must be added to the tags of a beatmap set." People who makes the hitsounds shouldn't be added to the tags aswell or it's not mendatory?

Nevo wrote:

Pachiru wrote:

"Guest mappers and storyboarders must be added to the tags of a beatmap set." People who makes the hitsounds shouldn't be added to the tags aswell or it's not mendatory?

I definitely feel people who make hitsounds for a set should be required in tags, since they do play a large role in mapsets, also because a lot of hitsounders put forth plenty of time and effort into their work.

Nevo wrote:

Pachiru wrote:

"Guest mappers and storyboarders must be added to the tags of a beatmap set." People who makes the hitsounds shouldn't be added to the tags aswell or it's not mendatory?

I definitely feel people who make hitsounds for a set should be required in tags, since they do play a large role in mapsets, also because a lot of hitsounders put forth plenty of time and effort into their work.

If a track has more than 5 artists they must be substituted with Various Artists, similarly if a track is composed of 3 or more individual tracks, the title must be substituded to <Descriptor> Compilation.

Songs with German umlauts (ü, ö, ä and ß) must be romanised into two-letter combination (ue, oe, ae and ss).

Commas, vs., &, feat./ft., CV: must always use a trailing whitespace. Unless it is a comma, leading whitespace is also required.

If a song or artist are referred to in multiple ways on official sources provided by the artist, the mapper is free to choose any of the romanisations. The only exception to this is if the song already has a mapset in the Ranked Section, in which case the corresponding guideline applies to it.

Only use the Source field if the song comes from, is remixed from or specifically fan-made for a video game, movie, or series. Website names are not an acceptable Artist nor Source.

Guest mappers and storyboarders must be added to the tags of a beatmap set. This is to give credit where credit is due and helping others identify the main contributers of any given beatmap set.

For songs belonging to doujin circles, the circle name must be used over the vocalist or composer, unless these contributors are not part of the circle. In these cases the priority falls on vocalist followed by composer for instrumental songs.

Special unicode characters must be filtered to their nearest standard equivalent or removed from the Romanised Artist and Romanised Title fields within a .osu file. ★ ☆ ⚝ ✩ ✪ ✫ ✬ ✭ 🟉 🟊 ✮ ✯ ✰ and the likes are substituded to an asterisk. Corner Brackets have to be written as quotation marks instead. Other special characters are to be romanised or dropped on case-by-case basis.

ailv wrote:

Only use the Source field if the song comes from, is remixed from or specifically fan-made for a video game, movie, or series. Website names are not an acceptable Artist nor Source.

Does this include if the song was popularized by a specific game/movie/series? I beleive that's how it's being handled rn as well.

Naotoshi wrote:

agre w/ nevo abt hitsounders in tags.

i think forcing tv size is a bit stupid since "cut ver." for example isn't forced if it's not official yet it serves the exact same purpose. it takes players about 3 seconds to see if a map is tv size or not, and in many cases dropping it makes the title look much cleaner anyway.

Sieg wrote:

alright

Cyrillic Romanisation: Use BGN/PCGN system for Russian/Cyrillic. Е and е should be romanised as ye if it stands alone or after a, e, ё, и, о, у, ы, э, ю, я, й, ъ, ь. In other cases, it should be romanised as e. ё should be romanised to ye, however, use yo or o to avoid usage of special characters. Ignore any other rules in the file provided, these are either irrelevant or wouldn't help in the game. If an artist uses a preferred romanisation, follow it regardless of this rule. For most of the other characters, refer to the first page of this document.

I suggest to remove "Cyrillic" and leave it to case by case since current wording is ambiguous trying to cover all Cyrillic languages with different phonetics and different scenarios of romanisation, which is obviously wrong approach. So, reword it to

Russian Romanisation: Use BGN/PCGN system for Russian. Е and е should be romanised as ye if it stands alone or after a, e, ё, и, о, у, ы, э, ю, я, й, ъ, ь. In other cases, it should be romanised as e. ё should be romanised to ye, however, use yo or o to avoid usage of special characters. Ignore any other rules in the file provided, these are either irrelevant or wouldn't help in the game. If an artist uses a preferred romanisation, follow it regardless of this rule. For most of the other characters, refer to the first page of this document.

J1NX1337 wrote:

Brackets within artist or title fields should be separated from the other text surrounding it, unless there is obvious reason to not do so.

-> unless there is an obvious reason not to do so.
Slight grammar correction.

Kurai wrote:

- Cyrillic Romanisation should follow the BGN/PCGN system (except for the letter ё in Russian which should follow the GOST 2002(B) system). Read more here: http://up.kuraip.net/032209ex3724.pdf

Pachiru wrote:

For tags, from draft: "This is to give credit where credit is due and helping others identify the main contributers of any given beatmap set."

Since we should give feedback to the main contributors of the set, we need to put the person who made the hitsounding, which is an important part of the map, because without hitsounds the map is unrankable. If we give credit to someone who made something optional like Storyboard, we should add the hitsounds person to the tag aswell.

(also, don't forget to fix the typo on: "contributers" → "contributors")

ailv wrote:

If a track has more than 5 artists they must be substituted with Various Artists, similarly if a track is composed of 3 or more individual tracks, the title must be substituded to <Descriptor> Compilation.

What about albums? E.g If I were to map https://soundcloud.com/owslaofficial/se ... nctuary-ep the entirety of this ep mixed into one track, I can't see why I'd have to name it "Sanctuary EP Compilation" over just "Sanctuary EP".
suggest an alternative, this is a fair point

Songs with German umlauts (ü, ö, ä and ß) must be romanised into two-letter combination (ue, oe, ae and ss).

This doesn't make sense in certain cases, for example https://osu.ppy.sh/s/723626 wouldn't make sense as the "Ü" is simply a stylizing choice, it's intended to be a U with some fancy shmancy stuff.
limiting it to romanisation of german then because german words are affected

Commas, vs., &, feat./ft., CV: must always use a trailing whitespace. Unless it is a comma, leading whitespace is also required.

does this include "ft" or "feat" without a "."
now it does

If a song or artist are referred to in multiple ways on official sources provided by the artist, the mapper is free to choose any of the romanisations. The only exception to this is if the song already has a mapset in the Ranked Section, in which case the corresponding guideline applies to it.

How does this apply to https://osu.ppy.sh/p/beatmaplist?q=diao%20ye%20zong which has had maps ranked under "Diao Ye Zong" and "RD-Sounds".
if the song youre mapping has 2 ranked sets with both then you can go back to choosing, otherwise follow ranked unless that one was wrong

Only use the Source field if the song comes from, is remixed from or specifically fan-made for a video game, movie, or series. Website names are not an acceptable Artist nor Source.

Does this include if the song was popularized by a specific game/movie/series? I beleive that's how it's being handled rn as well.
example needed?

Guest mappers and storyboarders must be added to the tags of a beatmap set. This is to give credit where credit is due and helping others identify the main contributers of any given beatmap set.

Does this need to be extended to previous usernames?
does it say so? no.

For songs belonging to doujin circles, the circle name must be used over the vocalist or composer, unless these contributors are not part of the circle. In these cases the priority falls on vocalist followed by composer for instrumental songs.

I'm not sure if I'm interpreting this wrong, but shouldn't it be more something like guest composer + circle, to give accurate credit in those cases?
usually when that happens the song is a guest on an album anyways but im not sure myself more debate required.

Special unicode characters must be filtered to their nearest standard equivalent or removed from the Romanised Artist and Romanised Title fields within a .osu file. ★ ☆ ⚝ ✩ ✪ ✫ ✬ ✭ 🟉 🟊 ✮ ✯ ✰ and the likes are substituded to an asterisk. Corner Brackets have to be written as quotation marks instead. Other special characters are to be romanised or dropped on case-by-case basis.

I believe there should be some clarification between ' ' and " ", being used for romanization of 「 」, see https://osu.ppy.sh/s/735097, https://osu.ppy.sh/s/538136. Since British and American ways differ.
then clarify instead of saying that?

The same applies to the Source field if a romanised Source is preferred by the mapper.

ailv wrote:

If a track has more than 5 artists they must be substituted with Various Artists, similarly if a track is composed of 3 or more individual tracks, the title must be substituded to <Descriptor> Compilation.

What about albums? E.g If I were to map https://soundcloud.com/owslaofficial/se ... nctuary-ep the entirety of this ep mixed into one track, I can't see why I'd have to name it "Sanctuary EP Compilation" over just "Sanctuary EP".
suggest an alternative, this is a fair point

Compilation should be used in cases where the songs are not already part of a organized set of songs.

Songs with German umlauts (ü, ö, ä and ß) must be romanised into two-letter combination (ue, oe, ae and ss).

This doesn't make sense in certain cases, for example https://osu.ppy.sh/s/723626 wouldn't make sense as the "Ü" is simply a stylizing choice, it's intended to be a U with some fancy shmancy stuff.
limiting it to romanisation of german then because german words are affected

Can we state that this appleis speficially to Songs with a German title or artist fields then? Currently the wording implies that any song with those german umlaut characters would need to be romanized as such.

Guest mappers and storyboarders must be added to the tags of a beatmap set. This is to give credit where credit is due and helping others identify the main contributers of any given beatmap set.

Does this need to be extended to previous usernames?
does it say so? no.

I've seen discussion about this before, I think I've seen cases where the previous username was added to the online tags so a DQ wouldn't be needed. I think further discussion would be useful.

Special unicode characters must be filtered to their nearest standard equivalent or removed from the Romanised Artist and Romanised Title fields within a .osu file. ★ ☆ ⚝ ✩ ✪ ✫ ✬ ✭ 🟉 🟊 ✮ ✯ ✰ and the likes are substituded to an asterisk. Corner Brackets have to be written as quotation marks instead. Other special characters are to be romanised or dropped on case-by-case basis.

I believe there should be some clarification between ' ' and " ", being used for romanization of 「 」, see https://osu.ppy.sh/s/735097, https://osu.ppy.sh/s/538136. Since British and American ways differ.
then clarify instead of saying that? I don't know which one is better, i'd propose that bot are acceptable and up to choice.

the thing part nine wrote:

Word-by-word Romanisation: Each character must be romanised into a single, capitalised, separated word. Refer to this thread for examples and supplementary information.

the thing part thirty wrote:

Guest mappers, storyboarders, and hitsounders must be added to the tags of a beatmap set. This is to give credit where credit is due and helping others identify the main contributors of any given beatmap set.

the thing part forty two wrote:

Commas, vs., &, any variations of feat./ft., CV: must always use a trailing whitespace. Unless it is a comma, leading whitespace is also required.

Okoratu wrote:

4 yea idk either

If the creator of the mapset has done major edits to the .mp3, they are free to name it appropriately to signal that this song is a special version. In this case the original songs must still be clearly indicated in order for players to be able to search for the original songs.

Corner Brackets have to be written as quotation marks instead.

Other special characters are to be romanised or dropped on case-by-case basis.

Brackets within artist or title fields should be separated from the other text surrounding it, unless there is obvious reason not to do so. Reasoning like this would include syntactical use of brackets and the general typesetting of a song title or artist using them without whitespaces often and consistently across multiple platforms.

ailv wrote:

Corner Brackets have to be written as quotation marks instead.

Add an example of what a corner bracket is "⸤ ⸥" and " ｢ ｣ " since there are multiple forms.

Noffy wrote:

That's why it's in the glossary

Okoratu wrote:

also the source is a unicode field as such it can hold anything we want it to -> the mapper should have the choice to decide which one is shown in the client