Maybe disallowing higher snapped antiflow dashes after a higher snapped hyperdash? The current rule is prohibiting too much but I think it should be limited somehow.
Agree with this part. In the case that was pointed out in https://osu.ppy.sh/beatmapsets/769584/discussion/1618190/timeline#/698216, this pattern should be completely rankable and fine.
Sanyi wrote:Maybe disallowing higher snapped antiflow dashes after a higher snapped hyperdash? The current rule is prohibiting too much but I think it should be limited somehow.
you're essentially saying at this point why even have a ranking criteria when bns/mappers should know what is fine and what isn't fine at this point
Ascendance wrote:But the point is that when people are already pointing out stuff that you've proposed to add, there's no real reason to add it. By then, we could potentially be limiting cases where it's completely fine.
Not completely agreeing with that point. Just because the rule isn't followed in it's current version, doesn't mean that every pattern it prohibited is ok a Rain. Let's take my previous suggestion as an example: In what scenario would a higher snapped antiflow dash after a higher snapped hyperdash not break a Rain?
Ascendance wrote:Without the RC, you create serious objective issues, some of which break levels of difficulty entirely. This, as has been proven by the lack of following of this rule, is not one of those.
This now allows for the usage of basic dashes after hypers in Rain Difficulties.
Ranking Criteria wrote:Basic hyperdashes can't be used more than four times between consecutive fruits. If higher snapped hyperdashes are used, they must not be used in conjunction with other hyperdashes or higher snapped dashes.