Hi!
Seeing some of the latest discussion regarding the osu!catch Ranking Criteria, I took on the work of doing a small cleanup of the Ranking Criteria. The following proposals are the result of a draft I discussed with Ascendance. An important note when reading this proposal is that striked red text represents removals, whereas italic green text represents additions.
Without further ado, let's move to the proposed changes!
Changes regarding definitions and minor wording changes
Specific changes to rules and guidelines related to dashes, edge dashes and hyperdashes
I wanted to give these changes a separate section, in order to better explain the reasoning behind them.
(General) Edge dashes combined with hyperdashes
The following rule should be removed: "Edge dashes must not be used in direct conjunction with hyperjumps. This is because such patterns require especially precise movement and force an unreasonable restriction on accuracy required to catch them.
Currently, this rule conflicts with recent approved changes to Overdose difficulties (https://osu.ppy.sh/community/forums/topics/901220). Thinking about ways to deal with this, I noticed that edge dashes are already regulated in the criteria of each difficulty. Edge dashes are explicitly prohibited in Cup, Salad and Platter difficulties, their combined usage with hyperdashes is explicitly prohibited in Rain difficulties, and the recently approved Overdose guideline already regulates them. Therefore, this general rule is redundant and can be removed.
(Salad) Consecutive higher-snapped dashes
The following rule should be removed: "Higher-snapped dashes of different beat snap must not be used between consecutive fruits.".
This is because there is another rule that says that "If higher-snapped dashes are used, they must be used singularly (not in conjunction with other dashes)." The first rule is already covered by the second one.
(Platter) Basic hyperdash strength
A recent proposal (https://osu.ppy.sh/community/forums/topics/907104) changed the rule regarding hyperdash strength after higher-snapped hyperdashes to a guideline, mainly due to the difficulty (or rather, tediousness) of measuring every single HDash for compliance with the rule. However, the rule that regulates the same thing, but for basic hyperdashes, wasn't changed.
Therefore, the proposal is that the same is done for the following rule:
"Basic hyperdashes may be used in conjunction with antiflow patterns. If used, the spacingmust should not exceed a distance snap of 1.2 times the trigger distance if followed by a walkable movement, or 1.1 times the trigger distance if followed by a basic dash."
(Rain) Consecutive higher-snapped hyperdashes
Similarly to the Salad change, the following rule should be removed: "Higher-snapped hyperdashes of different beat snap (1/2, 1/4, etc.) must not be used between consecutive fruits.".
This is also because there's another rule forbidding any type of consecutive higher-snapped hyperdashes, so this rule is already covered by the other one.
Changes relating to the order in which rules and guidelines appear
Discussion Deadline
Discussion will be initially open until Monday 5th of August at 4:00 UTC. Depending on the discussion that takes places, this deadline may be extended.
Seeing some of the latest discussion regarding the osu!catch Ranking Criteria, I took on the work of doing a small cleanup of the Ranking Criteria. The following proposals are the result of a draft I discussed with Ascendance. An important note when reading this proposal is that striked red text represents removals, whereas italic green text represents additions.
Without further ado, let's move to the proposed changes!
Changes regarding definitions and minor wording changes
Glossary
General Rules
General Guidelines
Skinning Rules
- Fruit: A large object representing
represented bya hitcircle, slider head, tail or repeat. - Drop: A medium-sized object representing
represented bya slider tick. - Droplet: A small object representing a slider body. Missing these will reduce your accuracy, but unlike fruits and drops
the above, will not result in a combo break. - Active object: An object that must be caught in order to maintain combo, namely fruits and drops.
- Walk: Any
distancespacing between two objects where no dash is needed to catch both. JumpDash: A spacing between two objects that requires the use of the dash key to catch both.Hyperjump: A more exaggerated spacing which cannot be caught by normal dashing. During play, hyperdash will be triggered between the two objects, characterised by a coloured outline on the first object.- Hyperdash: Objects generated when the spacing between two active objects is too far apart to be caught by normal dashing. During play, this is characterized by a coloured outline on the first object. The term is also used to describe the movement between the two objects.
- Trigger distance: The minimum spacing between two active objects at which a hyperdash is generated between them.
- Edge dash: A very large spacing between two active objects where the required Trigger Distance is not reached, and as such, a
hyperjumphyperdash is not generated. The first object must be caught with the edge of the plate in order to catch the second object at all. - Basic dash/hyperdash: Any dash or hyperdash whose time between
fruitsactive objects is at least twice the time required to allow dashes or hyperdashes, respectively. As an example, a hyperdash between objects separated by 250 ms in a Platter classifies as a basic hyperdash.
General Rules
- Your map must theoretically be possible to SS. This means it must be possible to catch absolutely all fruits,
includingdrops and droplets. - Each map must use at least two different combo colours which must not blend in with the map's background/storyboard/video. This is so
hitobjects are always visible to the player.
General Guidelines
- Dashes and hyperdashes should not be used when the destination of the dash or hyperdash
hyperjumpis located near the left or right border of the play field. This creates an uncomfortable movement as the catcher is forcibly stopped upon reaching the border of the playfield. Try to leave at least 16 osu!pixels of space between the end point of the dash/hyperdashhyperjumpand the border of the play field,respectivelynamely at x:16 or x:496.
Skinning Rules
- Custom
fruitsobjects 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.
Specific changes to rules and guidelines related to dashes, edge dashes and hyperdashes
I wanted to give these changes a separate section, in order to better explain the reasoning behind them.
(General) Edge dashes combined with hyperdashes
The following rule should be removed: "Edge dashes must not be used in direct conjunction with hyperjumps. This is because such patterns require especially precise movement and force an unreasonable restriction on accuracy required to catch them.
Currently, this rule conflicts with recent approved changes to Overdose difficulties (https://osu.ppy.sh/community/forums/topics/901220). Thinking about ways to deal with this, I noticed that edge dashes are already regulated in the criteria of each difficulty. Edge dashes are explicitly prohibited in Cup, Salad and Platter difficulties, their combined usage with hyperdashes is explicitly prohibited in Rain difficulties, and the recently approved Overdose guideline already regulates them. Therefore, this general rule is redundant and can be removed.
(Salad) Consecutive higher-snapped dashes
The following rule should be removed: "Higher-snapped dashes of different beat snap must not be used between consecutive fruits.".
This is because there is another rule that says that "If higher-snapped dashes are used, they must be used singularly (not in conjunction with other dashes)." The first rule is already covered by the second one.
(Platter) Basic hyperdash strength
A recent proposal (https://osu.ppy.sh/community/forums/topics/907104) changed the rule regarding hyperdash strength after higher-snapped hyperdashes to a guideline, mainly due to the difficulty (or rather, tediousness) of measuring every single HDash for compliance with the rule. However, the rule that regulates the same thing, but for basic hyperdashes, wasn't changed.
Therefore, the proposal is that the same is done for the following rule:
"Basic hyperdashes may be used in conjunction with antiflow patterns. If used, the spacing
(Rain) Consecutive higher-snapped hyperdashes
Similarly to the Salad change, the following rule should be removed: "Higher-snapped hyperdashes of different beat snap (1/2, 1/4, etc.) must not be used between consecutive fruits.".
This is also because there's another rule forbidding any type of consecutive higher-snapped hyperdashes, so this rule is already covered by the other one.
Changes relating to the order in which rules and guidelines appear
The Ranking Criteria has been updated as discussion happens, which has made the order in which certain rules and guidelines appear rather awkward to follow. Just to give an example, the current guideline regulating overall hyperdash strength in Platters comes after the guideline regulating the strength for hyperdashes followed by antiflow patterns. It is obvious that the latter is a more general guideline, and should therefore be read first.
Since listing such order changes in this forum post would make this even lengthier, I have prepared a Google Document assuming all the proposed changes go through (so it's basically a preview of a finalized Ranking Criteria), and in which order changes are indicated in blue. You can find said document here: https://docs.google.com/document/d/1mw6I2Ufy8kBL90leiRgvnoeX-1b2ASoV9NtzNuboxuw/edit?usp=sharing
Since listing such order changes in this forum post would make this even lengthier, I have prepared a Google Document assuming all the proposed changes go through (so it's basically a preview of a finalized Ranking Criteria), and in which order changes are indicated in blue. You can find said document here: https://docs.google.com/document/d/1mw6I2Ufy8kBL90leiRgvnoeX-1b2ASoV9NtzNuboxuw/edit?usp=sharing
Discussion Deadline
Discussion will be initially open until Monday 5th of August at 4:00 UTC. Depending on the discussion that takes places, this deadline may be extended.