wiki
Requested page is not yet translated to the selected language (Italiano). Showing English version.

osu!catch ranking criteria

Notice: This article is an extension of the general ranking criteria.

This set of osu!catch ranking criteria lays out rules and guidelines that osu!catch-specific beatmaps must follow in order to progress through the beatmap ranking procedure.

Overall

Overall rules and guidelines apply to every kind of osu!catch difficulty. Rhythm-related rules and guidelines apply to approximately 180 BPM beatmaps with 4/4 time signatures. If your song is drastically faster or slower, some variables might be different, as detailed in Scaling BPM on the Ranking Criteria.

General

Rules

  • Your map must theoretically be possible to SS. This means it must be possible to catch absolutely all fruits, drops and droplets.
  • Each beatmap must use at least two different custom combo colours unless the default skin is forced. The combo colours must not blend with the beatmap's background/storyboard/video in any case. This is so hit objects are always visible to the player and custom skin's combo colours do not blend with the background accidentally.
  • Do not use keysounds without hitnormal support. If sounds blend perfectly with the song, feedback for hitting notes is minimal.

Guidelines

  • All circles and slider heads should represent a sound existing in the music. This is usually a distinct sound, but can also represent a continuous sound with an indistinguishable start or end.
  • Sliderends of extended sliders should be snapped according to the song's beat structure. If the song is using a straight beat, 1/4, 1/8, and 1/16 should be used. If the song is using a swing beat, 1/6 or 1/12 should be used. If the song has a sound in a different snap from what was recommended, snapping to an actual beat always takes priority.
  • Dashes and hyperdashes should not be used when the destination of the dash or hyperdash is located near the left or right border of the playfield. This creates an uncomfortable movement as the catcher is forcibly stopped upon reaching the border of the playfield (x:16 on the left and x:496 on the right).
  • Ensure combos do not reach unreasonable lengths. Caught fruits will stack up on the plate and can potentially obstruct the player's view. Bear in mind that slider tails, repeats and spinner bananas also count as "fruits". New combos should be placed regularly to clear the plate and avoid this.
  • Try to have at least one spinner in each difficulty to create variety in the map and fluctuation among scores. However, if a spinner just doesn't fit anywhere in the song, then there's no need to force one.
  • Overall Difficulty should have the same value as the Approach Rate. This is just a standardised value, as Overall Difficulty does not affect gameplay nor does the number of fruits a spinner has. Overall Difficulty only affects the maximum score of a difficulty.
    • If a difficulty uses a lower Approach Rate than one or more difficulties in the difficulty level below it, then the Overall Difficulty should be equal to that of the highest Overall Difficulty value in the previous difficulty level.
  • Slider tick rate should be set according to the song. For example if your song only uses 1/3 snapping, using tick rate 2 or 4 would not be fitting.
  • Use the same slider tick rate on every difficulty as it is a property of the music rather than the mapping. However, lower difficulties may use lower tick rates to reduce accuracy requirements for newer players, providing they still follow the rhythm of the song. Using high tick rates purely to increase score/combo/difficulty is senseless.
  • Avoid using combo colours with ~50 luminosity or lower. Dark colours impact the readability of fruits with low background dim.
  • Avoid using combo colours with ~220 luminosity or higher if Kiai time is used. Light colours create bright pulses during Kiai time, which can be unpleasant to the eyes.

Skinning

Rules

  • Custom catchers must be included in v2 skin format. This is to ensure correct display on all skins. The required filenames are fruit-catcher-idle.png, fruit-catcher-kiai.png and fruit-catcher-fail.png.
  • Custom objects must include all necessary elements and be coloured in a scale of grey colours. This is to ensure that your images are clearly defined and of acceptable quality. The needed elements can be found at Skinning/osu!catch. Additionally, it is recommendable to use transparent elements for the overlays.
  • Skinned elements must be the same size as their default skin counterparts. This is so they represent the hitbox properly and don't alter gameplay. The current dimensions used in the default skin are 128x128 pixels for the fruits, 82x103 for the drops and 306x320 for the catcher.

Guidelines

  • Custom catchers should additionally include the element lighting.png to complete the skin set. This element is however optional to add and has default dimensions of 184x184 pixels, though it may vary depending on the desired visibility of the element.

Difficulty-specific

Difficulty-specific rules and guidelines do only apply to the difficulty level they are listed for and therefore do not apply to every osu!catch difficulty. Rhythm-related rules and guidelines apply to approximately 180 BPM beatmaps. If your song is drastically faster or slower, some variables might be different, as detailed in Scaling BPM on the Ranking Criteria.

Difficulty names

Main article: Difficulty Naming

  • Cup
  • Salad
  • Platter
  • Rain
  • Overdose

Snapping reference table

Difficulty Basic-snapped dash Higher-snapped dash Basic-snapped hyperdash Higher-snapped hyperdash
Cup - - - -
Salad 250 ms or higher 125-249 ms - -
Platter 125 ms or higher 62-124 ms 250 ms or higher 125-249 ms
Rain 125 ms or higher 62-124 ms 125 ms or higher 62-124 ms
Overdose - - - -

Cup

Rules

  • Dashes and hyperdashes of any kind are disallowed. This is to ensure an easy starting experience to beginner players. In order to test that out, it must be possible to achieve an SS rank on the difficulty without making use of the dash key.
  • At least 250 ms must be left between circles/sliders and the start and end of spinners. This is to ensure readability.

Guidelines

  • Combos should not exceed 8 objects including slider tails and repeats. Spinners are an exception.
  • Note density should follow a mostly 1/1 pattern. 1/2 and/or 1/3 patterns should be used sparingly.

Difficulty setting guidelines

Salad

Rules

  • Hyperdashes of any kind are disallowed. This is to ensure a manageable step in difficulty for novice players.
  • Dashes must have at least a 125 ms gap between their two objects.
  • Dashes that are basic-snapped must not be used more than two times between consecutive fruits.
  • Dashes that are higher-snapped must always be followed by a walk.
  • Edge dashes must not be used. They require extremely precise timing which cannot be expected of less-experienced players.
  • At least 250 ms must be left between circles/sliders and the start and end of spinners. This is to ensure readability.

Guidelines

  • All distances should be clear on whether they require the player to walk or dash. This is to ensure that players can easily recognize patterns that require dashing.
  • Dashes that are basic-snapped should not be used consecutively when different beat snaps are used. For example, a 1/1 dash followed by a 1/2 dash.
  • Dashes that are higher-snapped should not be followed by antiflow patterns.
  • Combos should not exceed 10 objects including slider tails and repeats. Spinners are an exception.
  • Note density should follow a mostly 1/1 and 1/2 pattern. 1/3 and/or 1/4 patterns should be used sparingly.

Difficulty setting guidelines

Platter

Rules

  • Hyperdashes must have at least a 125 ms gap between their two objects.
  • Hyperdashes cannot be used on individual drops and/or slider repetitions. The accuracy and control required is unreasonable at this level and can create a situation where the player potentially fails to read the slider path.
  • Hyperdashes of a different beat snap must not be used between consecutive fruits. For example, a 1/2 hyperdash followed by a 1/4 hyperdash.
  • Hyperdashes that are basic-snapped must not be used more than two times between consecutive fruits.
  • Hyperdashes that are higher-snapped must not be used in conjunction with any other dashes or hyperdashes.
  • Dashes must have at least a 62 ms gap between their two objects.
  • Dashes that are basic-snapped must not be used more than four times between consecutive fruits.
  • Dashes that are higher-snapped can be used up to two times between consecutive fruits, provided there isn't a direction change between them.
  • Edge dashes must not be used. They require extremely precise timing which cannot be expected of less-experienced players.
  • At least 125 ms must be left between circles/sliders and the start of spinners. This is to ensure readability.
  • At least 250 ms must be left between circles/sliders and the end of spinners. This is to ensure readability.

Guidelines

  • Strong hyperdashes should not be used. For basic-snapped hyperdashes, a limit of 1.5 times the trigger distance is recommended. For higher-snapped hyperdashes, a limit of 1.3 times the trigger distance is recommended instead.
  • Hyperdashes that are basic-snapped may be used in conjunction with antiflow patterns. If used, the spacing should not exceed a distance snap of 1.2 times the trigger distance when followed by a walk, or 1.1 times the trigger distance when followed by a basic-snapped dash.
  • Hyperdashes that are higher-snapped should not be followed by antiflow patterns. If used, the spacing should not exceed a distance snap of 1.1 times the trigger distance and the movement after the hyperdash must be a walk.
  • Combos should not exceed 12 objects including slider tails and repeats. Spinners are an exception.
  • Note density should follow a mostly 1/2 and/or 1/3 pattern. 1/4 and/or 1/6 patterns should be used sparingly.

Difficulty setting guidelines

Rain

Rules

Guidelines

  • Hyperdashes should not be used on individual drops and/or slider repetitions.
  • Hyperdashes that are basic-snapped should not be used consecutively when different beat snaps are used. For example, a 1/1 hyperdash followed by a 1/2 hyperdash.
  • Hyperdashes that are higher-snapped should not be followed by antiflow dashes with a gap lower than 250ms.
  • Edge dashes may only be used singularly (not in conjunction with other dashes or hyperdashes).
  • Combos should not exceed 16 objects including slider tails and repeats. Spinners are an exception.
  • Note density should follow a mostly 1/2 + 1/4 and/or 1/3 + 1/6 pattern. 1/8 patterns and higher should be used sparingly.

Difficulty setting guidelines

Overdose

Rules

  • At least 62 ms must be left between circles/sliders and the start of spinners. This is to ensure readability.
  • At least 125 ms must be left between circles/sliders and the end of spinners. This is to ensure readability.

Guidelines

  • Hyperdashes should only be used on drops and/or slider repetitions when the slider path is simple and easy-to-follow. This is to prevent chaotic or unreasonably difficult slider movement, as transitioning into and out of complex slider shapes with hyperdash is usually uncomfortable to play, and a major penalty to accuracy for little benefit.
  • 1/8 and higher hyperdashes should not be used between consecutive object pairs.
  • Edge dashes may be used with caution for a maximum of three consecutive objects, and should not be used after hyperdashes.
  • Combos should not exceed 16 objects including slider tails and repeats. Spinners are an exception.
  • Note density should follow a mostly 1/2 + 1/4 and/or 1/3 + 1/6 pattern. 1/8 patterns and higher should be used sparingly.

Difficulty setting guidelines