Two different accuracy formats coexist in the API

[TTTaevas]

It is far from new so I figure it is already well-known, but I find it enough of an annoyance to open an issue

It's possible through the API to get the accuracy of Scores through several routes, it will always be in a format where "1" is the maximum accuracy (displayed as 100% in-game/web) It's also possible through the API to get the hit_accuracy of UserStatistics through several routes, it will always be in a format where "100" is the maximum accuracy

As someone who's in charge of an API wrapper, I'd definitely prefer if there was only a single format, preferably the one used by Scores

Would making any change on that front cause too many things to break, even if the benefits of such a change were to be locked behind a new x-api-version version?

[peppy]

@ppy/team-web thoughts on this?

[nanaya]

I'd probably rather add a new field and eventually remove the old one instead of dealing with versioning (and potentially keeping it forever?)

[notbakaneko]

I'm with making the range 0 to 1 and using a new field; api header for versioning with a formatting change is just just confusing.