forum

Guideline: A maximum of three slider velocities should be...

posted
Total Posts
58
Topic Starter
pieguyn
A maximum of three slider velocities should be used (including 1x). For example, you could have a single map using 0.6x, 0.8x, and 1x; or 0.75x, 1x, and 1.5x; etc. If more than three slider velocities are used, then they should make sense and be intuitive. If slider velocity changes are able to be merged (e.g. close values like 0.8x and 0.7x) while still flowing/working correctly, then they should be.
The last sentence in this guideline doesn't make any sense... Why should they have to be merged? There's no problem with having them as separate values as long as they fit.

Suggestion: remove the last sentence :?
Shiirn
This is already functionally a guideline rather than a rule. What the last line is attempting to state is that if you have 0.75 and 0.8, say, in two entirely separate sections of the map, to switch one to the other since it's needlessly strange to have a 0.05x difference in slider velocity.
Larto
I'm still completely against even having this guideline. Slider velocities can be used terribly even if you only have three different velocities. The amount of slider velocities has nothing in common with how well used they are. You could make a similar guideline about the volume settings per section, and it would make similarily litle sense.

Edit: And how much does it actually matter if you have 0.7x and 0.8x or if you have just 0.75x? Why is this important?
Raging Bull
.5x 1x 2x within few seconds of each other orz. Perhaps it's a good idea to just remove it or say something like use it intuitively. No one would like to see a slow slider then a fast and then a slow again next to each other. :s
Mismagius
If there is something wrong with different sliderspeeds being abused, please make "Disable Distance Snap" unrankable too because too many people use jumps and abuse it.
Shiirn

Blue Dragon wrote:

If there is something wrong with different sliderspeeds being abused, please make "Disable Distance Snap" unrankable too because too many people use jumps and abuse it.
That's a fucking retarded comparison, namely because the rule isn't about abusing silderspeeds at all, it's about being consistent with your speeds and using one speed where you have two similar (read: functionally identical) ones. iloveyoubd
Mismagius

Shiirn wrote:

the rule isn't about abusing silderspeeds at all
Then why create the rule?

As far as I know there are way more MATs/BATs complaining about sliderspeeds being abused than complaining about 0.77x / 0.8x different sliderspeeds. This rule is a minor part of the "be intuitive" stuff, which is completely unnecessary and common sense would take over it.

If there is no common sense for the mappers in this community, there are the BATs. And they should keep these kind of maps out if they are completely unreadable, and before that, not fun to play.

Same thing that applies to most rules: If it's fun to play, why not?
Soaprman
Focusing on how many speeds are used rather than how they are used does nothing to make a map better. This guideline should be deleted entirely.

Also, seconding Blue Dragon's entire post.
Ekaru

Soaprman wrote:

Focusing on how many speeds are used rather than how they are used does nothing to make a map better. This guideline should be deleted entirely.

Also, seconding Blue Dragon's entire post.
This.

A better guideline would be the following:

Slider velocity changes should fit the music. If the music feels significantly slower or faster, but the BPM doesn't actually change, then it's recommended to use a slider velocity change to reflect this change in the music. It is also not recommended to use slider speed changes as "traps", or just because you feel like it; this is not fun, and will secretly make many people want to kill you in your sleep.
Okay, that will probably have to be rewritten to look more professional, especially that last sentence.
Shiirn
Slider velocity changes should fit the music. If the music feels significantly slower or faster, but the BPM doesn't actually change, then it's recommended to use a slider velocity change to reflect this change in the music. You should avoid over-representing the change in the feel of the music because of using multipliers that are too high or too low (x2 or x0.5). As well, a maximum of three slider velocities should be used in most cases, as situations in which you use more than that would most likely involve actual BPM changes.

Feel free to make it more concise, but in all reality that's probably as close as we're going to get to something that is functionally covering most arguments.
Ekaru

Shiirn wrote:

Slider velocity changes should fit the music. If the music feels significantly slower or faster, but the BPM doesn't actually change, then it's recommended to use a slider velocity change to reflect this change in the music. You should avoid over-representing the change in the feel of the music because of using multipliers that are too high or too low (x2 or x0.5). As well, a maximum of three slider velocities should be used in most cases, as situations in which you use more than that would most likely involve actual BPM changes.

Feel free to make it more concise, but in all reality that's probably as close as we're going to get to something that is functionally covering most arguments.
Yeah, I agree with that.

About the only real situations where more than 3 make sense shouldn't even be attempted by newer mappers anyways, and since it's a guideline, experienced mappers can still use as many changes as they wish. This also gives newbie mappers good advice at the same time that can add more variety to their maps without destroying them by accident. This is pretty close to perfect IMO.
Mismagius

Ekaru wrote:

About the only real situations where more than 3 make sense shouldn't even be attempted by newer mappers anyways, and since it's a guideline, experienced mappers can still use as many changes as they wish. This also gives newbie mappers good advice at the same time that can add more variety to their maps without destroying them by accident. This is pretty close to perfect IMO.
Sad how new mappers will abuse it and say "this map is ranked and it used it so why can't i"
Rena-chan

Shiirn wrote:

This is already functionally a guideline rather than a rule. What the last line is attempting to state is that if you have 0.75 and 0.8, say, in two entirely separate sections of the map, to switch one to the other since it's needlessly strange to have a 0.05x difference in slider velocity.
Actually, this kind of thing does have a use, though it's mainly in a "fixing sliderends" way. A 0.05x difference won't make a noticeable speedup/slowdown, but it can make a slider end exactly on an osu!pixel instead of being just slightly off, thus allowing a note to be stacked above/below the end of the slider instead of effectively screwing stacking up.

Example:


(2) is made with a 1,20x section instead of 1,25x to make the sliderend land exactly on (4). Without this, it would be slightly off and look ugly.
Mismagius

Rena-chan wrote:



(2) is made with a 1,20x section instead of 1,25x to make the sliderend land exactly on (4). Without this, it would be slightly off and look ugly.
I'm not against this kind of stuff, but wouldn't (4) get covered by (2)'s hitburst anyway?

EDIT: hurr it's a slider, nevermind
Shiirn
Additionally, can't you just re-make (2) so that it still uses 1.2? It's not difficult to make sliders perfect as far as osu!pixels go...
Rena-chan

Shiirn wrote:

Additionally, can't you just re-make (2) so that it still uses 1.2? It's not difficult to make sliders perfect as far as osu!pixels go...
Dooooooesn't really work, no. While it may not be difficult to do that, I would have to remake every slider in that section due to the change in velocity, which in turn would screw a lot of the curved sliders over (particularly longer sliders). Straight sliders aren't much of a problem, but if I can use a 0.05x difference to make a single slider look better, then why not ? It's a difference of around half an osu!pixel that won't make a noticeable slowdown either in osu! or Taiko, thus a purely cosmetic difference, which is the only use there is for this kind of difference in slider velocity.

As with everything, it can be used and abused needlessly, but this is a technique that can be used with reason.
RandomJibberish
Using speed changes for prettiness is just no. I'm sure you could have figured out another way around that pattern.

Speed changes should relate only to music intensity.
Shulin

Larto wrote:

I'm still completely against even having this guideline. Slider velocities can be used terribly even if you only have three different velocities. The amount of slider velocities has nothing in common with how well used they are. You could make a similar guideline about the volume settings per section, and it would make similarily litle sense.

Edit: And how much does it actually matter if you have 0.7x and 0.8x or if you have just 0.75x? Why is this important?
Agree with this, you could use 1 slider velocity terribly. I think the guideline would be better if it suggested all slider velocity changes should be intuitive rather than focusing on the number used.
Ekaru

Shulin wrote:

Agree with this, you could use 1 slider velocity terribly. I think the guideline would be better if it suggested all slider velocity changes should be intuitive rather than focusing on the number used.
That's why we came up with a possible replacement guideline:

Slider velocity changes should fit the music. If the music feels significantly slower or faster, but the BPM doesn't actually change, then it's recommended to use a slider velocity change to reflect this change in the music. You should avoid over-representing the change in the feel of the music because of using multipliers that are too high or too low (x2 or x0.5). As well, a maximum of three slider velocities should be used in most cases, as situations in which you use more than that would most likely involve actual BPM changes.
The last sentence is arguable, but its aim is overall what you said; to focus on *how* they're used, and not the actual amount used.
Rena-chan
Using speed changes for prettiness is just no. I'm sure you could have figured out another way around that pattern.

Speed changes should relate only to music intensity.
Such as placing a note on a half osu!pixel ? I think you're missing the fact that a player will not notice the speed change by this example.
show more
Please sign in to reply.

New reply