1. osu! forums
  2. osu!
  3. Development
  4. Ranking Criteria
  5. Finalized/Denied Amendments
show more
posted
just stop trying to force diffnames on things that have 0 relation to whatever you're trying to force on it. is it so hard to be normal? the word "frozen" has absolutely zero relation to usao wubstep remix #30 so why is it being used? you can say anything is a part of a "series" if you want to. we had this in ctb with the diff name "wilderness" related to a user and we disallowed it because it was being used on maps that just had no correlation at all to what he was using as a diffname. outer oni still is a play on a standardized level of difficulty, just like "kumanoverdose" in ctb for example. raidcore, frozen, etc have clear relations to usernames without relation to the song and shouldn't be allowed. things like melancholy or cataclysm (two of sotarks's diff names) have relation to the song, or to the band in general, which allows that to be acceptable.
posted

Nao Tomori wrote:

a rule with exceptions is a guideline.
agree with this
posted
yeah move that to guidelines please
posted

eiri- wrote:

Nao Tomori wrote:

a rule with exceptions is a guideline.
agree with this
to elaborate on this, we're generally trying to standardize most guidelines into being "rules with expressly stated instances where the exceptions will be made". most recent rc changes have had this format.

moving this to guidelines so ppl can use an adjective related to their username or wtfever would pretty much make this guideline totally useless. we should avoid "moving outdated rules to guidelines so we can just totally ignore them" at all times, it just causes more cleanup later.

we should just remove the rule altogether instead, it was added at a time when star rating was actually useless, but now our sr's are usually pretty telling of what difficulty a map is so there's no real reason to keep it other than "some people didn't like username-only diffnames", which isn't a very good reason.
posted
iirc, it was added when difficulties weren't very clear, regardless of star rating. It wasn't always the hardest difficulties getting custom names, but even easier ones.
posted
@UndeadCapulet: It existed because one) peppy hated the idea to use the own username not altered as difficulty name and second) to prevent sets like https://osu.ppy.sh/s/32726. A map in the time when this was discussed was unranked because of these circumstances.

this was less because of the poor SR calculations at this time, this was additionally included in the reasoning but not the major reason.
posted
if i named a difficulty "pishi" or "pishifat", it wouldn't be valid for ranking. if people are talking about stuff like pishInsane not being enforced as unrankable, i can understand editing the rule accordingly, but removing it entirely makes the first case okay, which shouldn't happen

im not sure how melancholy/posthomus/frozen etc are related to the rule either. they're not related to a username, they're just used by certain users frequently
posted
just my 2 centavos

pishifat wrote:

im not sure how melancholy/posthomus/frozen etc are related to the rule either. they're not related to a username, they're just used by certain users frequently
the first two are correct, but the example pointed out in the original post is a more delicate case since the mapper’s name directly relates to it (ice -> frozen) while it has no relation to the song itself — which is why the topic is being brought up in the first place

i’d be ok with either tweaking the rule to adapt it to the guideline criteria UC has mentioned. i don’t see a need to fully kill it, but rather just modify it enough, as it would still prevents mappers from doing as Stefan mentioned but would also allow for more freedom on diff name-ign relation (and “map series” stuff as mentioned before)

also as a follow up to this paragraph UC said (that i can’t directly quote for some reason)
we should just remove the rule altogether instead, it was added at a time when star rating was actually useless, but now our sr's are usually pretty telling of what difficulty a map is so there's no real reason to keep it other than "some people didn't like username-only diffnames", which isn't a very good reason
i’d just like to bring up this set: https://osu.ppy.sh/beatmapsets/87547#osu/253980

there’s no way of knowing which is the harder diff even with the current sr because of the mapper’s different mapping styles. it’s not weak reasoning at all.

if we’re going by checking sr we might aswell take Hollow Wings’ Kikoku Doukoku Jigokuraku and pitch it against whatever the most popular 5* farm map is right now while naming their respective diffs the mapper’s name (i’m aware it’s a kinda extreme example but that’s my point) it’ll be clear that it won’t make any sense to not keep this as at least a guideline

(last edit cuz 11 is an ugly number and wtf thats a lot of edits)
posted

pishifat wrote:

if i named a difficulty "pishi" or "pishifat", it wouldn't be valid for ranking. if people are talking about stuff like pishInsane not being enforced as unrankable, i can understand editing the rule accordingly, but removing it entirely makes the first case okay, which shouldn't happen

im not sure how melancholy/posthomus/frozen etc are related to the rule either. they're not related to a username, they're just used by certain users frequently
possibly revising the rule to be able to be related, but not use direct parts of one's name? But there exists difficulties such as Raidcore (Raiden's map series thing) that may still be an exception to that rule. The rule covers such a broad range which is why I think it would be better as a guideline.

Idealism wrote:

i’d just like to bring up this set: https://osu.ppy.sh/beatmapsets/87547#osu/253980


bruh this map is from 2013 lol
posted

Nifty wrote:

Idealism wrote:

i’d just like to bring up this set: https://osu.ppy.sh/beatmapsets/87547#osu/253980


bruh this map is from 2013 lol
yea thats exactly why i brought it up lo it does exactly the opposite of what uc said and exactly what stefan said
posted
So, to be clear, topdiffs don't need to have any relation to the song or music or theme whatsoever now, since that's what is being allowed?
posted
Been talking about this stuff internally so I guess here we go. Here's some stuff I've gathered from our discussions and I guess what we can look to do moving forward:

- Moving it to guidelines is a problem because unless we know when to enforce it, it might as well not be there at all
- Leaving the decision to the NAT will lead to inconsistent decisions, which as we've seen lately, have not gone over well with the community


The best way to go about it is to draw a clear line and not take the rule so literally I guess. Something like this might work?

Ranking Criteria wrote:

Difficulty names must not solely consist of usernames. Words that happen to be usernames are acceptable as difficulty names as long as they relate to the song.
and then moving the other one to

Ranking Criteria wrote:

A beatmapset host cannot indicate possession in a difficulty's name. Conflicts caused by beatmapping multiple songs with the same metadata and collaborative difficulties are the only exceptions. Guest difficulties, however, may indicate possession with its creators' username or nickname. (e.g. Guest Creator's Insane).
edit: both would be rules btw
posted

Ascendance wrote:

The best way to go about it is to draw a clear line and not take the rule so literally I guess. Something like this might work?

Ranking Criteria wrote:

Difficulty names must not solely consist of usernames. Words that happen to be usernames are acceptable as difficulty names as long as they relate to the song.
and then moving the other one to

Ranking Criteria wrote:

A beatmapset host cannot indicate possession in a difficulty's name. Conflicts caused by beatmapping multiple songs with the same metadata and collaborative difficulties are the only exceptions. Guest difficulties, however, may indicate possession with its creators' username or nickname. (e.g. Guest Creator's Insane).
edit: both would be rules btw
I support this. I can't think of examples which could cause further issues under these changes
posted
feel like you could also include something about custom names that are not explicitly usernames but are also completely unrelated to the song since it is more or less the same thing.
posted
Reworded something with Naxess:

Ranking Criteria wrote:

Difficulty names must not solely consist of usernames. Words that happen to be usernames are acceptable as difficulty names as long as they relate to the song.

Ranking Criteria wrote:

A beatmapset host cannot indicate possession in the name of a difficulty (i.e. User's Insane). Conflicts caused by beatmapping multiple songs with the same metadata and collaborative difficulties are the only exceptions. Guest difficulties, however, may indicate possession with its creators' username or nickname.
edit: we're also going to separate the bottom part of this rule (starting with "Custom...") to be bolded and more clear

That should fix all of our problems in one go
posted
I support this.

A mapset by Sotarks that has already been ranked would technically break the old rule "A difficulty's name must be unrelated to a username.", with the top diff called "Les vaches de Sotarks". All the diffnames in that mapset, however, are named thematically, and so I think that's completely fine. If we rephrase this rule to "Difficulty names must not solely consist of usernames.", it would prevent a lot of confusion with thematically named difficulties as well.

Also I don't think this will go against the rule "A beatmapset host cannot indicate possession in the name of a difficulty." either, as it's not the conventional kind of possession e.g. "User's Insane" that we know. As far as I know, the point is not to eliminate "possession" completely, but simply the use of the pattern "<x>'s <diff>" from the mapset host themselves. For clarification purposes, perhaps a clause could be added such as "A beatmapset host cannot indicate possession in the name of a difficulty, except for thematic naming purposes that make sense in the given context.".
posted
what about old cases of this, such as iNiS980/iNiS201 (indicating EBA/Ouendan style) or something like KIRBY Mix/DaRRi MIx
this wouldn't really cause a lot of confusion since most people are probably playing the diffs because they are made by old mappers in that case
posted

Nitroz wrote:

what about old cases of this, such as iNiS980/iNiS201 (indicating EBA/Ouendan style) or something like KIRBY Mix/DaRRi MIx
this wouldn't really cause a lot of confusion since most people are probably playing the diffs because they are made by old mappers in that case
I believe you could easily justify those cases (if they'd ever happen ((X) Doubt)) under

J1NX1337 wrote:

except for thematic naming purposes that make sense in the given context.
Since these cases have always been such a great legacy in osu!'s history (basically everyone knows what's going on), I think the context is given for "thematic naming purposes" for them.
posted
Please sign in to reply.