How osu! skins the slider ball, track and slider ticks
Sliders are where a lot of otherwise careful osu! skins fall apart. The hit circles look finished, the cursor is clean, and then the slider body is a default pink ribbon with a tiny white diamond sitting on it. This note is a practical checklist for skinning the ball, the generated track, the follow circle and the ticks — the parts players actually stare at for several beats at a time.
I use this list when reviewing skins for osuskins.org, an unofficial catalogue of osu! skins with gameplay previews. It is not affiliated with ppy.
The files that actually matter
In osu!stable the slider body is not a texture you drop in. The game generates the ribbon. What you ship are the moving parts and the colours that tint that ribbon:
| File | Role |
|---|---|
sliderb.png or sliderb0.png, sliderb1.png, … |
The slider ball. Numbered frames play as an animation. |
sliderfollowcircle.png (optional sliderfollowcircle-0 …) |
The ring that expands while you stay in the hold area. |
sliderscorepoint.png |
A slider tick. These are easy to forget and easy to hide by accident. |
reversearrow.png |
Drawn at a reverse; stacked reverses need this to stay readable. |
sliderstartcircle.png / sliderstartcircleoverlay.png
|
Optional start circle (skin version 2.2 and later). |
sliderendcircle.png / sliderendcircleoverlay.png
|
Optional end circle, same version rule. |
If a file is missing, osu! falls back to the default skin for that element only. A custom ball on a default track, or custom circles with default ticks, is the usual result — not a hard error.
@2x variants follow the same names (sliderb@2x.png, sliderscorepoint@2x.png). Mixing a 1x ball with @2x circles is a common reason the ball looks soft or slightly the wrong size on a high-DPI install.
Colours in skin.ini, not a body PNG
Under [Colours]:
-
SliderTrackOverride: r,g,bsets the fill of the generated body. If you omit it, you get the default track colour, which clashes with almost every custom combo palette. -
SliderBorder: r,g,bsets the outline. A border that is too close to the fill makes the path hard to read against a busy background video.
Under [General]:
-
AllowSliderBallTint: 1multiplies the ball by the current combo colour. This looks polished when every combo colour is bright, and disappears when a mapper-unrelated combo is navy or maroon. Leave it at0unless you have checked the ball against every combo colour the skin defines (and the default ones, if you define fewer than eight). -
SliderBallFlip: 1(the usual default) flips the ball sprite when the slider reverses. Set0only when the sprite is symmetrical, or the logo on the ball will briefly read backwards.
Version still matters. Below 2.2 the start/end circle files are ignored and the regular hit circle is used at both ends. A skin that only ships sliderstartcircle and sets Version: 2.0 will look unfinished.
Slider ticks are a readability problem, not decoration
Ticks (sliderscorepoint) are scored. If they blend into the track, players drop combo without seeing why.
What usually works:
- A small, high-contrast mark with a hard outline, not a soft glow the same colour as
SliderTrackOverride. - A tick that stays visible on both a light and a dark body. If you only tested on your own dark track, try the skin on a map with long sliders over a bright break-in video.
- No animation on the tick itself. A pulsing tick is easy to mistake for the ball or a follow-circle flicker.
If you are comparing existing skins rather than drawing your own, look at how the tick sits on the body in a gameplay preview before you download a large .osk. The install notes cover loading a skin so you can test long sliders in the editor or on a low-AR practice map.
Follow circle and ball size
The follow circle is the only honest signal that you are still inside the hold area. A faint, thin ring looks “clean” in a screenshot and fails in play, especially on fast sliders where the ball itself covers the path.
Check:
- The follow circle is clearly larger than the ball at its expanded size.
- Its alpha is high enough to read over the stage background at 80–90% background dim, not only on a black menu.
- Animation frames, if you use them, do not shrink the visible ring for a frame or two — that reads as a mis-aim.
The ball can be animated (sliderb0, sliderb1, …). Keep the hotspot in the centre of every frame. An off-centre frame makes the ball wobble along the track, which feels like input delay even though it is just artwork.
A short in-game test
After packing the .osk:
- Open a map with at least one long slider, one stacked reverse, and a visible tick rate (most 180+ BPM maps will do).
- Watch the body against the background video, not against the editor’s blank grid.
- Confirm ticks remain visible for the whole slider, including the end.
- If
AllowSliderBallTintis on, play until the combo colour cycles; the ball should never vanish. - Repeat once with
@2xforced off if you ship both resolutions, so a 1x fallback is not an afterthought.
If you would rather start from a finished skin and only replace the ball or the ticks, browse the catalogue at osuskins.org and keep the rest of the element set together — mixing a new ball into a skin whose follow circle and tick were designed as a set is how most “why does this slider feel wrong?” cases start.
Notes by ZentaoLabs. osuskins.org is an unofficial fan catalogue, not affiliated with ppy or osu!.
Top comments (0)