0

The tags for questions concerning Diablo 3 characters look very redundant like this:

For Starcraft there is no and . It is just .

I understand that the term demon hunter is used in multiple games and selecting just demon hunter might confuse some people, because the questions might be for Warcraft 3 and WoW, but I assume everybody understands how to query a search bar. Plus it is the same for tags like micro.

I suggest to change etc. to and perhaps explain how the search bar works, e.g. searching for " " would yield the same results as "". Especially after someone selects a specific tag.

11

The primary reason for tags is not for searching. You can just search for "diablo 3 demon hunter", no square brackets, and it will work just fine. Tags are primarily used for filtering - e.g. if someone is interested in all Demon Hunter questions she can "star" the tag (follow it), and then questions about it will be tinted differently and it will be included in the "my tags" tab of the unanswered questions page.

Likewise, if someone wants to filter away all questions about Witch Doctor, because he doesn't play that class, he can mark that tag is ignored.

So, why and not just ? Because "Demon Hunter" is not unique enough to Diablo III. And even if it is, and definitely aren't. And now this may collide with, say, the hypoethetical .

, and are pretty unique, so we don't need the prefix there. If Diablo III's class names were far more unique, such as "Zacharum Warrior", I don't think we'd need the prefix there, either.

Or at least, this is my opinion :) I've also wrote about in in another meta-question which discussed the validity of these tags in the first place.

5
  • +1 Exactly what I was going to say, but you beat me to the punch :)
    – Wipqozn Mod
    May 21 '12 at 11:36
  • But would it not be even cooler if you could specify tag sets for this. E.g. I am interested in [diablo-3][monk] but not in [diablo-3][wizard] etc. This would also solve this. But I see your point and this is just another suggestion.
    – ayckoster
    May 21 '12 at 11:42
  • @ayckoster well our platform doesn't support that. You are welcome to open a feature-request about it here in meta, though! The StackExchange team is usually opposed to adding features only to one site of the Stack Exchange site family, though, so I recommend that you try to make your case as solid as possible if you want to ask for such a feature, or otherwise show how it is applicable to all the network's sites.
    – Oak
    May 21 '12 at 11:46
  • @ayckoster The problem is that "tag sets" aren't supported by the tagging system. We have made requests for changes, but they have been denied (apparently the tag system is Really hard to change, due to the way the site is designed). Therefore we need to do our best with the system we are given.
    – Wipqozn Mod
    May 21 '12 at 11:46
  • @ayckoster: I also get the feeling that this would require hierarchal tagging, which has been explicitly denied in the past (see the Sci-Fi and and Fantasy meta post where I discussed a similar issue, and Joel's initial reason for not doing something like this in the first place).
    – MBraedley
    May 21 '12 at 11:56

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .
https://gaming.meta.stackexchange.com/questions/4701/why-do-we-have-tags-like-diablo-3-demon-hunter
gaming.meta.stackexchange.com
crawl=CC-MAIN-2021-49
118002
application/http; msgtype=response
sha1:B3F3X6B6X4KZNUF3W4YRFUT3VCG2YAIE
<urn:uuid:91963f77-7ed3-466b-a6e5-4d3b7cda8d1c>
2021-12-02T06:05:08Z
151.101.65.69
text/html
sha1:T4JXOFTGCE3OK4ZTAV4PPRNPZJLMVHOY
<urn:uuid:5b12323b-5a34-41ad-84da-0c660475e248>
https://gaming.meta.stackexchange.com/questions/4701/why-do-we-have-tags-like-diablo-3-demon-hunter
response
<urn:uuid:9b8d1cde-283d-420d-933f-035d5f3cb9ca>
isPartOf: CC-MAIN-2021-49
publisher: Common Crawl
description: Wide crawl of the web for November/December 2021
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-102
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/