Color Code:
- DISAGREE
- agree
- Everything else.
pishifat wrote:
Spread
Rules
All rules are exactly that: RULES. They are NOT guidelines and may NOT be broken under ANY circumstance. Let's see... let's see...First sentence is obvious.
- 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. This should say at most a Normal instead because the phrase "at least" can imply that a Hard difficulty can be used as the lowest difficulty, then people would get an idea that Insanes can be the lowest, and so forth.
- 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. Not really into the "two difficulties per mode" thing, but can't think of a better solution, really.
- If a hybrid mapset includes osu!standard difficulties...
Same wording issue as 1st rule and rule above.
- 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. Seems Good.
- 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. It's alright, but it could be worded better; by converted difficulties, if you're meaning "osu!standard CtB" and not something like "Mapset as is, difficulties between all game modes must not have large gaps in difficulty", then I can see the gap needing to be filled, but if the latter, then just leave the difficulties as are regardless of jumps like 2* standard 4* Taiko
- 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 issue as 1st rule.- 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. That's obvious.
- Marathons must have a minimum drain time of 5 minutes. This excludes especially long mapsets from requiring a spread of difficulties.
This could be lowered, IMO. There are a great variety of songs with a length between 4-5 minutes that show so much potential without a need for a full spread.- Songs/maps cannot be modified to reach the minimum drain time. Abusing the 5 minute limitation removes its intended purpose. Types of abuse include:
I'm polarized by the "no song modification" thing in general; I like it because it helps to combat such a petty way to cheat the ranking system, but I think that song modifications provide experimentation and variety all around. Personally, I'd lean more toward this rule if the minimum approval drain time were around 4 minutes instead, but if it is to stay at 5 minutes, then I'd be more against this rule.
- Lowering a song’s BPM
- Looping portions of a song
- Adding sounds before/after a song begins/ends The first three are debatable because maybe the mapper fiddled with the song a certain way, liked it that way, and wanted to map that edited version.
- Extending spinners/sliders over inaudible sounds I agree; what's the point?
- Manually removing breaks Totally should stay unrankable, hands down.
- 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. Definitely not. This would essentially split many difficulties of a mapset (ex: 20 diffs into 3-4 different mapsets), which is exhausting to the GD mappers and maphost as they may split their work among each maps, leading to checking different threads for the mods instead of one, and for BNs as they'll need to icon check more maps instead of one. That last sentence is iffy, because it essentially means "Holy SH*T, I can make an 8 star difficulty right after my 5.5 star difficulty because of this!"; no don't hit those people with the "common sense" hammer, because it'll lead to a big mess in the threads, which could lead to more work from the moderation team.
- 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. Unnecessary rule as difficulty naming is up to interpretation of the mapper.
- 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). No problems here.
- 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. Kind of obvious, considering difficulties without a name are automatically assumed the host's.
- 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.
Second one needs some clean-up. "for via storyboarding." Wonder what that means? The mapper might not want a storyboard every time they host a collab, so maybe they should just put respective total drain times worked on in the "space provided".
Guidelines
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.Don't know too much about this, so you tell me!
- Avoid incomprehensible username combinations to indicate possession of a collaborative guest difficulty. If it’s unclear whose usernames are combined, simplification is recommended. True.
- 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. Once again,
up to interpretation of the mapper.- 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 think so, too.
- 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.
Well, that's all the feedback I can provide for you. Hoping for the best for the future of osu!mapping!
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! Also I'd like to reap my kudosu reward pls thx