This is a kinda nitpicky suggestion, but I think this part could be clarified more:

Ranking Criteria wrote: 69z3w

Mapsets must have a minimum drain time of 30 seconds.

currently, it can be read in a few different ways. does every map of the mapset need 30 seconds minimum? do all of them combined need 30? does only one map of the set need 30?

I know the correct interpretation is the first one, but it's not made very clear.

my suggestion is:
Every difficulty of a beatmapset must have a minimum drain time of 30 seconds.

or, replace "difficulty" for "beatmap", I can't really tell which term is preferred in the RC

@clayton "Beatmaps must have a minimum drain time of 30 seconds." seems to be the simplest solution.

also this reminds me that there are a metric fuckton of instances where the word "mapset" is used instead of "beatmapset" and they all need to be fixed, lol..


or we could get rid of all the instances of beatmapset bc that word is icky

I've got a PR open for this one too, seems same as what you suggest https://github.com/ppy/osu-wiki/pull/1905

edit: merged. I'll make a note to look into the wording

hi
some osu!mania stuff
i know the current one is temporary and new rc is about to come, temporary one should at least be cleaned up until the new one comes

Rules/General wrote: 3n1i3m

osu!topus (AutoPlay) must be able to achieve the full score (1,000,000) in all diffifculties.

diffifculties lol

Rules/General wrote: 3n1i3m

You can't have two notes in the same column that overlap each other, and there must always be a space between two notes in the same column.

isn't this just repeating itself? "You can't have two notes in the same column that overlap each other" is enough.

Rules/Timing wrote: 635xt

Use inherited timing sections and SV changes instead.

again, repeating itself. "Use inherited timing points (SV changes) instead" should be enough.
also, this rule uses the term "timing section", wouldn't using "timing points" be better?

i have tons of stuff more to say, but hopefully the new rc will fix them

timing section is the term used across the wiki, and it's used by the editor, tho points is the uh.. more noticeable term, to say the least.... /shrug

Very nitpicky stuff (In osu!catch ranking criteria).

Your map must theoretically be possible to SS. This means it must be possible to catch absolutely all fruits, including droplets.

Due to the definitions of fruit and droplet in the ranking criteria, including a droplet as a fruit isn't correct, because a fruit is listed as "A large object represented by a hitcircle, slider head, tail or repeat.". It'd be better to word it as " This means it must be possible to catch absolutely all fruits, drops, and droplets." It's a little more long winded, but I couldn't really think of a shorter way to write it that doesn't lead to something being left out. (I also know that it's quite obvious what an SS means really, but if we're including an explanation I think it makes sense for it to be clarified properly.)

Overall Difficulty should have the same value as the Approach Rate. This is just a standardized value, as Overall Difficulty does not affect gameplay nor the amount of fruits a spinner has, just the maximum score of a difficulty. For cases where the two values are not equal, the Overall Difficulty must be less than or equal to the Overall Difficulty of the next hardest difficulty.

Similar thing here, "nor the amount of fruits a spinner has" goes against the definition of fruit, as bananas aren't listed under the fruit definition. Again, fairly obvious what is meant, but it's probably better to list as "nor the amount of bananas a spinner has", for the sake of definitions.

Use the same slider tick rate on every difficulty as it is a property of the music rather than the mapping. However, lower difficulties may use lower tick rates to reduce accuracy requirements for newer players, providing they still follow the rhythm of the song. Using high tick rates purely to increase score/combo/difficulty is senseless.

This being the only place in the general section which has the sentence carry on from the main part to the explanation seems really strange to me, and actually confused me a tiny bit when I was reading through until I realised. Maybe best to just make it "This is because it is a property of the music rather than the mapping.".

A beatmapset's audio file must be no lower than 128kbps and no higher than 192kbps. Variable bit rate songs must average between that range.

imo this should be changed to a guideline where it must be followed unless there isn't a higher quality version of the song available

Sinnoh wrote: 2f4r3l

A beatmapset's audio file must be no lower than 128kbps and no higher than 192kbps. Variable bit rate songs must average between that range.

imo this should be changed to a guideline where it must be followed unless there isn't a higher quality version of the song available

should prob make a thread for this, since that'd be an actual change to rc
(i it btw)

Seeing that so many mappers are ignorant of the setup "Sample match playback rate"(to raise perfect fifth in NC mod). I want to suggest this:
A beatmap containing pitched hitsounds must open "Sample match playback rate" Of course, it doesn't matter in maps without pitched hitsound

Pitched hitsounds means hitsounds with pitch, like piano sounds and etc. Whether they're raised by perfect fifth depends on whether this setup is ticked. If not, players, when playing maps with pitched hitsounds, will hear inconsonant sounds.

Mcen314 wrote: 333r34

Seeing that so many mappers are ignorant of the setup "Sample match playback rate"(to raise perfect fifth in NC mod). I want to suggest this:
A beatmap containing pitched hitsounds must open "Sample match playback rate" Of course, it doesn't matter in maps without pitched hitsound

Pitched hitsounds means hitsounds with pitch, like piano sounds and etc. Whether they're raised by perfect fifth depends on whether this setup is ticked. If not, players, when playing maps with pitched hitsounds, will hear inconsonant sounds.

i really agree with this but need it's own thread

For catch specific RC, I merged Standard mode's combo colour rules, but reworded them because combo colour hax does not exist in ctb


old I worded this assuming you would use kiai time, but that's not always the case.

fixed

just an error on my part when adding things
ya i'll just merge this myself tbh

https://puu.sh/CRj9T/4c7ecb6baa.png that last "feat." should be written in the fancy way

https://github.com/ppy/osu-wiki/pull/2120 covers last post and a bit more

the link to Modified Hepburn could be fixed. it currently links to https://en.wikipedia.org/wiki/Hepburn_romanization#Features_of_Hepburn_romanization which is now just https://en.wikipedia.org/wiki/Hepburn_romanization#Features

edit: done

[deleted as part of purging my old post history]

^ https://github.com/ppy/osu-wiki/pull/2148

there has been some confusion about spread rules. the intention when oko and i wrote them was to require all diffs to reach minimum play time requirements in order for a set to qualify for higher lowest diffs. this is how it's been enforced since the rule was added (at least, when i noticed a set needed it or was asked about it). the current wording apparently doesn't make that clear enough so after some bn server discussion this consensus was reached:

old wrote: 5l3j12

If the drain time of the highest difficulty is...

...lower than 3:30, the lowest difficulty of each included game mode cannot be harder than a Normal. Because osu!mania does not have a difficulty-specific Ranking Criteria yet, an osu!mania beatmapset's Normal difficulty is defined as a difficulty below 2.00 stars. For hybrid beatmapsets that include osu! difficulties, the additional modes' lowest difficulties cannot be harder than a Hard.
...between 3:30 and 4:15, the lowest difficulty of each included game mode cannot be harder than a Hard.
...between 4:15 and 5:00, the lowest difficulty of each included game mode cannot be harder than an Insane.
...anything higher, the beatmapset is exempt from reasonable spread rules.

Lower difficulties can use their play time as a metric instead of drain time, but their drain time must be equal to at least 80% of their play time. (Not applicable to difficulties below 30 seconds of drain time.) Judgement regarding the suitability of gameplay elements used for any lowest difficulty Hard and Insane difficulties is up to the Beatmap Nominators and Quality Assurance Team for the corresponding game modes.

needs to be changed to

new wrote: 214035

If the drain time of each difficulty is...

...lower than 3:30, the lowest difficulty of each included game mode cannot be harder than a Normal. Because osu!mania does not have a difficulty-specific Ranking Criteria yet, an osu!mania beatmapset's Normal difficulty is defined as a difficulty below 2.00 stars. For hybrid beatmapsets that include osu! difficulties, the additional modes' lowest difficulties cannot be harder than a Hard.
...between 3:30 and 4:15, the lowest difficulty of each included game mode cannot be harder than a Hard.
...between 4:15 and 5:00, the lowest difficulty of each included game mode cannot be harder than an Insane.
...anything higher, the beatmapset is exempt from reasonable spread rules.

Difficulties lower than the highest difficulty can use their play time as a metric instead of drain time, but their drain time must be equal to at least 80% of their play time. (Not applicable to difficulties below 30 seconds of drain time.) Judgement regarding the suitability of gameplay elements used for any lowest difficulty Hard and Insane difficulties is up to the Beatmap Nominators and Quality Assurance Team for the corresponding game modes.

posting here instead of a proposal as this is already how things are enforced, this is just more clear

done

some random stylization stuffs across mode-specific pages:

UndeadCapulet wrote: 1a6q4h

catch uses super cute section dividing lines https://puu.sh/DmBEK/3f3cc89146.png can we add these to the other pages too they're lovely

rules/lines aren't supposed to go before top-level headers so I'm removing them. what you'd probably want to suggest instead is a different top-level header style for the wiki (or... second-to-top level I guess. sort of confusing because the only "top-level" headers are at the beginning of articles to control the display title)

edit: done now

wording here still references the QAT, it should be changed from

Difficulties lower than the highest difficulty can use their play time as a metric instead of drain time, but their drain time must be equal to at least 80% of their play time. (Not applicable to difficulties below 30 seconds of drain time.) Judgement regarding the suitability of gameplay elements used for any lowest difficulty Hard and Insane difficulties is up to the Beatmap Nominators and Quality Assurance Team for the corresponding game modes.

to

Difficulties lower than the highest difficulty can use their play time as a metric instead of drain time, but their drain time must be equal to at least 80% of their play time. (Not applicable to difficulties below 30 seconds of drain time.) Judgement regarding the suitability of gameplay elements used for any lowest difficulty Hard and Insane difficulties is up to the Beatmap Nominators and Nomination Assessment Team for the corresponding game modes.

will come as part of a larger change on the wiki, for now there's no harm in keeping this since the meaning is the same

RC wrote: 6p1460

No two hit objects can be placed on the same tick. This includes hit circles, starts and ends of sliders, and starts and ends of spinners. osu!mania beatmaps are exempt from this.

This seems to exclude slider and spinner bodies, can this made clearer to avoid confusion?

RC wrote: 6p1460

No two hit objects can be placed on the same tick. This includes hit circles and the duration of sliders and spinners. osu!mania beatmaps are exempt from this.

so this happened https://osu-ppy-sh.cinevost.com/beatmapsets/417408/discussion/-/generalAll#/1003431

kinda saw this comin when i was fixing this before ^^'

tl;dr in this rule in metadata technical section: https://puu.sh/DBPd9/903aea7b7e.png change "names containing single characters separated by whitespaces must have the whitespaces replaced with underscores." to "names containing single characters separated by whitespaces should also include a tag with the whitespaces replaced with underscores." cuz it looks like we're saying the other one shouldnt be in tags

the current rule is actually correct, apparently by accident. it's confusing because there's an issue with elasticsearch configuration on the website at the moment

client -
no concept of search priority here, just blind matching each search term to the tags, so either spaces or underscores are fine

website -
- "mapper_name" will never be matched by a "mapper name" search, this is unintended and will be fixed
- "mapper name" will be matched by a "mapper name" search, but the search boost for tags is so low (0.5, compared to every other metadata's 1.0) that your chances of finding correct results from a multi-word search are tiny. if you happen to find the map you're looking for, it's only because one word of the mapper's name was uncommon enough to not match other results. this is not the ideal way to be writing single tags and it shouldn't be encouraged

its more that we dont want ppl to be popping for the original name tag, so it's better to say "include" instead of just "replace"

the original name tag is (or will soon be) 100% useless if you've already got the underscored version. just want to confirm that redundancy is OK for ranked?

yeah tag redundancy is w/ev

i guess the optimal solution would be one that requires underscore ver w/out making it sound at all like spaces ver is illegal so mapper can include it if they want, but i cant figure out the wording for that ^^'

From osu!catch Overdose ranking criteria:

"At least 62 ms must be left between objects and the start of spinners to ensure readability. As an example, a 1/6 gap would be required at 160 BPM, whereas a 1/4 gap would be required at 240 BPM."

This seems a little strange wording just because every other rule/guideline with this structure talks in of 120BPM and 160BPM, not 240BPM and 160BPM (Except the ones regarding 1/3 at 80BPM, since this would be 1/1.5 at 160BPM, which would make no sense to a lot of players), including the one regarding HDashes on rain, which uses the same overall time. Would make sense to change this wording to as follows for consistency with the rest of the RC.

"At least 62 ms must be left between objects and the start of spinners to ensure readability. As an example, a 1/6 gap would be required at 160 BPM, whereas a 1/8 gap would be required at 120 BPM."

Sorry. I posted this on Change- an unnecessary and urgent manner



Since osu!mania RC doesn't say anything about "Triple" but instead use "Hand" which means three notes pressed at the same time.

So it will be good to remove that "Triple" to "Hand" or just add description about "Triple"

1. Original:

Occasional Triples can be used in a stream with a note that their distances are further than a measure (4 beats).

1. Change:

Occasional Hands can be used in a stream with a note that their distances are further than a measure (4 beats).

Dubstek wrote: 5w1n4b

So it will be good to remove that "Triple" to "Hand" or just add description about "Triple"

change should be coming in https://github.com/ppy/osu-wiki/pull/2551

while I'm translating Osu!mania RC , I think I got some little problem? again.

" Additional guidelines for 7 key Normal difficulties:

Avoid chords with more than 3 notes. This includes long note patterns that involve notes in more than three columns.
Bracket patterns should be used sparingly. "

Since osu!mania RC doesn't say anything about "Bracket" pattern , it will be good to add a description of it will stop the confusion. I think..

added definition in https://github.com/ppy/osu-wiki/pull/2620

rc wrote: 5i23o

Any form of feat., ft., Ft., etc. must be written as feat. when it is used as a marker signifying a featured artist in the song.

From standardisation in metadata rules.

i think it could be reworded to "Any form of feat., ft., Ft., etc. must be written as feat. when it is used as a marker signifying an artist featured in the song."

Currently the wording includes "featured artist" which is a term used in the game now. It can be confusing for non-native english speakers.

https://github.com/ppy/osu-wiki/pull/2797

unintended ambiguity in https://puu.sh/EL5DG/ffabfa02ba.png, it makes it appear as if the perfect stack rules don't also assume 180bpm, should read "Rhythm related rules and guidelines" blabla so we dont need to keep telling bn's that 90bpm easies can actually have 1/1 stacks

https://github.com/ppy/osu-wiki/pull/2886

now featuring many unrelated changes from Pish&Clay RC Co. because both of us are easily bothered apparently

rc wrote: 5i23o

No two hit objects can be placed on the same tick. This includes hit circles and the durations of sliders and spinners. osu!mania beatmaps are exempt from this.

under this rule, three or more hit objects on the same tick would be rankable. to further clarify the rule, it should be worded as

update wrote: v6k10

Two or more hit objects cannot be placed on the same tick. This includes hit circles and the durations of sliders and spinners. osu!mania beatmaps are exempt from this.

if there are three or more, there are also two. this doesn't need clarification

if you want to get really technical with the wording, "no two hit objects" is equivalent to saying "no combination of two objects from a set". three objects on the same tick would break this rule 3C2 == 3 times!

True, it's completely redundant if someone went out of their way to bend rules like that in such a manner.

Under standard specific RC in difficulties listed "Insane" is missing the little emoji. https://i.imgur.com/9wx0tDX.png

noticed that too, I'll try to get it fixed when updating the difficulties page for the RC thread about taiko diff names (soon!)

dunno if this is still alive

rc currently says "Guest mappers, storyboarders, skinners and hitsounders must be added to the tags of a beatmapset. This is to give credit where credit is due and help others identify the main contributors of any given beatmapset. names containing single characters separated by whitespaces must have the whitespaces replaced with underscores."

should probably specify current name since that's what everyone has been following for the past few years

I don't see how it could be confused to mean anything but current name

osu!taiko Ranking Criteria - Futsuu Guidelines wrote: v6y4h

1/3 patterns should not be longer than two notes. Anything longer is very situational and usually too complex for newer players. Patterns like these should be followed by a rest moment within 2/1 and not contain any 1/2 or faster patterns within that time.

I would like to suggest a minor change to have a slight rewording of the above recently amended guideline for better readability. The last sentence should be rewritten as "Patterns like these should be followed by a rest moment within 2/1 and be avoided in conjunction with other patterns that are 1/2 or faster within that time." as subject-object disagreement occurs at the moment.

not sure what you mean by "subject-object disagreement" (subject-verb ?), the sentence is grammatically correct as is

anyway to make it a little simpler, how does this sound: "These patterns should be followed by a rest moment within 2/1, and patterns that are 1/2 or faster should be avoided during that time." ?

I mean "Patterns like these should not contain any 1/2 or faster patterns within that time." is logically not correct. Patterns with certain snaps (1/3, 1/2 etc.) are to be treated individually so a pattern cannot contain another pattern.

Ranking Criteria wrote: 69z3w

If the source of the song is available in both unicode and romanised formats, the option not used in the source field should be added to tags

There is no period.

both fixed

taiko rc (oni) wrote: 372m3z

At least 1 rest moment which is 1/1 or longer should be inserted after 16/1 to 20/1 of continuous mapping. Less frequent rest moments or shorter ones may put too much strain on beginners.

...beginners?

lol. "players" is probably better

the wording of that last sentence doesn't make a lot of sense anyway. "Less frequent rest moments or shorter ones may put too much strain" implies the short rests are putting strain, but it's actually the other parts of the mapping besides the rests that are putting too much strain.

O!m overall guidelines section:
The number is shown in brackets after the BPM range in the song selection, e.g. BPM: 60-160 (130)
Those are parentheses (), brackets are square [].

fixed fixed

There's a minor grammar mistake here:

"Hitsounds must be audible. Their purpose is to provide , so hitsounds with extremely low volume or samples that blend with a song's samples are unacceptable. Specific game modes list exceptions to this rule on their respective ranking criterias."

The word "criterias" doesn't exist, criteria is already the plural form of criterion.

𝒻𝒾𝓍𝑒𝒹

Ranking Criteria wrote: 69z3w

This set of ranking critera lays out rules and guidelines that beatmaps must follow in order to progress through the beatmap ranking procedure.

criteria is misspelled

can we change the title of ranking criteria page to title case

Ranking criteria -> Ranking Criteria

RC is usually referred to (especially elsewhere on the wiki) in plural, like "these are the ranking criteria", rather than in singular as a document, "this is the Ranking Criteria". I think that was the main reason it ended up as a common noun in most places. and wiki titles are sentence cased, so that's why R is capital but not C

will fix blixys typo

now that 1/5 and 1/7 are built-in snap divisors, the examples here should be changed to ones that still aren't ed, like "(e.g 1/11, 1/32)"

Accomodating for objects in musical sections requiring uned beat snap divisors (e.g. 1/5, 1/7).

Objects must be snapped to timeline ticks according to AiMod. Objects in a musical section requiring uned beat snap divisors (e.g. 1/5, 1/7) can either:

fixed, thanks

Easy:
Objects 1 beat apart or less must not fully overlap.
'fully' seems superfluous, or at least define what a 'partial overlap' would look like. ty

icytors wrote: 6a55x

Easy:
Objects 1 beat apart or less must not fully overlap.
'fully' seems superfluous, or at least define what a 'partial overlap' would look like. ty

its referring to perfect stacks, this should be defined in the glossary unless something got fucked up (which is possible? since ive been dead theres been some weird glossary shenanigans idfk)

yeah it doesn't seem to be on the overlap glossary page, adding it there would also fix the rule for other diffs

what the fuck is this garbage

"fully", "perfectly", "completely" etc overlapping is when something is entirely contained or covered by the other. "partial" would be any overlapping where that's not the case. isn't this common wording in english? i don't feel like it should need explanation

General RC - Metadata wrote: 2a3c1e

Metadata that exceeds the field's limits (81 characters) must be shortened.

The current wording is really confusing, as the maximum allowed number of characters is 80 and titles/artist names that are exactly 81 characters cannot be submitted. I'd suggest changing it to something like this to avoid ambiguities:

Metadata that exceeds 80 characters must be shortened.

General Ranking Criteria > Audio > Guidelines wrote: 1y6ok

If you do not beatmap the last 20% of your beatmapset's audio file, it should be cut.

This should just say "If you do not map the last 20% of your beatmapset's audio file, it should be cut." because it makes more sense and the verb map is used more often than beatmap.

Glossary > Beatmapset wrote: 712z3p

...some beatmaps from a beatmapset may specifically contain a certain sounds, background images, or storyboards that are separate from the others.

Should just say "...some beatmaps from a beatmapset may specifically contain certain sounds, background images, or storyboards that are separate from the others." It shouldn't say "contain a certain sounds" because "a" would be used for a singular sound and not the plural.

edit: found another thing

General Ranking Criteria > Timing > Rules wrote: 192mk

If the same video appears in multiple difficulties, it must always have the same offset(s).

Should just say "offset." rather than "offset(s)." because a video can only have 1 offset and all similar videos must have the same offset, so adding the "(s)" is unnecessary.

People that I have asked seem to agree that >=5:00 marathons are supposed to be exempt from all spread rules.
But currently, the only place where the 5:00 length is clearly mentioned is in the rule for what the lowest difficulty of a mapset can't be higher than, which is not the only spread rule.

To clarify this, another clause should be added between the third and fourth bullet points of this section:


Saying:
...5:00 or higher, the mapset is exempt from all spread rules.

Yes, HX marathon spreads and the like are already stated to be rankable earlier in the "starting from the lowest difficulty level dictated by the drain time" rule, but this can be potentially misinterpreted (as I did), and specifying it under the bullet points in the screenshot just makes it much easier to understand in general since the bullet points in the screenshot are absolutely the part people look at the most.
This also clarifies that marathons below hard diffs are rankable on their own, as was the intention looking at the context of the original draft of these rules here.


Edit: It seems a lot of people in the discord I talked about this in were confused because this is a clause that used to be in the RC but was removed at some point, and people didn't realize it wasn't there anymore. I'm just saying to add it back because it's pretty important and helpful

clayton wrote: 5b1y29

"fully", "perfectly", "completely" etc overlapping is when something is entirely contained or covered by the other. "partial" would be any overlapping where that's not the case. isn't this common wording in english? i don't feel like it should need explanation

Very late but I kinda interpretted 'fully' as "perfectly". I'm just wondering why the word 'fully' has to be used, it's either overlapped or it's not. I must have misunderstood the term "overlap". I thought overlap meant "perfect on top of eachother" by default.

UndeadCapulet wrote: 1a6q4h

its referring to perfect stacks, this should be defined in the glossary unless something got fucked up (which is possible? since ive been dead theres been some weird glossary shenanigans idfk)

But the page says an overlap is not a stack...? I would just put the rule as "Stack leniency must be high enough so any perfectly overlapped circles will stack" or something.

o i guess i forgot to link the thread mir and i started about this, since its part of a larger issue w/ how osu!rc glossaries got removed community/forums/topics/1294813?start=8030006 ill also try to regrab mir when we're both free to work on this again

The article "Timing songs with #/8-Signatures" has a few issues

Here is the article for reference

Issue 1: In the beatmap .rar file, the difficulty "6/4" for the song "Leonard Bernstien - America" has no objects (I'm unsure if this is intentional or not but it's something to point out as all the other difficulties in each of the songs have objects). In addition, the "6/4" difficulty is always referred to as the "6/8" difficulty in the actual article.

Issue 2: The article refers to the writer as "I" multiple times
Ex. 1 "In this difficulty, I timed everything in 3/4-signature..."
Ex. 2 "When talking about the 3/4-difficulty in Leonard Bernstein's "America", I mentioned that..."

This makes the article read off as a forum post rather than a part of the ranking criteria. I have 2 suggestions to fix this, my first being credit the person/people who originally made this through a sentence like "Posted by person who made it" so that the self-reference makes more sense or change the "I" to something else that fits
Following Ex. 1: "In this difficulty, everything was timed in 3/4-signature..."

can wee add "&" to the list regarding "Commas, vs., feat., CV: and any other symbols linking or designating artists must include a trailing space. Excluding commas, a leading space is also required if the marker is preceded by a word." because it gets asked a lot and it's very commonly used thank you

An issue on new hitsound RC of osu!mania which may cause misunderstandings.

General Ranking Criteria -> Audio -> Rules wrote: l47

osu!mania beatmaps do not require hitsound additions. This is to allow for easier approachability to osu!mania mappers of different upbringings. It is still highly recommended to add hitsounds to improve the feel of your beatmaps.

Actually Hitnormal is still needed. But for new beginners it can be misunderstood into "osu!mania do not require any of hitsound" Reason are as follows:
Firstly, "additions" isn't a strong stress. And the definition of "addition" is not bolded. New beginners tend to read the bolded part more. And Bolded part is "Beatmaps must be hitsounded." and "osu!mania beatmaps do not require hitsound additions." Thus ignoring the word "addition" and misunderstood.
Secondly is the wording of "still highly recommended to add hitsounds". In the word "highly recommend" it has a meaning of "it's ok of you not having hitsound". It's contradict to "Beatmaps must be hitsounded."

My idea is as follow:

new wrote: 214035

osu!mania beatmaps do not require hitsound additions. But hitnormals is still needed. This is to allow for easier approachability to osu!mania mappers of different upbringings. It is still highly recommended to add full set of hitsounds with both hitnormals and additions to improve the feel of your beatmaps.

"hitsound additions" in the bold part is already explained in the line above it. might be easy to miss though. I think the wording is fine either way, but maybe "hitsound additions" should link somewhere that explains hitnormal vs. addition in more detail.

agree "hitsounds" in the last sentence is weird, should be changed to "additions" or "hitsound additions"

edit: updated RC

There's a minor mistake in the guideline

If multiple metadata options are available, priority should be given to the option which is most easily recognisable and traceable back to the original song or source. Official romanisations and translations are preferred for romanised fields so long as they are easily found and commonly recognised.

which was added a few months ago (didn't notice until now).

See this post in the relevant thread. Basically, remove the "and translations" part.



Also I happened to notice that some things mentioned in this thread were most likely overlooked or not implemented? It'd be nice to check those too.

changes to rules need their own thread in this forum; this one's only for clarifying wording etc.

and hard to tell if that was a "mistake" because nobody responded to the linked post

It is a wording mistake which I explained in that post (the way it's written implies something that doesn't match how the guideline is being used/enforced, it doesn't change anything).

u can open a PR on wiki for it, regardless I think should double-check with someone originally involved in that rule to confirm that it's ok to change

I don't really know how to open a PR and I feel like making a new thread here would be pointless since this subforum is pretty dead anyway. Is there any other way of getting this forward?

General Ranking Criteria > Video and background > Rules wrote: 54725x

A video's audio track must be removed from the video file. The audio track in video is not used in osu!, so removing it reduces that file size of the beatmap. This includes videos with muted audio tracks.

a missing article and two wrong words:

The audio track in a video is not used in osu!,

could also use "The audio track in the video..." but "a" feels better to me for some reason

soand removing it reduces thatthe file size of the beatmap.

the audio track not being used and its removal reducing file size are two separate justifications for the rule, and removing the track would reduce file size even if it was used in osu!, so using "so" there makes no sense

full proposed wording:

A video's audio track must be removed from the video file. The audio track in a video is not used in osu!, and removing it reduces the file size of the beatmap. This includes videos with muted audio tracks.

sukamenromato

There must not be any obscene imagery in the background/storyboard/video content. This includes nudity, near-nudity, sexual references, violence, drug abuse, etc. See Visual Content Considerations for more detailed rules.

Nudity is allowed according to the VCC, meaning the summary on the RC main page is wrong.

"Drug abuse" should also be changed to "Some forms of drug use"

I have two PRs open that don't change rules but still may be opinionated rewordings-

"Reword comparisons of times and rhythms in RC" https://github.com/ppy/osu-wiki/pull/10252
"Clean up difficulty naming articles" https://github.com/ppy/osu-wiki/pull/10253

osu!- and osu!taiko-specific RC for drain time rules has redundant of each included game mode clause, which might come from copy-paste result after RC separation. This shouldn't exist as the drain time and minimum difficulty rules only dictate the respective mode.

General Ranking Criteria > Beatmap > Rules
"there cannot be any drastically large difficulty gaps between any two difficulties."

I believe that since people find difficulty subjective, the ranking criteria should clarify the nature of what "difficulty" means to avoid mod posts like this one relating to "Spread issues", given that the star rating difference is larger to what people usually see.

I suggest adding the following line to clear things up: "there cannot be any drastically large difficulty gaps between any two difficulties. However, the difficulty gap should not be assessed by using the star rating system due to it not reflecting a beatmap's objective difficulty."

doesn't seem like an issue to me, people are free to judge difficulty how they want, and in both of these example threads it was quickly determined to not be a concern

https://osu-ppy-sh.cinevost.com/wiki/en/Guides/How_to_time_songs

For the example of songs that require multiple red bars, both "Bad Apple" and "kemu's Ikasama Life Game" links no longer work.

^ https://github.com/ppy/osu-wiki/pull/11404

General Ranking Criteria > Audio > Guidelines

We should probably rephrase
"If you do not beatmap the last 20% of your beatmap's audio file, it should be cut."
because honestly the wording is not good.

Proposing the amended guideline:
"Each difficulty in a beatmap should end at least 80% of the way through the song. If not, then the audio file should be cut."
That stops any ambiguous wording left with the first guideline.

Posting it in here first in case there is any misunderstanding with the allowances of this rule regarding the other gamemodes.

I wouldn't be comfortable changing this without a discussion because it's ambiguous rn how that's supposed to be read (and maybe on purpose? you never know)

just gonna link this in the rc rewrite server and hope it can be addressed then

Matadata RC is vague

I'm making this post because of this(https://osu-ppy-sh.cinevost.com/beatmapsets/2182114/discussion/-/generalAll/total#/4548503) post on a map, where its debated about a certain rule of the Metadata RC.
There shouldn't be a situation where people have to guess the meaning of the ranking criteria, and it should be clearly stated what rules are optional and what aren't.

I'll look into the RC more when I have time, as I'm writing this in a rush and posted this so it can be acknowledged.

Taken from https://github.com/ppy/osu/discussions/29590