Titanic Ranking Criteria

This set of ranking criteria lays out rules and guidelines that beatmaps must follow in order to progress through the beatmap ranking procedure. The ranking criteria mostly follows the original one with some minor changes.

The rules also have been simplified, to give mappers a clearer perspective on what's required to create a rankable map. Sections that are not covered in this document should be referenced from here.

For a map to be ranked, it has to follow this ranking criteria, as well be reviewed by at least 2 independent BAT members, plus one for each mode. This means, that a BAT can't approve their own beatmap and beatmaps with multiple game modes also require approval from more BAT members of that game mode. This criteria may change in the future, due to increasing map requests and BAT members.

Beatmap

• Make sure everything in the map is cleared in terms of content usage permissions.
• Difficulties must be at least 30 seconds long.
• Maps should use at least 80% of the audio file. If you want to end the map earlier, try cutting the song.
• Maps must not use decimal settings. (i.e AR9.3 -> 9)

Spread

• Mapsets must have a total drain time of at least 90 seconds (1 minute and 30 seconds).
• Difficulty names must have progression.
• Easy -> Normal -> Hard -> Insane -> Expert is default.
• Logical naming schemes like Seed -> Sprout -> Tree are okay too.
• Exception: The hardest difficulty can use a custom name, like Normal -> Hard -> Melancholy.
• Don't skip difficulties. For example, if you have Normal and Insane difficulties, you need a Hard too.
• A guest mapper can't create more difficulties than the host.

Slider Usage

• Using Perfect Curve sliders is highly discouraged.
• Perfect Curve sliders are the type of sliders creating when a slider has 3 control points in clients b20121106 or later
• 
• These sliders get converted to the Catmull curve type on older clients. This causes slider shapes to differ greatly, creating gameplay differences on those clients. To avoid this issue we highly encourage mappers to use any of the other curve types. In the image above you can see how identical slider skeleton lines create completely different slider paths on each curve type.
• Exception: Perfect Curve sliders with extremely small amounts of curve will generally convert fine, but for safety we recommend not using them.
• For information on how to avoid using Perfect Curve, check out this forum post!

Visuals

• Avoid using combo colours, slider borders or hitcircleoverlays with ~50 luminosity or lower. Dark colours like these impact readability of approach circles with high background dim and the other elements partially give up their functions as borders.
• Avoid using combo colours and custom slider track colours with ~220 luminosity or higher during kiai times. They create bright pulses which can be unpleasant to the eyes.

Hitsounds

• Maps must be hitsounded, excluding osu!mania maps.
• Every clickable object must have audible feedback.

Timing

• Maps must be correctly timed. This includes BPM and time signatures.
• All difficulties must use the same timing.
• Do not change timing to adjust slider velocity.
• Objects must be snapped to timeline ticks.
• Only one object is allowed per tick, excluding osu!mania maps.
• Manual lead in time must be added to ensure the first object starts after 1500ms

Metadata

• Metadata must be accurate.
• Use a primary metadata source.
• If the song has a Ranked or Loved map, use that map's metadata unless it's blatantly wrong.
• Use Modified Hepburn romanisation for Japanese words.

Tags

• Add usernames of anyone who contributes to the map. This doesn't include modders.
• Add the song's genre and language.
• Add featured artist if the song is in the Featured Artist catalogue.
• Other tags must be relevant to the song/map.

Title

• Songs shortened for TV must have (TV Size).
• Replace game version markers with (Game Ver.).
• Replace short version markers with (Short Ver.).
• Use (Cut Ver.) to indicate an unofficial song cut.
• Use (Extended Edit) to indicate an unofficial song extension.
• Use (Sped Up Ver.) to indicate an unofficial song tempo increase. For some genres, (Nightcore Mix) is an okay alternative.

Source

• Use the Source field if the song is from another media source, like a game, movie, or event.

Files

• Don't use inappropriate content. See song content rules and visual content considerations.
• Don't include unused files in the map folder.

Song

• Use .mp3 or .ogg file formats.
• At most 192 kbps for .mp3 files.
• At most 208 kbps for .ogg files.
• At least 128 kbps for any filetype.
• One song file must be used for all difficulties.
• Set a consistent preview point for all difficulties.

Hitsounds

• Hitsound files must be at least 25 ms long and use .wav or .ogg file formats.
• Do not use .mp3.
• Exception: Use this file for silent hitsounds.
• Hitsounds must not be delayed.

Background

• Every difficulty must have a background adhering to the following:
• Minimum width: 160 px
• Minimum height: 120 px
• Maximum width: 2560 px
• Maximum height: 1440 px
• Maximum file size: 2.5 MB
• Link the source of the map's background in the description.

Video

• Videos must adhere to the following:
• Maximum video resolution: 1280x720
• Video encoding: H.264
• The audio track must be removed from video files.

Mode-specific

Please refer to the osu! wiki for the full game-mode sepecific ranking criterias!

osu!

• No offscreen objects in 4:3 aspect ratios.
• The Auto mod must achieve bonus score on spinners. They're too short otherwise.
• Use at least two combo colors.

osu!taiko

• Avoid covering essential parts of the background with the taiko playfield. You can edit the vertical offset of the background in the .osu file.
• Avoid rapid kiai toggles.
• On rhythms that are 1/4 or faster, use big notes only at the end of patterns.
• Avoid slider velocity changes on lower difficulties.
• Each difficulty should follow its respective break length guidelines:

Difficulty	Break	Chain length
Kantan		Break needed every 32–36 beats
Futsuu		Break needed every 32–36 beats
Muzukashii (option 1)		Break needed every 16–20 beats
Muzukashii (option 2)		Break needed every 16–20 beats
Oni		Break needed every 16–20 beats

osu!catch

• The Auto mod must be able to SS your map.
• Avoid dashes and hyperdashes that lead to the edges of the screen. Placements between x = 16 and x = 496 are okay.
• Overall difficulty should match approach rate.

osu!mania

• Spread rules apply to each key mode or playstyle separately. For example, if you have 4K and 7K difficulties, you need two difficulty spreads.
• Beatmaps can only use 4–10, 12, 14, 16, or 18 keys. Key modes over 10 keys must use certain playstyles.
• No column can be left empty.
• No more than 6 notes can be pressed at the same time in Insane or lower difficulties.
• Difficulties using an N+1 playstyle must enable the Use special style (N+1 style) for mania toggle.

Song interpretation

Note: This section is based on subjective mapping views, not the ranking criteria.

Every element of a map should represent the song.

This principle sounds simple, but it might be the most controversial part of ranking a map! There's no correct way to interpret a song, so each individual's interpretation varies, and the Beatmap Approval Team determine if your interpretation is valid for Ranked status. Every BAT member may have a different opinion on this subject, but it's a good idea to follow older mapping styles.

These pointers may also lead you in the right direction:

• Correlate map and song intensity.
• Rhythm: Intense parts have more rhythm density than calm parts.
• Spacing: Intense parts have higher jump distance than calm parts.
• Slider velocity: Intense parts have faster sliders than calm parts.
• Design: Intense parts have more complex object composition than calm parts.
• When the song gradually increases or decreases intensity, show a gradual progression of any elements above.
• Show song variation through contrast.
• Establish some core ideas for your mapping choices.
• When the song enters a new section, shift those mapping ideas according to how different the song feels.
• If a specific sound only occurs once or twice in a song, make it stand out by clearly deviating from your usual mapping choices.
• Be consistent (within reason).
• When a song repeats itself, it makes sense to repeat your map too.
• Copying and pasting part of your map can be pretty boring though, so when a song repeats, vary your map in ways that don't drastically change how you previously interpreted the song.
• Ask how your objects fit into the "every element of a map should represent the song" principle.
• Example 1: "How does this object represent the sound it aligns with?"
• Example 2: "How does this section of objects follow the general mood of this section of the song?"
• Consider how other people will interpret your map. If your way of interpreting the song isn't clear, it'll feel like your map doesn't follow the song!