Fix incorrect limit for sliderbreak estimation #33110
Conversation
|
!diffcalc |
This comment was marked as outdated.
This comment was marked as outdated.
|
!diffcalc |
This comment was marked as outdated.
This comment was marked as outdated.
|
!diffcalc |
This comment was marked as outdated.
This comment was marked as outdated.
|
!diffcalc |
github-project-automation
bot
moved this from Pending Review
to Pending Deploy
in Difficulty calculation changes
* fix incorrect clamp * Add inline comment to explain `possibleBreaks` calculation * move limit to aim and speed functions * fix negative okMehAdjustment * fix cases where lazer effective misscount gets reduced * Simplify scope of changes * Correct variable name --------- Co-authored-by: James Wilson <[email protected]>
stanriders
moved this from Pending Deploy
to Deployed
in Difficulty calculation changes
3 participants
This score https://osu.ppy.sh/scores/4357222093 being estimated to have more than 1 sliderbreak despite being only 1x100 it estimates effectiveMisscount to be 1 using Math.Min, and then adds additional sliderbreaks with also using Math.Min
so it can estimate up to 2 sliderbreaks in case of 1x100