Open shrublet opened 4 years ago
Gonna remove the proposal tag from this since we've discussed something like this internally for quite a long time. With that being said this is probably dependent on having databasing of difficulty attribs.
Not sure it's going to be a radar chart, as opposed to some bars or similar. As a non-proposal it may be better to change the title to covering displaying more stats, rather than changing the display design methodology.
okay will change title- mostly mentioned radar graph bc I always thought it was a novel and interesting way to display stats, though admittedly goes against current design standard of lazer. (edit idrk what to name it so it's prob best if somebody else does haha)
Nice to read that more aspects than only star count of the vague term "difficulty" being displayed will be a thing in the future. I hope this thread applies to PP and skill breakdown aswell.
One more thing, could someone confirm please if it is just a coincidence or by-design that taking the natural logarithm of the number of pp a score is worth (not weighted) gives a a star rating how well the player did, which is surprisingly very accurate (up to a certain point at least) to actual beatmap difficulties. E.g.:
That's coincidence.
That's coincidence.
Too bad... Thanks for the reply.
Describe the new feature: A radar chart (similar to DDR as seen in this video) to showcase a map's traits at a glance. Ideally, it would allow players to gauge what a map is like before playing it (e.g. aim focused vs stream focused). Originally, I had come up with a bunch of semi-nebulous terms, but with the pp rework, there is now at least 3 objective terms (aim, tap, finger control) of star rating which could be implemented into said radar chart. It would be hard to properly objectify other terms used commonly by the community like tech etc, but having a radar chart of any amount of easily definable traits that play into difficulty would prove more helpful than just star rating by itself which is often misleading. A few additional examples could be like reading, something to do with frequent sv changes (an attempt to narrow down tech maps), or rhythm complexity (unsure if that's what finger control accounts for). Proposal designs of the feature: It could be put under the details sections under the points of failure graph if you scroll downwards since there's not much extra room there.