Topic: Tag implication: classic_amy_rose -> amy_rose

The tag implication #69230 classic_amy_rose -> amy_rose is pending approval.

Reason: I believe this is pretty obvious; classic Amy is a specific subset of Amy Rose, so I believe the classic Amy tag should be implicated as such. Most posts involving classic Amy have already been tagged with Amy Rose as well, but the automatic implication isn't there yet. The same has already been done for classic Sonic and classic Tails being implicated to their main versions, but not for Amy (and Knuckles it seems) yet.

Different forms of a character shouldn't be tagged together, unless they're both present. So someone can search for posts that have both classic Amy and normal Amy in the same image with "classic_amy_rose amy_rose", rather than that search giving posts that only have classic Amy. Or if someone wants to search for posts that have normal Amy regardless of classic Amy also being present, a search for amy_rose would return posts that only have classic Amy, while amy_rose -classic_amy_rose would exclude posts that have normal Amy alongside classic Amy, if classic Amy was also tagged with the normal Amy tag.

watsit said:
Different forms of a character shouldn't be tagged together, unless they're both present. So someone can search for posts that have both classic Amy and normal Amy in the same image with "classic_amy_rose amy_rose", rather than that search giving posts that only have classic Amy. Or if someone wants to search for posts that have normal Amy regardless of classic Amy also being present, a search for amy_rose would return posts that only have classic Amy, while amy_rose -classic_amy_rose would exclude posts that have normal Amy alongside classic Amy, if classic Amy was also tagged with the normal Amy tag.

I just find it very odd that the implied tag was done for Sonic and Tails, but not for Amy and Knuckles? Feels like inconsistency.
And most classic Amy posts are still tagged under the main Amy Rose (and all classic Sonic pics are tagged Sonic the Hedgehog) anyways, regardless of how you feel about it.

You do bring up a fair point about posts having both versions of the character present, but currently as how most posts are tagged it's not really helping. And the amount of posts that have both versions present are in the minority.

The bulk update request #12192 is pending approval.

remove implication classic_sonic (856) -> sonic_the_hedgehog (24257)
remove implication classic_tails (365) -> miles_prower (20433)

Reason: The alternative

I've said it before, but this is a really odd policy. it means that characters with official* alternate designs/forms get multiple tags for really good reason.
^{_{*only official alt forms because unofficial ones still get tagged with the base character tag regardless of how little they resemble the original form. and the official alt forms are kept separate regardless of how similar they look to base.}}

this forum post, and others I've made in that thread are more detailed reasons for why I oppose this policy overall, and think we should consider reworking it to make it less... dumb.

Maybe there should be a base "amy rose" tag with "modern amy rose" and "classic amy rose" tags that implicate it?

Another previous forum topic where I made the same Classic Amy Rose implication request to match Sonic and Knuckles:

topic #39477

As above, the reason given by Watsit is that it's done like this for searchability purposes.

Character tags like this must remain separate or have a "any form" tag implied so that people can find posts that have Classic Sonic but not Modern Sonic, Modern Sonic but not Classic Sonic, and both characters simultaneously.
This is the sort of thing that is going to extend far beyond the Sonic the Hedgehog series (different LoZ Links, for instance) so any pattern of form/design implications would need hundreds/thousands of tags to be looked at.

In a perfect world, people would just know and use the ~x ~y syntax, or the site itself would suggest things like "searching for Asriel? click this link to view normal Asriel and/or god Asriel."

eightoflakes said:
Maybe there should be a base "amy rose" tag with "modern amy rose" and "classic amy rose" tags that implicate it?

Something like this would be ideal for characters that are commonly depicted as different forms, although making amy_rose the base tag could be a problem if people are used to tagging that for modern Amy. If people only tag amy_rose for modern Amy, leaving modern_amy_rose largely undertagged, while classic_amy_rose implies amy_rose, that would leave us with the same issue this policy tries to avoid.