BUR #2908 has been rejected.
create implication akali_(redesign) -> akali
create implication akali_(redesign) -> redesign
Subsets.
EDIT: The bulk update request #2908 (forum #168391) has been rejected by @evazion.
Updated by DanbooruBot
Posted under Tags
BUR #2908 has been rejected.
create implication akali_(redesign) -> akali
create implication akali_(redesign) -> redesign
Subsets.
EDIT: The bulk update request #2908 (forum #168391) has been rejected by @evazion.
Updated by DanbooruBot
Currently akali_(redesign) needs some gardening. Akali's skins have all been changed to look differently in her redesigned version. To name an example, the Blood Moon Akali skin is different: her old version with the long ponytail, and the new one, which is shorter and raised.
I'd argue that we should do the opposite and start tagging the old Akali as akali_(old or similar, because as time goes on there will be more redesigned Akali art than otherwise.
I don't think redesign is a good tag. It doesn't have a definition and it's not commonly used for other character redesigns, like characters from Final Fantasy VII Remake or the Resident Evil 2 remake. It's mainly just used for random mecha posts. Also, we don't imply chartags to gentags.
The bulk update request #2908 (forum #168391) has been rejected by @evazion.
We don't implicate any of her other forms to Akali. We don't imply skins for any other League of Legends character either. Nor do we do it for other copyrights like Overwatch or Azur Lane. If we want to start implying skins, we should do it consistently. (Yes, you could technically say this is a redesign, not a skin, but it's the same difference).