Considering stuff like glacierfall is being pushed in qualified, might be a good idea to ensure visual components are still kept intact for cases like 00:33:955 (1) - where the sliderend is at the top right of the slider but the visual is at the bottom right
cuz sliderends (not reverse arrows or sliderheads!!!) have a 36 ms offset
this is also an issue for beatmaps like FALLEN 02:31:998 (1) - where u have to do this in order to 300 the slider where no player will (probably ever) play the slider like this
Maybe controversial since it would limit le choices for slider design but maybe a rule that states to ensure sliderend leniency overlapping with the visual sliderend like
Ensure -36 ms sliderend leniency offsets overlap the visual sliderend displayed for a slider or a guideline to ensure that the path that players need to take to 300 a slider is obvious or something like
Ensure players following through a slider via visual cues can 300/fully complete a slider See community/forums/posts/8237803
Not sure, but I'm mostly writing this to discuss and resolve to a definite answer regarding this, personally I would encourage a rule for leniency overlapping the visual end currently but there may be issues that I am missing with that
cuz sliderends (not reverse arrows or sliderheads!!!) have a 36 ms offset
this is also an issue for beatmaps like FALLEN 02:31:998 (1) - where u have to do this in order to 300 the slider where no player will (probably ever) play the slider like this
Not sure, but I'm mostly writing this to discuss and resolve to a definite answer regarding this, personally I would encourage a rule for leniency overlapping the visual end currently but there may be issues that I am missing with that