1) Why are we removing the marathon definition from the glossary? After the changes I feel like people will still refer to single diff spreads as marathons so it only seems practical.
2)
I still see a lot of people get discouraged over making spreads for songs that are around 2:30. A song bpm / rhythm complexity has a lot to do with how long someone might take to create a difficulty. This also hurts if there's no particularly "slow section" or break part of a map. So this can still be discouraging for those types of songs, i don't feel like it's entirely out of laziness at that point. I would change it like so:
This feels like it would make a little more sense too because the drain requirements for each type of spread would be established in a more linear fashion (3:00, 4:00, 5:00) similar to the difficulty increases in spreads (normal, hard, insane). But that probably doesn't matter much xd
3)
These are pretty repetitive, they can be combined into one
Hybrid spreads with osu! difficulties are specified afterward so that should cover everything too
4)
Definitely disagree here. There are many ways 2 songs together can offer a compelling experience.
Okay so to change this I would basically move this over to a guideline and modify it to encompass combining 2 songs out of laziness:
5) One thing that I think should definitely be addressed is reasoning for songs compilations. As in: you shouldn't be able to take any random songs by any random composers and throw it into a 5:00 minute compilation just because I don't feel like making a spread. I think this would be the most important thing to address if anything:
Don't know if that would be the best way to word it though.
2)
If the drain time of a song is...
… lower than 3:30, the lowest difficulty cannot be harder than a Normal. For non-osu! game modes in hybrid mapsets that feature osu! difficulties, the lowest difficulty cannot be harder than a Hard.
… lower than 4:30, the lowest difficulty cannot be harder than a Hard.
I still see a lot of people get discouraged over making spreads for songs that are around 2:30. A song bpm / rhythm complexity has a lot to do with how long someone might take to create a difficulty. This also hurts if there's no particularly "slow section" or break part of a map. So this can still be discouraging for those types of songs, i don't feel like it's entirely out of laziness at that point. I would change it like so:
If the drain time of a song is...
… lower than 3:00, the lowest difficulty cannot be harder than a Normal.
… lower than 4:00, the lowest difficulty cannot be harder than a Hard.
This feels like it would make a little more sense too because the drain requirements for each type of spread would be established in a more linear fashion (3:00, 4:00, 5:00) similar to the difficulty increases in spreads (normal, hard, insane). But that probably doesn't matter much xd
3)
- Single-mode mapsets must form a reasonable spread. This spread must comply with its respective mode's difficulty-specific Ranking Criteria.
- Hybrid mapsets without osu! difficulties must form a reasonable spread for each mode. This spread must comply with its respective mode's difficulty-specific Ranking Criteria.
These are pretty repetitive, they can be combined into one
- Single-mode and Hybrid mapsets
without osu! difficultiesmust form a reasonable spread for each mode. This spread must comply with its respective mode's difficulty-specific Ranking Criteria.
Hybrid spreads with osu! difficulties are specified afterward so that should cover everything too
4)
Song compilations must incorporate 3 or more songs. Using only 2 songs in a compilation is not a sufficient number of tracks to offer a compelling experience for players when compiled together, and should be broken up into separate mapsets.
Definitely disagree here. There are many ways 2 songs together can offer a compelling experience.
- There are a lot of cases where 2 songs are cohesive / go alongside eachother, which are intentionally done by the composer. Example of a ranked set that does this: https://osu.ppy.sh/s/654053 According to the mapper, both songs are usually performed together, and the theme of both songs align in a somewhat chronological way.
- Another different example, https://osu.ppy.sh/b/315867 The songs in the actual album for this one are sold as "The Island, Part 1 (Dawn)" and "The Island, Part 2 (Dusk)." So under this rule, wouldn't this be illegal? Even though part 2 is literally intended to be a sequel to part 1, plus they are extremely similar in the first place.
- One last point, while its might be uncommon for only 2 songs to be contained on an album together, 2 song eps are a thing. Since they're intended to be sold together by the artist, why would it be unfitting to make them into a compilation, if they encompass their own album? exmaple
Okay so to change this I would basically move this over to a guideline and modify it to encompass combining 2 songs out of laziness:
Guidelines
Song compilationsmustshould incorporate 3 or more songs. Using only 2 songs in a compilation is usually unfitting, unless the music within the compilation is cohesive together.
5) One thing that I think should definitely be addressed is reasoning for songs compilations. As in: you shouldn't be able to take any random songs by any random composers and throw it into a 5:00 minute compilation just because I don't feel like making a spread. I think this would be the most important thing to address if anything:
Rules
Song choice within song compilations must be justified in some manner. This is to ensure that song choice within compilations are not by random and that the songs with in the compilation fit in with eachother.
Don't know if that would be the best way to word it though.
