Skip to content
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.

Adjusting pp lost on a miss based on location of miss within the map #141

Open
Stats-Kun opened this issue Aug 17, 2021 · 2 comments
Open

Comments

@Stats-Kun
Copy link

Instead of only applying a 0.97x Multiplier for every individual miss regardless of the difficulty of the Section the miss was made, It may likely be more representative of the score to change how much of the performance was lost based on where it was missed.
One method I had thought of for a while, (one that i had also wanted to test but never necessarily had the knowhow to actually create), was to basically take a copy of the map in question and take the Map Difficulty (Effectively, The Difficulty Star Rating in all modes aside from Standard) and apply the same calculations but with the Score's Missed Notes Removed.
This is basically aking the difficulty system, "What did the Player actually manage to play?" and Rewarding a player based off of what they did hit as base before applying the still necessary Accuracy, Combo and other Bonuses or Penalties as of the score.
in Effect, It's going to hit scores where the majority of misses are in the Hardest Section the most, and are going to benefit those who missed a single note in a slow section either right at the begining or end of a map, to make sure people are still penalised for a miss, some minimum loss can be implemented (although certainly less than -3% in most cases unless the map is particularly low in combo).

@peppy
Copy link
Member

peppy commented Aug 17, 2021

I'm pretty sure this is a duplicate of tens of other proposals. The statistics required for improvements like this are being considered as part of the roadmap forward with lazer, but not available with existing scores.

@stanriders
Copy link
Member

This is being pretty much covered as best as possible with current score data in ppy/osu#13583

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants