not this difficulty limiting crap again
So this suggest that the previous star rating limit at 2 is removed to something more lenient as long as it fits a Normal-level density right ?pishifat wrote:
Single-mode mapsets must include a reasonable spread of at least two difficulties. The lowest difficulty must be at least a Normal which complies with their respective mode’s difficulty-specific ranking criteria.
I don't really see why this is a rule, the only benefit would be that there is less modding to do for the map.pishifat wrote:
- Mapsets cannot include more than 8 total difficulties of a single game-mode. The highest difficulty of a game-mode is not required to fit within a reasonable spread, so long as no levels of difficulty are skipped.
"levels of difficulty" refers to normal/hard/insane/expert or just normal/hard/insane? question is - are normal->hard->insane->ultra spreads gonna be allowed since ultra is still an X iconpishifat wrote:
Mapsets cannot include more than 8 total difficulties of a single game-mode. The highest difficulty of a game-mode is not required to fit within a reasonable spread, so long as no levels of difficulty are skipped.
Nivrad00 wrote:
I agree with everyone about the 8-diff limit, especially in cases of mania sets with multiple keymodes. If you include two keymodes, the greatest amount of diffs per keymode is 4; and if you include four keymodes, the greatest amount of diffs per keymode is 2. Whether it's reasonable to have over 8 standard diffs or over 8 4k diffs can be debated, but I definitely think this rule should at least be edited to allow more diffs in the case of multiple keymodes.
Game-mode: osu!, osu!taiko, osu!catch, and each of osu!mania’s key counts are considered individual game-modes.???????
pishifat wrote:
Mapsets cannot include more than 8 total difficulties of a single game-mode. The highest difficulty of a game-mode is not required to fit within a reasonable spread, so long as no levels of difficulty are skipped. how will this make maps more accessible to people? I think it won't. Some spreads can't get really hard and there are lots of difficulty techniques to grow between few amount of difficulties. This cap makes spreads like these be much harder to accomplish properly AND I think nobody will care to try to accomplish them since highest diff is not required to fit within a spread.
A mapset host must have equal or more drain time mapped than any guest difficulty mappers. This is to provide credit where credit is due. Drain times for collaborative difficulties must be listed in the creator’s words for via storyboarding. what part of mapping is hitsounding? this should be defined if its considered or not and how much its considered to avoid confusion.
Avoid incomprehensible username combinations to indicate possession of a collaborative guest difficulty. If it’s unclear whose usernames are combined, simplification is recommended. this is really ambiguous
Usernames indicating possession of a guest difficulty should be consistent between multiple mapsets. Varying nicknames for one user makes interpreting who created a difficulty confusing. I know this is a guideline because of name changes, but in this event there are usually links in the description to the creators profile in case of ambiguity, and usually anyone who really cares checks there. Though does this mean if the gd is NOT indicated in the diff name it will be a problem also?
pishifat wrote:
hi hey I'm here to mod your draft to sort out clarifications as well as point out potential issuesCommon terms
Mapset
- Game-mode: osu!, osu!taiko, osu!catch, and each of osu!mania’s key counts are considered individual game-modes. and the entire osu!mania community goes "what" as this is the first time in 5 years they've ever been referred to as individual game modes.
Spread
Rules
All rules are exactly that: RULES. They are NOT guidelines and may NOT be broken under ANY circumstance.Guidelines
- Single-mode mapsets must include a reasonable spread of at least two difficulties. The lowest difficulty must be at least a Normal which complies with their respective mode’s difficulty-specific ranking criteria. the use of the term "at least a Normal" can be quite confusing for new modders as it doesn't indicate a direction. Saying "The lowest difficulty must be a normal or easier" would be better clarification. This holds true for the below points as well.
- Hybrid mapsets without osu!standard difficulties must include a reasonable spread of at least two difficulties per mode. The lowest difficulty must be at least a Normal which does not break any difficulty-specific guidelines. ^
- If a hybrid mapset includes osu!standard difficulties...
- A reasonable spread of at least two osu!standard difficulties must be included. The lowest difficulty must be at least a Normal which does not break any difficulty-specific guidelines. ^
- Converted difficulties must form a reasonable spread. For example, a mapset with Easy and Normal osu!standard difficulties and an Insane osu!catch difficulty is not permitted. One or more additional difficulties may need to be added to fill the gap. See this with rule D send out conflicting messages when first read. "Oh you can't have an Insane with an Easy/Normal oh but rule D says it can be Insane and lower." I understand that this is for normal/hard converted spreads but better clarification should be used.
- Any two osu!taiko or osu!mania difficulties must be arranged in a reasonable spread. The lowest difficulty must be at least a Hard. same wording thing as first point
- One osu!catch difficulty may be included. It must be at least an Insane difficulty. extending from rule B, this should most likely read something along the lines of "One osu!catch difficulty may be included. It must be a hard or easier unless the converted osu!standard set is a normal &
hard spread (and any other acceptable combinations), to which an insane diff would be allowed." This might sound somewhat confusing in itself, but it's at least less ambiguous and not conflicting as the current set of rules.- Mapsets must have a minimum drain time of 30 seconds. This ensures each ranked map has a practical play-time.
- Marathons must have a minimum drain time of 5 minutes. This excludes especially long mapsets from requiring a spread of difficulties. does the new website have a fix for maps that end with a slider/spinner? that would be really nice
- Songs/maps cannot be modified to reach the minimum drain time. Abusing the 5 minute limitation removes its intended purpose. Types of abuse include:
- Lowering a song’s BPM
- Looping portions of a song
- Adding sounds before/after a song begins/ends so I get that these 3 here are meant to be there to preserve audio accuracy to the actual song at hand, but I feel like if they're used in the correct way (sound being slowed down enough to change how the song could be interpreted for instance,
having perfect loops of a song to the point where it just sounds like an Extended Mix for lack of a better term, and well we have Pavor Nocturnus [2015] for the last point) it could potentially work but then that runs the risk of always being a case by case basis which is something you want to avoid as a ranking criteria council, so I'll leave this one up to further discussion- Extending spinners/sliders over inaudible sounds this is fine
- Manually removing breaks this is already against the RC afaik (aka editing the .osu file)
- Mapsets cannot include more than 8 total difficulties of a single game-mode. The highest difficulty of a game-mode is not required to fit within a reasonable spread, so long as no levels of difficulty are skipped. see no I can't get behind this. I understand that mapsets containing 9 or more diffs are rare, but they're common enough that they already have a place in the game, and whilst I've seen people argue the point that "if they're so similar/different they should just be in separate spreads" but most people won't do that, definitely considering that most people that have spreads that high are mostly guest difficulties, and so the mappers of the guest difficulties in a very high number of scenarios will just not bother to rank another spread of that map as it's not in their interest, so what you're doing is taking a 12 diff spread, and instead of splitting it into 2 6 spread mapsets like you want, you'll just cut 4 diffs from the set, that's reality. Also in spreads that have a high SR top diff, an 8 diff count is very limiting in spread terms. For example, stuff like Doppelganger barely fits into the 8 diff criteria and its spread isn't exactly overdoing, in fact, any less and it would be questionably unrankable due to gaps in the SR. Please, for the love of god, reconsider this before you make a terrible mistake and injure potential massive projects, or even just decent sets throughout, I can't see any upside to this rule.
- Excluding a mapset’s hardest difficulty, a difficulty’s name must accurately indicate its level of difficulty. Conventional difficulty names vary between modes, but any set of clearly progressive difficulty names can be alternatively used. Additionally, a mapset’s hardest difficulty should not use a name misrepresentative of its difficulty. woo case by case basis on hardest difficulty naming woo time to argue over why a diffname is relevant woo (in reality no one is going to follow this rule after like 2 weeks)
- A difficulty’s name must be unrelated to a username. Guest difficulties, however, may indicate possession with its mappers’ username or nickname. (e.g. Guest Mapper’s Insane).
- Additionally, a mapset host cannot indicate possession in a difficulty’s name. (e.g. Mapset Host’s Insane). Metadata conflicts caused by mapping a song multiple times are an exception.
- A mapset host must have equal or more drain time mapped than any guest difficulty mappers. This is to provide credit where credit is due. Drain times for collaborative difficulties must be listed in the creator’s words for via storyboarding. <--- this wording at the end makes no sense. "for via storyboarding"? does that mean that the people's names have to be included in a storyboard? have to be included in the description for potential storyboarding?
what if the mapset owner doesn't plan to have a storyboard is it still necessary then? I can't contribute more to this until it's rewritten to make more sense.
Guidelines may be violated under exceptional circumstances. These exceptional circumstances must be warranted by an exhaustive explanation as of why the guideline has been violated and why not violating it will interfere with the overall quality of the creation.
- Avoid incomprehensible username combinations to indicate possession of a collaborative guest difficulty. If it’s unclear whose usernames are combined, simplification is recommended.
- Avoid difficulty names with descriptive elements not clearly related to a guest difficulty mapper or a level of difficulty. (e.g. Mapper’s Tragic Love Extra). A mapset’s hardest difficulty may use free naming, but clear and appropriate relation to its song is recommended. Debatable being in the guidelines section considering you put a strict use of hardest diff naming in the rules
- Usernames indicating possession of a guest difficulty should be consistent between multiple mapsets. Varying nicknames for one user makes interpreting who created a difficulty confusing. I guess if a user changes name then a drastic name change is fine, might want to add that as an exception.
- Avoid unicode characters in a difficulty’s name. These can cause errors with the beatmap submission system and problems for certain users when appearing in chat.
Once again, this draft is not the final result, as we need the feedback of the community first before getting it officially bumped into the wiki! It will be up to discussion for two weeks and close on the 18th of June! feedback given kds plz xd
Single-mode mapsets must include a reasonable spread of at least two difficulties. The lowest difficulty must be at least a Normal which complies with their respective mode’s difficulty-specific ranking criteria.Shouldn't be the same?
Hybrid mapsets without osu!standard difficulties must include a reasonable spread of at least two difficulties per mode. The lowest difficulty must be at least a Normal which does not break any difficulty-specific guidelines.
uhm is that a typo on "or via storyboarding"? Because the "for" can cause quite a bit of a confusion since many people (the ones that I've asked, at least) will think that collaborations now requires storyboards that states each mapper's part lolpishifat wrote:
A mapset host must have equal or more drain time mapped than any guest difficulty mappers. This is to provide credit where credit is due. Drain times for collaborative difficulties must be listed in the creator’s words for via storyboarding.
Like what celerih said earlier, many songs can be interpreted in a lot of different ways due to the sheer number of different mapping styles that you can see varying from mapper to mapper. While I do see some sense to why this has been proposed (avoiding unnecessarily large mapsets and all that), I strongly think that this rule should be adjusted in a more flexible way and that it should only be applied in a case-by-case basis.pishifat wrote:
Mapsets cannot include more than 8 total difficulties of a single game-mode. The highest difficulty of a game-mode is not required to fit within a reasonable spread, so long as no levels of difficulty are skipped.
If a mapper is going to go out of their way to have the mp3 edited to reach marathon length, this rule won't get them to make a full spread. This rule is choosing between "have a 5 minute map for a song that isn't 5 minutes" and "have no map". As long as the actual play experience of the map is still pleasant, it is better to have the map than not have the map. There is never anything bad about having more maps.update wrote:
Songs/maps cannot be modified to reach the minimum drain time. Abusing the 5 minute limitation removes its intended purpose.
This idea has already been very vocally rejected by the community. Players love big sets because it gives lots of different difficulties in one easy-to-download bundle instead of having to dig through a bunch of different sets. Mappers love big sets because they create lots of community interaction and they are fun to build up with friends. They are harder to find bn's for but that's the mappers' risk to take.update wrote:
Mapsets cannot include more than 8 total difficulties of a single game-mode. The highest difficulty of a game-mode is not required to fit within a reasonable spread, so long as no levels of difficulty are skipped.
change "for" to "or"update wrote:
A mapset host must have equal or more drain time mapped than any guest difficulty mappers. This is to provide credit where credit is due. Drain times for collaborative difficulties must be listed in the creator’s words for via storyboarding.
If the mapper doesn't care whether they're credited or not then that's entirely on them. The real username will be in tags and description anyway for users to find them so it doesn't matter what nickname they use in the diff name. This is just a "No Fun Allowed" rule that doesn't affect map quality in any way.update wrote:
Usernames indicating possession of a guest difficulty should be consistent between multiple mapsets. Varying nicknames for one user makes interpreting who created a difficulty confusing.
pishifat wrote:
hiSpread
Rules
All rules are exactly that: RULES. They are NOT guidelines and may NOT be broken under ANY circumstance.Guidelines
- Single-mode mapsets must include a reasonable spread of at least two difficulties. The lowest difficulty must be at least a Normal which complies with their respective mode’s difficulty-specific ranking criteria. The wording of "at least" is really confusing. I'm guessing you are saying that it is Normal or lower, but "at least" suggests "more", which you could interpret as being harder than Normal (rip Easy difficulties, because they are apparently unrankable now lol). I propose an alternative wording, "must be no higher than X difficulty"/"must not be higher than X diff". PLEASE FIX FOR ALL INSTANCES!
- Hybrid mapsets without osu!standard difficulties must include a reasonable spread of at least two difficulties per mode. The lowest difficulty Does this apply to both difficulties, or a singular difficulty? must be at least a Normal which does not break any difficulty-specific guidelines.
- If a hybrid mapset includes osu!standard difficulties...
- A reasonable spread of at least two osu!standard difficulties must be included. The lowest difficulty must be at least a Normal which does not break any difficulty-specific guidelines.
- Converted difficulties must form a reasonable spread. For example, a mapset with Easy and Normal osu!standard difficulties and an Insane osu!catch difficulty is not permitted. One or more additional difficulties may need to be added to fill the gap.
- Any two osu!taiko or osu!mania difficulties must be arranged in a reasonable spread. The lowest difficulty must be at least a Hard.
- One osu!catch difficulty may be included. It must be at least an Insane difficulty.
- Mapsets must have a minimum drain time of 30 seconds. This ensures each ranked map has a practical play-time.
- Marathons must have a minimum drain time of 5 minutes. This excludes especially long mapsets from requiring a spread of difficulties.
- Songs/maps cannot be modified to reach the minimum drain time. Abusing the 5 minute limitation removes its intended purpose. Types of abuse include:
- Lowering a song’s BPM
- Looping portions of a song
- Adding sounds before/after a song begins/ends
- Extending spinners/sliders over inaudible sounds
- Manually removing breaks
- Mapsets cannot include more than 8 total difficulties of a single game-mode. The highest difficulty of a game-mode is not required to fit within a reasonable spread, so long as no levels of difficulty are skipped. OKOKOK HOLD ON. If the highest difficulty is not bound by reasonable spread, so I can theoretically map an Easy bundled with an Insane? This conflicts with an earlier rule which says that both difficulties must adhere to a "reasonable spread". So which rule here takes precedence?
- Excluding a mapset’s hardest difficulty, a difficulty’s name must accurately indicate its level of difficulty. Conventional difficulty names vary between modes, but any set of clearly progressive difficulty names can be alternatively used. Additionally, a mapset’s hardest difficulty should not use a name misrepresentative of its difficulty.
- A difficulty’s name must be unrelated to a username. Guest difficulties, however, may indicate possession with its mappers’ username or nickname. (e.g. Guest Mapper’s Insane).
- Additionally, a mapset host cannot indicate possession in a difficulty’s name. (e.g. Mapset Host’s Insane). Metadata conflicts caused by mapping a song multiple times are an exception.
- A mapset host must have equal or more drain time mapped than any guest difficulty mappers. This is to provide credit where credit is due. Drain times for collaborative difficulties must be listed in the creator’s words for via storyboarding.
Guidelines may be violated under exceptional circumstances. These exceptional circumstances must be warranted by an exhaustive explanation as of why the guideline has been violated and why not violating it will interfere with the overall quality of the creation.
- Avoid incomprehensible username combinations to indicate possession of a collaborative guest difficulty. If it’s unclear whose usernames are combined, simplification is recommended.
- Avoid difficulty names with descriptive elements not clearly related to a guest difficulty mapper or a level of difficulty. (e.g. Mapper’s Tragic Love Extra). A mapset’s hardest difficulty may use free naming, but clear and appropriate relation to its song is recommended.
- Usernames indicating possession of a guest difficulty should be consistent between multiple mapsets. Varying nicknames for one user makes interpreting who created a difficulty confusing.
- Avoid unicode characters in a difficulty’s name. These can cause errors with the beatmap submission system and problems for certain users when appearing in chat.
Once again, this draft is not the final result, as we need the feedback of the community first before getting it officially bumped into the wiki! It will be up to discussion for two weeks and close on the 18th of June!
Agreed, better as it is.xxdeathx wrote:
I'm strongly opposed to the 8 difficulty limit per game mode rule and would not like to see it put into practice at all, but I have to hear your reasoning behind it. What good will it do that outweighs the current state?
If a hybrid mapset includes osu!standard difficulties...so this means that overdose and deluge can be included without rain? that's how i'm interpreting it + no longer allowed to gd salads/platter/cup
One osu!catch difficulty may be included. It must be at least an Insane difficulty.
It is also an attempt to encourage beatmap sets to be more "cohesive" and possessed of design and concept from top to bottomWhy is doing this vs. not doing this an indication of higher quality in a mapset? People don't play every difficulty of the spread from bottom to top, they play what skill level they are at. I don't look at a set, notice how the hard and insane have some cool concept that's similar between them and think "wow that's neat" because I'm not going to be playing both diffs; if I'm at the level where I play Insanes, I'm only going to really be playing the insane.
In my personal opinion, either way is bad, cutting and extending alike. Extending stuff by a few seconds just to adhere to personal laziness to avoid mapping a fullspread and making the set accessible to the entire playerbase (instead of just to a small minority that can even play most Approvals, which are mostly Extreme level) is contradicting some core philosophy we have been trying to defend for years (make stuff accessible and enjoyable for the majority, not just to only the top players). Like it or not, but those who play Extreme level maps are in the sheer minority. Encouraging to circumvent the necessity to produce content for the majority of our playerbase is unwanted, because with that new people will eventually not find content they like and they can play.StarrStyx wrote:
Also, regarding the mp3 extension rule, I don't really see a reason to deny extensions if the mp3 is properly extended without any badly trimmed sections; plus I'd rather see an extension of a song rather than a crude 1-2 min cut. Imo those are even worse than extending an mp3 just by a few seconds. (Also the song compilations stuff that others have pointed out already so ya)