Feedback: User tags

[peppy]

We released the new "user tags" system last week in a relatively raw state, with the intention of building it out based on how the community wishes to see it grow. Feel free to leave your feedback and discuss the system here!

Please post one idea per comment thread to keep things organised.

[peppy]

Website doesn't show/respect threshold for tags "counting" (ppy/osu-web#12015)

In the client implementation tags change colour when they hit 10 votes, but this isn't conveyed on the beatmap info pages. We should probably hide tags which haven't hit this threshold from the beatmap pages (but still show at results so they can be upvoted easily).

The threshold system (and cutoff number) was an arbitrary decision, so feel free to discuss whether it feels too low / high / wrong.

[bdach]

addressed by #32579

[bdach]

will be resolved by ppy/osu-web#12047

[bdach]

resolved by ppy/osu-web#12042

[pajwoj]

Current tag data should be reworked for better usability.

In my opinion the tags should be significantly simplified or reworked to improve readability; I thought of a solution for this:

• Deprecate overly complex tags and retain simpler ones: tags like "song representation/difficulty spike" could be removed, while more intuitive tags like "tap/streams" or a basic "jump" tag (if it already exists, if not, then it should be created) could be kept; this way you get fewer details about the map, but it'd be way easier to classify most (which I think is the main challenge of this; putting tags on lots of maps, this way potentially some sort of bot could distinguish between e.g. streams and jumps and automatically tag most maps correctly) for both players and mappers.

Retaining the "sub-genre / slash" format for more detailed tagging would allow for more descriptors to be put on maps which equals more details, also no current data would have to be removed / changed, however it would be much harder to put those tags on maps, it would be harder to incorporate those in the search menu (unlike the option above, where it could just be a new row of search filters with only a few existing tags), and there would surely be misunderstandings / misclassifications with this system.

All in all I think the raw OMDB data has to be revised to allow a functioning, user-friendly tag system, usable and understandable for everyone, be it a beginner or someone very experienced.

[apollo-dw]

I would strongly encourage retaining the more complex tags like "difficulty spike" -- I absolutely saw them being used for discovery on OMDB side. It may seem like a lot at first, but I promise that with time it becomes digestible and very powerful.

Instead, focus should be placed on making the list of tags and their descriptions available in full somewhere (#32568 (comment)) so that people can slowly acclimatize to the selection of tags. Because I agree that right now it's probably unreadable, but I don't think that's because of the specific selection of tags.

[bdach]

Adjust user tag display thresholds (ppy/osu-web#12015)

As per issue thread, configurable, 5 votes to begin with, should only apply to beatmap info display

[bdach]

Improve UX of tag control

From #32534

The tag window sucks. The search bar is your one solace here, and it's really only useful if you know what tags you're looking for. The tags themselves appear to be arbitrarily organized within the list, and certainly aren't grouped together in any intuitive way

I've also seen it brought up (can't find link) that the window shouldn't auto-close after a tag is selected, because people generally want to assign multiple

[tovc]

Is there any reason that it needs to be a popout window? It seems like the current placement isn't exactly short of real-estate

[bdach]

I don't think there's any reason it needs to be one but the initial pitch was having it mirror the GitHub issue label popout thing. Not sure. Will require some experimenting.

I don't think a popout is bad as long as it's big enough. I've seen tags on some maps and they look pretty overwhelming already, so popout makes sense to me still, but I'm not ruling out some redesign of the entire control.

[tovc]

If the tagging window was further up the page and overlapping something, I think a popout would make sense, but as it is currently, it's below everything else and isn't overlapping anything

Again, this is getting into the scoring screen as a whole, but the dead space looks especially silly on ultrawide resolutions

[bdach]

Tag control is in a very hidden place

From #32534

The tag window is tucked away at the bottom of a screen that a lot of people don't know exists. I was screen sharing with a friend in discord the other day, and I opened the extend score information panel, and he said that was the first time he'd ever seen it. He's been playing lazer exclusively since he started playing ~3 years ago. That's maybe a topic for a future rework of the scoring screen, but putting the tags there, and only having them visible/accessible from there is just not good design

@peppy would like your opinion on this one, since the location was originally your suggestion I think

[bdach]

Tags are not supported well in client

Not shown in beatmap set overlay, not shown in song select, no support for searching by them in song select.

Probably wise to resolve #32568 (comment) first to avoid redundant work

[bdach]

display on beatmap set overlay -> #32610

[tovc]

Some 2b maps make achieving a C rank much harder than on regular maps

One example would be TheFatRat - Mayday (feat. Laura Brehm) (Voltaeyx). This map forces you to drop lots of slider ends, which results in much lower acc than on most other maps. This is ironic given that there's a specific tag for 2b

There should be a better way to qualify plays for tagging a map. Being above 60% of the average accuracy of the top 50 plays sounds good to me

[bdach]

somewhat duplicate of #32568 (comment)

also lazer generally is not very compatible with 2b right now so low priority in my eyes to a degree...

[tovc]

Somewhat, but it doesn't touch on initially achieving a C-rank. About half of the leaderboard is below a C-rank on that map

And yeah, I'm aware of lazer+2b. The client is actually a lot better for playing some 2b maps because it allows hitting object placements that would otherwise be impossible, but I do get that support is low priority. This seems like a reasonable enough thing to add tho

[tovc]

Mirror genre/langauge fields as beatmap tags

For future use, mainly. Would also allow adding genres beyond the 13 that the game has had for years

(and I want to tag atmospheric dnb maps as breakcore)

[tovc]

Allow creating beatmap collections exclusively from beatmap tags

More of a 'this would be nice' than a 'this is whats wrong with the current system'. I want to be able to, for example, create a beatmap collection with tags like reading/overlap reading and style/old-style revival, then have any maps that meet one or all of those tags added to that collection as my map library grows. Having language tags would also allow me to make a tap/streams language/metal collection

[apollo-dw]

Show the full list of tags somewhere

On OMDB, we had a full list of tags available on a page for people to peruse. It presented itself in a tree format, it contained descriptions for each tag and it allowed users to click on the tag to search maps with the tag. I think this is useful for exploration as well as acclimatizing to the list of tags.

[AJT127]

this echoes what I wrote in a different thread and was going to repost here on request: "it would also be nice if they were added to the menu to be searched by clicking (like language and genre)"

it could be optional if you think that having it in that menu by default would be too cluttered. the slashes are also kinda meaningless right now as you can't see the rest of the things under a certain umbrella, and several of these terms are not things that someone would independently think is a category to search e.g. "avant-garde"

there was also an explanation for each tag on omdb, maybe this could be incorporated somehow e.g. hovering over the tag brings a box with the explanation.

[AJT127]

could there be a website provision for mappers to tag their own maps without having to play them?

on another note, certain tags may only apply to certain difficulties of a mapset. especially for large sets, this differentiation would seem necessary for people actually looking for the map with that skillset

[bdach]

certain tags may only apply to certain difficulties of a mapset

The tagging system already works per-difficulty though?

[AJT127]

certain tags may only apply to certain difficulties of a mapset

The tagging system already works per-difficulty though?

oh i hadn't noticed that, my bad, nice one

[cyperdark]

Tags suggestion

• tap/doubles - patterns of two circles with same bpm
• tap/triples - patterns of three circles with same bpm
• tap/polyrhythm or rhythm/poly, for maps like sputnik (not sure if it's right name for bpm changes throughout the map

[cyperdark]

i dont know if it makes too much sense to add, but:

• jumps/squares
• jumps/triangles

[cyperdark]

jumps/fullscreen or aim/spaced jumps - maps like this:

• https://osu.ppy.sh/beatmapsets/1835522#osu/3768437
• https://osu.ppy.sh/beatmapsets/1804676#osu/3729848
• https://osu.ppy.sh/beatmapsets/1315615#osu/2726346

[cyperdark]

similar to tap/stamina will be nice to have a aim/stamina, maps like this:

• https://osu.ppy.sh/beatmapsets/1902178#osu

[cyperdark]

also tap/accelerating for accelerating streams and bursts:

• https://osu.ppy.sh/beatmapsets/1816952#osu/3727508
• https://osu.ppy.sh/beatmapsets/1826036#osu/3747453

[bdach]

Ruleset-specific tag support

see ppy/osu-web#12057, will likely require client-side adjustments as well