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
forum
Report minor fixes here!
posted
Total Posts
92
Topic Starter
MBomb
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
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
Topic Starter
should prob make a thread for this, since that'd be an actual change to rcSinnoh wrote:
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
(i support 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.
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:
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
fixed
just an error on my part when adding things
ya i'll just merge this myself tbh
old
Avoid using combo colours with ~220 luminosity or higher. They create bright pulses during Kiai time which can be unpleasant to the eyes.
I worded this assuming you would use kiai time, but that's not always the case.fixed
Avoid using combo colours with ~220 luminosity or higher if Kiai time is used. Light colours create bright pulses during Kiai time, which can be unpleasant to the eyes.
just an error on my part when adding things
ya i'll just merge this myself tbh
Topic Starter
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
edit: done
Topic Starter
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:
needs to be changed toold wrote:
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.
posting here instead of a proposal as this is already how things are enforced, this is just more clearnew wrote:
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.
done
Topic Starter
some random stylization stuffs across mode-specific pages:
stuffs
- glossary capitalization is handled differently by all pages, should be standardized to match general page's capitalization (first word of a term capitalized, acronyms capitalized, everything else lowercased)
- catch difficulty names should be followed by colons instead of periods https://puu.sh/DmB2D/fa42b00452.png
- taiko using inconsistent diffname/gameplay titles to all other pages: https://puu.sh/DmB3h/13ba00387b.png vs. https://puu.sh/DmBBu/b51b11f768.png
- catch missing alternative difficulty names forum thread link (tho uhh i think that should kinda just be removed from the other pages lol its pretty obsolete) https://puu.sh/DmBZT/d204016293.png vs. https://puu.sh/DmBZu/4881f8edfd.png
- 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
- taiko misformats "overall" section https://puu.sh/DmBMy/2b40feb0d7.png vs. https://puu.sh/DmBOE/8e6cdab5c6.png
- catch diff-specific difficulty settings guidelines are not separated into their own section https://puu.sh/DmBSw/0a88a23fe0.png vs. https://puu.sh/DmBTv/bab0269a60.png
- taiko uses "OD" and "HP" instead of "Overall Difficulty" and "HP Drain Rate"
- oh uh https://puu.sh/DmBWT/b9b31a3cb1.png capitalization inconsistency on the general page, romanization should be lowercased
UndeadCapulet wrote:
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:
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:
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.
Topic Starter
so this happened https://osu.ppy.sh/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 "Usernames containing single characters separated by whitespaces must have the whitespaces replaced with underscores." to "Usernames 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
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 "Usernames containing single characters separated by whitespaces must have the whitespaces replaced with underscores." to "Usernames 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
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
Topic Starter
its more that we dont want ppl to be popping for the original username tag, so it's better to say "include" instead of just "replace"
the original username 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?
Topic Starter
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 ^^'
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 ^^'
MBomb
From osu!catch Overdose ranking criteria:
This seems a little strange wording just because every other rule/guideline with this structure talks in terms 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/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 terms 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."
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"
- Original:
- Change:
Dubstek wrote:
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..
" 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:
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.
Topic Starter
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
now featuring many unrelated changes from Pish&Clay RC Co. because both of us are easily bothered apparently
rc wrote:
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:
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!
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. Usernames containing single characters separated by whitespaces must have the whitespaces replaced with underscores."
should probably specify current username since that's what everyone has been following for the past few years
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. Usernames containing single characters separated by whitespaces must have the whitespaces replaced with underscores."
should probably specify current username since that's what everyone has been following for the past few years