Excluding map tags from search doesn't work

[Qunas101]

Current behavior: putting -tag in search doesn't seem to affect the results in any way

Expected behavior: It should exclude all maps with tag from search

Example: https://osu.ppy.sh/beatmapsets?g=10&q=ranked%3D2023%20-electronic&s=ranked - same example as in #10916, only back then this prompt produced a few maps that weren't tagged with electronic by mapper. Now all maps with electronic are included

[Qunas101]

It seems to only work if sorted by Relevance, and even then it's only a suggestion, it just pushes 'excluded' beatmaps to bottom

[peppy]

Bumping in priority since this is a primary use of tags / search.

[nanaya]

-thing seem to work though? The link above explicitly selected electronic genre but otherwise there's no electronic in the tag.

[nanaya]

I think more details is needed, preferably with screenshots and links on the query and the result

(I did cursory check and the result seems correct)

[Qunas101]

I think more details is needed, preferably with screenshots and links on the query and the result

Sure, I am an idiot for not including it in my reply

https://osu.ppy.sh/beatmapsets?l=8&q=ranked%3D2020%20-viking&s=ranked

Look at this example. Notice how the map with viking gets pushed to the bottom of the list. You can repeat the same process with other tags from maps in the example. Since maps are not removed from search completely, the sorting gets overwritten if you sort by anything other than Relevance.

[nanaya]

So it's not "affect the results in any way" but more of it's still included just with lower relevancy (and thus not useful when sorted by anything else).

Apparently it's from adding the user tag query... removing the specific part hides it again

osu-web/app/Libraries/Search/BeatmapsetSearch.php

Lines 64 to 69 in 12c5c2d

	->should([
	'nested' => [
	'path' => 'beatmaps',
	'query' => QueryHelper::queryString($this->params->queryString, ['beatmaps.top_tags'], 'or', 0.5 / count($terms)),
	],
	])

[Qunas101]

Also, beatmap search overlay on lazer experiences completely the same problem, but I assumed it works on the same web voodoo? So I didn't report it there