The tag implication #51398 classic_amy_rose -> amy_rose has been rejected.

Reason: classic_sonic implicates sonic_the_hedgehog, and classic_tails implicates miles_prower.

But those implications are not currently in place for Amy and Knuckles.

EDIT: The tag implication classic_amy_rose -> amy_rose (forum #371213) has been rejected by @slyroon.

I really do not like any of these implications existing.

lafcadio said:
post #1461481
Rosy the Rascal with Amy Rose

post #667380
Rosy the Rascal without Amy Rose

Do not implicate. Just search with ~ operators if you want images that have either one.

~rosy_the_rascal ~amy_rose

Different forms of a character are supposed to be separate for searchability purposes. Being that there are classic_sonic and classic_tails forms, that implies the existence of non-classic forms, which are only tagged sonic_the_hedgehog and miles_prower, so the classic_* form tags shouldn't implicate the non-classic form tags.

lafcadio said:
I really do not like any of these implications existing.

My reason for requesting this is that I occasionally see images that have the classic_amy_rose tag without the amy_rose tag:

classic_amy_rose -amy_rose

Ideally, that tag situation should never happen, because images with Classic Amy Rose are a subset of images of Amy Rose. So IMO all images with the Classic Amy tag should have the Amy tag.

A search for classic_tails -miles_prower will never bring up any results, because the tag implications automatically prevent it. The same should happen for Amy and Knuckles.

If it's decided that the site should not have these Classic_Sonic_Character -> Sonic_Character implications for any character, then I'll go along with that. But at the moment, there's an inconsistency between the characters.

EDIT: I posted that before I refreshed the page and saw Watsit's reply.

watsit said:
Different forms of a character are supposed to be separate for searchability purposes. Being that there are classic_sonic and classic_tails forms, that implies the existence of non-classic forms, which are only tagged sonic_the_hedgehog and miles_prower, so the classic_* form tags shouldn't implicate the non-classic form tags.

I think I see what you mean about searchability:

With these implications:

• If you want to search for images with only "modern" Amy you search: amy_rose -classic_amy_rose
• If you want to search for images with only "classic" Amy you search: classic_amy_rose
• If you want to search for images where both versions are in the same picture you can't do it, because the search amy_rose classic_amy_rose will give exactly the same results as the classic_amy_rose search.

Without these implications:

• If you want to search for images with only "modern" Amy you search: amy_rose
• If you want to search for images with only "classic" Amy you search: classic_amy_rose
• If you want to search for both in the same picture you search amy_rose classic_amy_rose

So that's fair enough; I agree there's a bit more searching flexibility if the site doesn't have the implications.

However, for that to work, they need to be accurately tagged! So I suppose we need to go through all the images of classic_amy and remove all the amy_rose tags from all images that don't feature Modern Amy?

And then remove the equivalent tag implications from Sonic and Tails, and do the same manual updates for them...?

An alternative is to establish more Sonic/Tails/Amy/Knuckles/etc. tags for things like the Dreamcast designs, spinoff designs like the very distinct Sonic Riders or storybook (Secret Rings, Black Knight) designs, etc.

To quote another staff member: "I am personally of the opinion that characters with multiple forms should all imply a base form of the character", and tagging projects like these often create "huge mess[es] that [are] constantly mistagged and nobody is cleaning up, and I think realistically almost everybody searching for that character is fine with either form".

lafcadio said:
To quote another staff member: "I am personally of the opinion that characters with multiple forms should all imply a base form of the character", and tagging projects like these often create "huge mess[es] that [are] constantly mistagged and nobody is cleaning up, and I think realistically almost everybody searching for that character is fine with either form".

Please! I understand wanting to be able to seaech for both forms together, but both forms should then have their own tags and imply a base tag that covers every form of the character. Asriel_dreemurr is constantly filled with mistags and I'm sure other multi form character tags are too.

cloudpie said:
Please! I understand wanting to be able to seaech for both forms together, but both forms should then have their own tags and imply a base tag that covers every form of the character. Asriel_dreemurr is constantly filled with mistags and I'm sure other multi form character tags are too.

As long as people will actually use the different form tags correctly. E.g. it wouldn't make much sense to establish a modern_sonic tag if people are only going to tag sonic_the_hedgehog for the modern version, leaving sonic_the_hedgehog to be the defacto Modern Sonic tag and create the same problem we're trying to avoid. In cases like this, it may be better to remove the existing classic_sonic -> sonic_the_hedgehog implication, and create a new tag as the base that both of those tags implicate (and the same for Tails).

The fact that there are 3 different Amy's confuse me. The nega characters confuse me sometimes.
Like...Classic Amy & Rosy the Rascal aren't the same person.
Yet Rosy looks like Classic Amy but she's clearly duranged...

Who thought making nega-characters look like the main characters or their classic counterpart was a good idea?

The tag implication classic_amy_rose -> amy_rose (forum #371213) has been rejected by @slyroon.