Posted under Tag Alias and Implication Suggestions
The tag alias #81940 minimal_clothing -> skimpy has been rejected.
Reason: Basically same as barely_clothed, which is already aliased.
EDIT: The tag alias minimal_clothing -> skimpy (forum #482771) has been rejected by @FinallyLostIt.
Updated by auto moderator
these are not quite the same thing, 'skimpy' emphasizes a characters sexuality were as 'minimal clothing' does not require that. skimpy also does not exclude fully clothed characters, fullbody suits may count as skimpy but not necessarily minimally clothed.
Apparently, the barely_clothed alias was approved even when the original request was doubtful if it was the right choice.
I'm all for sending both tags to clothed instead, if skimpy doesn't really describe all instances of minimal clothing.
The tag alias minimal_clothing -> skimpy (forum #482771) has been rejected by @FinallyLostIt.
The bulk update request #13411 is pending approval.
remove alias barely_clothed (0) -> skimpy (71534)
create alias minimal_clothing (51) -> clothed (1420836)
Reason: Alrighty then.
After the feedback, the takeaway is that both tags leave the coverage and purpose of the clothes vague, and thus do not reliably correspond to existing tags relating to revealingness. All they suggest is little clothing.
Tried to add
alias barely_clothed -> clothed
to the script, but got an error. I suppose it has to be unaliased first?
finallylostit said:
Tried to addalias barely_clothed -> clothedto the script, but got an error. I suppose it has to be unaliased first?
Yes, this is a limitation of BURs. If you have a tag with many aliases/implications attached to it, you may either unalias everything through a BUR first and then submit another one aliasing them after (like how you are doing it here) or submit a plain alias request instead (which can automatically move these attached tags).
