Standardizing tag names for skins

The bulk update request #14646 (forum #231277) has been rejected by @DanbooruBot.

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

The bulk update request #14648 (forum #231284) has been rejected by @DanbooruBot.

Since these went to auto rejection, is it safe to assume that we're keeping Apex/OW/LoL skin tags as is? In the time since the BUR was set up, I made a few new Apex skin tags for previously untagged skins in the new/rejected format for future proofing and idk if I should switch those to the original format just yet.

Just to give my opinion, as I downvoted the BUR.
I don't really see the sense in this change, if these are the correct names the game uses. I don't care too much about APEX, but for something like LoL such a standardization only brings an unneccessary long tag name. It also doesnt serve any purpose, as it doesnt make tag searching easier, as you can find the tag easily with our correction system by writing the character name. And in the case for LoL at least, it pretty much goes against the own games character naming. It wouldnt make sense for every tag and every character.

For your leblanc example: It is one of hundred characters with only a few images for every skin. Someone who wouldnt know the skins wouldnt search for them anyway and would just ignore them. How does changing the naming order help them in any way? If they want to tag an image, they could simply check the characters wiki, which is more helpful than the search Suggestion. Someone who is looking for another specific leblanc would ignore the skintags anyway. Adding (League of Legends) to the skin names doesnt Seem helpful in these cases.
You would possibly pollute the search suggestions even more, because the name gets unneccessary long.

if the same is applicable for APEX, then I don't see how it's necessary or useful, so I support leaving the naming as it is right now.

Nacha said:

if the same is applicable for APEX, then I don't see how it's necessary or useful, so I support leaving the naming as it is right now.

Gonna quote my own previous post from forum #189019 regarding Apex and Overwatch:

I don't play LoL so I'm not familiar with how their skin naming conventions are (which is why I mentioned I'd leave anything regarding that franchise to anyone more knowledgeable in it)

In Apex's case, the character's original name isn't even part of the skin names. You scroll down a skin select menu that only has the skin's names. So using Wattson for example, the list would look like this:

• Cyber Punked
• Haute Drop
• Kawaii Voltage
• Wired for Speed

The Apex wiki follows the same convention, the skins don't have their own pages, they're simply listed out with images on the character's page (see Wattson's page here). It's been a while since I last played Overwatch but I believe they treat their skins the same way.

League is a copyright I personally don't care for, so I'll leave any decision from the admins regarding that alone, but in the case of Apex and Overwatch their skin naming isn't very different from gachas where the outfit is named without the character's name being part of it. Vocaloid alts seem to generally also use the costumename_charname format so LoL wouldn't be alone in that if the other two were changed.

BUR #15758 has been approved by @nonamethanks.

Since it's been almost 2 weeks since the BUR rejection, I'm gonna assume we'll be keeping the original format and switch these back. These are new skin tags that were made in the proposed format for futureproofing while the BURs were running (and since I figured it'd be easier to switch these back to the old format in the case of a rejection than trying to hunt them down and switch them to the new format if it passed)

Gonna approve this last one for the sake of consistency.

The bulk update request #15758 (forum #236098) has been approved by @nonamethanks.