[New][GdeLine] Slider tick must be visible for speed changes

posted
Total Posts
39
show more
pw384

Kytoxid wrote:

This discussion seems to have died rather suddenly.

How about a simpler wording like this?

Slider speed changes should have corresponding cues. These cues may include changes in the music, changes in note density, or visible slider ticks.
Good idea, and I think that combo colors are also included
those
Not necessarily. New combos mark the start of a new phrase. If you have to use a new combo to show velocity change, you're doing something wrong.
Kodora
Just quoting my old post:

Kodora wrote:

You can never identify speed of next slider just by seeing new combo on it
Topic Starter
Garven
A "change in the music" isn't a cue you can read until you're already on it and is overly broad anyway. The other two I agree with.
D33d

Ekaru wrote:

Kytoxid wrote:

This discussion seems to have died rather suddenly.

How about a simpler wording like this?

Slider speed changes should have corresponding cues. These cues may include changes in the music, changes in note density, or visible slider ticks.
Support, though I wish we could just say "Don't be retarded" and be done with it D:
Just remember that this is the osu! community. :(

I second Garven's statement about what a "change in the music" actually is. There should be something visual to indicate the change. If you're not sure that the visual cues are obvious enough and that the speed change can't be followed on the fly, then don't use it. Yes, it's that simple and yes, you mappers should discard a feature if it isn't proven to work, instead of becoming attached to them in the name of artistic vision.

Beatmaps are made to translate the abstract (the music) into the literal (a game level which can be read and felt). This applies to every aspect of a beatmap's visuals.
Kytoxid
Slider speed changes should have corresponding prior cues. These cues may include changes in the music, changes in note density, or visible slider ticks, and should allow for the speed change to be expected before the slider begins.

I added a bit about expecting the speed change before you land on the slider. I'm reluctant to remove music changes completely because there are definitely times when the music will be able to provide prior warning. For example, many songs will have a build up prior to entering a chorus; as a player, I can definitely use that to anticipate an SV increase once I enter the chorus itself, even in the absence of visual cues.
Ekaru
As long as you guys are strict about stupid bullshit then I'm fine with this. ^_^
Topic Starter
Garven
Ekaru, that kind of language isn't helpful at all. Try to be at least a little constructive - explain what you mean. What is bad for you may be great for others. I just wanted to get some wording into the RC so that it will have a little bit a guidance towards fairness when it comes to sudden large slide speed changes, and this is the result. q:

@Kyto: That'll do then. As stated above, I wish there was mention of larger speed changes since that was the original intent of this thread.
RatedNC17
I'm not sure that a simple slider tick to show that the sliders speed has changed will be enough indicate that it has. I think a half a second (or a time equivalent to that of a approach circle) outline glow to a slider to indicate it has changed would be more noticeable
Kodora

RatedNC17 wrote:

I'm not sure that a simple slider tick to show that the sliders speed has changed will be enough indicate that it has. I think a half a second (or a time equivalent to that of a approach circle) outline glow to a slider to indicate it has changed would be more noticeable
That's why other part of proposed rule is exist:

Kytoxid wrote:

Slider speed changes should have corresponding prior cues. These cues may include changes in the music, changes in note density[u], or visible slider ticks, and should allow for the speed change to be expected before the slider begins.
Yes, new slider tick behaviour makes SV changes much harder to read since sliderticks appears just too fast to read them (it especially hurts on very fast maps). Most important thing - SV changes should have corresponding cues to allow people play them properly in first attempt without any problems, without looking in map in editor mode etc.

As i said before, support!
Kytoxid
Slider speed changes should have corresponding prior cues. These cues may include changes in the music, changes in note density, or visible slider ticks, and should allow for the speed change to be expected before the slider begins. Large, unexpected changes in slider velocity damage the readability and playing experience of the map.

Alright, I'm going to bubble the new guideline under this wording. I added a bit at the end to explain why we have this rule.

I'll leave it open to discussion for a few more days; if no one has issues with it, it'll be added to the RC.
Kytoxid
Added to ranking criteria.
Please sign in to reply.

New reply