create implication single_detached_sleeve -> single_sleeve
The former could be used as a more specific variation of the latter
The tag implication single_detached_sleeve -> single_sleeve has been rejected.
Updated by DanbooruBot
Posted under Tags
create implication single_detached_sleeve -> single_sleeve
The former could be used as a more specific variation of the latter
The tag implication single_detached_sleeve -> single_sleeve has been rejected.
Updated by DanbooruBot
What about if they have two sleeves, one of which is detached whilst the other isn't eg post #1609977?
Huh. Good question. Not sure how those would be classified beyond the more generic asymmetrical_sleeves
This reminds me about situation with single_elbow_glove and single_glove, see topic #7066 and topic #9269 for details.
Similar to that situation, I think that not having this implication is more convenient. This way we can search for both options:
- if character has only one sleeve and it is detached (post #2766199, post #2789480), then it would be tagged with both single_detached_sleeve and single_sleeve.
- if character has both sleeve and one of them is detached (post #1609977, post #2733755), then it would be tagged with single_detached_sleeve but not single_sleeve.
Updated
Agreed with MyrMindservant. Considering that single detached sleeve only has 86 posts, it should be no trouble to tag single sleeve manually.