You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
Which is pretty limited info to deal with, and forces us to assume that the player breaks combo at whatever the calculated hardest parts of the map are. Having information relating to how accurately the player hit each note would allow to properly calculate performance of a play.
Hitoffsets is also valuable data I believe is needed for pp development. It's currently only available in replays, which are too expensive to access and are only available in top 500 scores. With score data containing an array of hitoffsets, it would finally be possible to analyze the actual difficulty of each note across a wide spectrum of players and maps.
I imagine you would only need an array of signed 16 bit values for this (32,768 is plenty enough for hit offset).
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
currently score data contains
Which is pretty limited info to deal with, and forces us to assume that the player breaks combo at whatever the calculated hardest parts of the map are. Having information relating to how accurately the player hit each note would allow to properly calculate performance of a play.
Hitoffsets is also valuable data I believe is needed for pp development. It's currently only available in replays, which are too expensive to access and are only available in top 500 scores. With score data containing an array of hitoffsets, it would finally be possible to analyze the actual difficulty of each note across a wide spectrum of players and maps.
I imagine you would only need an array of signed 16 bit values for this (32,768 is plenty enough for hit offset).
The text was updated successfully, but these errors were encountered: