For this rule, I would suggest a clarification that the white border not be covered up by the slider being packed in too tightly. This greatly improves readability, especially on mmsliders. Sliders crossing themselves should be fine as long as the crossing leaves a small island in the middle which shows some white border. (i.e., the bird has a beak.)

This should take other beats/sliders in consideration as well. Sometimes a cricle or a hitburst can make a slider confusing to follow.

This is a simple update that should have been included in the original posting of newrules (and doesn't really need any discussion), so I'll go ahead and amend it.


There's already a rule about avoiding hitbursts that cover up slider paths and such, so that should be enough.

Define "clear and visible".

Define "unreadable or ambiguous".

Define "confusing".

There's no way to force this as a rule if you leave all these grey areas.

My version suffers for the same issue but i had a disclaimer saying that it's impossible to decide such stuff beforehand and it will have to be judged case by case.

This really isn't needed, since the following rule already exists: "Slider anchors/nodes must not be used to manipulate slider speeds".


This just seems too long-winded and irrelevant. Some rules already require judging on a case-by-case basis (since we can't possibly define everything), and thus it seems redundant to say so in the rule itself. The current amended rule explains (as best as possible) what is and isn't allowed, so just leaving it as "sliders must have a clear path but will need to be judged on a case-by-case basis" doesn't seem appropriate.

I'll gladly re-amend the rule if anyone is able to clarify it better, but I don't think that it's possible (without adding extra unnecessary sentences and/or links to picture examples).

Every rule has subjective aspects and is to be taken case-by-case. Stating it for every rule you find an exception for is redundant and silly.
Also, that slider overlaps be non-local isn't especially ambiguous.

Also this kind of nonsense needs to be forbidden:

Why that is readable in every sense come on man you asking for that not to be allowed is nonsense not to mention MMsliders kill readability by about 60% fwiw peppy sliders allow you to make patters such as those with no problem of reading but for the sliders you are using you need to read the bright center but I can see how that would be hard to read without peppy sliders because it looks as it can go both ways. Then again I used peppy sliders so this patter would be a no brainer for me as do most users just because of the fact mmsliders haven't really been set a hard default yet.

Sure, those might be a bit more obvious with peppysliders, but smaller scaled versions of those sliders can cause the same problems and not give enough reaction time to properly read. Besides, it's a simple fix for the mapper to spread out the slider (so that the borders are visible) while still retaining its basic shape. :/

I think slider renders should never be a reason to decide if a slider is readable or not, that'd be unfair since some skins already use mmsliders and opengl has a similar kind of sliders as well

The upcoming textured sliders have the same behaviour and I foresee heavy usage of them once they're available.

This rule has already a heart icon why is this even still being discussed? ._.

Edit: Oh i see

A heart only means that the rule/guideline has been amended. It can still be discussed/changed and won't be finalized until after community input.

Is that what I think it is? That's some epic trolling.

If you need to judge case by case how can something be a rule?
A rule is supposed to be 100% objectively correct everytime, not "case by case" because that means adding exceptions and thus it can't be considered an absolute rule anymore.

Tell that to the court system. Someone's an idealist.