Imply Xianyun -> Cloud Retainer

BUR #21825 has been rejected.

create implication xianyun_(genshin_impact) -> cloud_retainer_(genshin_impact)

Her human form's playable name.

This feels backwards. I had to search cloud_retainer_(genshin_impact) -xianyun_(genshin_impact) to figure out what the difference between these two tags even is (Cloud Retainer is her bird form and Xianyun is her human form). I'm going to guess that her human form is going to end up with significantly more fanart than her bird form.

The reason it feels backwards is because I believe the crane form is her actual form, and the human/playable form is just a facade, unlike most cases outside of Genshin where it'd usually be the other way around, where the animal form is an alternate form of the human. So from a logical standpoint it should be in the order the BUR does it (name-wise too, her actual name is Cloud Retainer, not Xianyun which is just a fake name for her human/playable form like this implies), even though it feels backwards.
Yeah this is a bit of a weird case.

I'm pretty sure this is not the first case where a character has an animal form and a human form, and the animal form is the true form, but the human form is what gets most of the attention.

The issue is when this character gets a few thousand posts and nearly all of them are tagged both Xianyun and Cloud Retainer and you can't tell which tag is which because they're 99% identical. Then the wiki has to explain that Xianyun is the tag for her human form, and Cloud Retainer is the umbrella tag for both her human form and bird form, but her bird form doesn't actually have a tag, instead you have to search cloud_retainer_(genshin_impact) -xianyun_(genshin_impact) to find it.

In other words, instead of having tags for both the human form and the bird form, and having an umbrella tag for both, or just letting the human form serve as the umbrella tag (as we do with Yae Miko and Yae Miko (fox)), instead we have tags for human and human+bird, and to find bird you have to search "human+bird - human".

In that case do you suggest keeping cloud retainer (genshin impact) as an umbrella for both forms, and creating a cloud retainer (bird) (genshin impact) or similar tag specifically for the bird form?

We should simply keep them separate. Xianyun for her playable, humanoid version, and Cloud Retainer for her bird form. Implication would, like evazion said, pollute the Cloud Retainer tag to the point that it's unusable.

BUR #22335 has been approved by @nonamethanks.

create implication cloud_retainer_(genshin_impact) -> xianyun_(genshin_impact)

I don't think we need umbrella tags for every character that has an alternate form or two. Yae Miko (fox) implicates Yae Miko and that's it. We don't need Yae Miko (human). The same should go for the birb.

As it stands, nearly every image of Xianyun is already tagged Cloud Retainer and there multiple people who go through and tag Cloud Retainer on Xianyun. We could either reverse the BUR presented or start removing Cloud Retainer from Xianyun.

I prefer the original BUR because her name IS Cloud Retainer, but I ultimately don't mind too much either way.

This bulk update request is pending automatic rejection in 5 days.

winterless said:

We should simply keep them separate. Xianyun for her playable, humanoid version, and Cloud Retainer for her bird form. Implication would, like evazion said, pollute the Cloud Retainer tag to the point that it's unusable.

Shouldn't -bird search tag solve the problem? Xianyun is her human alias, not a separate character, I don't see why it should be separate from cloud_retainer.

edit: CR in her animal form should have bird tag, while in human form should have Xianyun tag.

This bulk update request has been rejected because it was not approved within 45 days.

The bulk update request #21825 (forum #262470) has been rejected by @DanbooruBot.

This bulk update request has been rejected because it was not approved within 45 days.

The bulk update request #22335 (forum #264715) has been rejected by @DanbooruBot.

The bulk update request #22335 (forum #264715) has been approved by @nonamethanks.