Topic: Tail Wrapping Bur

The bulk update request #12239 is pending approval.

create alias tail_around_another (140) -> tail_coil (7901)
create alias tail_around_partner (1276) -> tail_coil (7901)
create alias wrapping_tails (41) -> tail_coil (7901)
create alias tail_wrappings (0) -> tail_wraps (4562)
create alias tail_wrapping (298) -> invalid_tag (0)
create alias wrapped_tail (272) -> invalid_tag (0)

Reason: An attempt to implement https://e621.net/forum_topics/40936, as the topic recieved no response and no BUR was made for it.

Actual usage of tail_wrapping and wrapped_tail is a mixture of tail_around_partner, tail_coil, and tail_wraps, but should probably either be aliased to tail_wraps or invalidated due to being ambiguous.

wrapping_tails, tail_around_another, and tail_around_partner are entirely used in cases where tail_coil fits.

tail_wrappings is entirely empty, and could either be dropped or aliased to tail_wraps.

-1 to the aliases to invalid_tag. If there are valid tags it could mean, it's better to disambiguate than alias to that black hole of a tag

Also is tail_coil for when the tail is coiled around another character, or is it applicable for self coiling

snpthecat said:
-1 to the aliases to invalid_tag. If there are valid tags it could mean, it's better to disambiguate than alias to that black hole of a tag

Fair enough

Also is tail_coil for when the tail is coiled around another character, or is it applicable for self coiling

As I understand it, tail_coil is intended for coiling around another, though I don't see why self-coiling wouldn't also fit under it.

The bulk update request #12240 is pending approval.

create alias tail_around_partner (1276) -> tail_around_another (140)
create implication tail_around_another (140) -> tail_coil (7901)
create implication entwined_tails (4828) -> tail_around_another (140)
remove implication entwined_tails (4828) -> tail_coil (7901)
create implication tail_around_self (12) -> tail_coil (7901)
create implication tail_around_own_tail (0) -> tail_around_self (12)
create alias wrapping_tails (41) -> entwined_tails (4828)
create alias tail_wrappings (0) -> tail_wraps (4562)
create alias tail_wrapping (298) -> tail_wrapping_(disambiguation) (0)
create alias wrapped_tail (272) -> tail_wrapping_(disambiguation) (0)
change category tail_wrapping_(disambiguation) (0) -> invalid

Reason: v4, per SNPtheCat's and Waydence's comments.

isawoo1234 said:

As I understand it, tail_coil is intended for coiling around another, though I don't see why self-coiling wouldn't also fit under it.

If it handles both, we should have 2 sub tags, tail around another for when it's coiled around another character, and tail around self for when it's coiled around themselves. Both tags should then imply tail coil.

isawoo1234 said:
create alias tail_around_another (131) -> tail_coil (7483)
create alias tail_around_partner (1180) -> tail_coil (7483)
create alias wrapping_tails (38) -> tail_coil (7483)

Definitely should be implications. Something like this:

imply tail_around_partner -> tail_around_another 
imply tail_around_another -> tail_coil
imply wrapping_tails -> entwined_tails

wrapping_tails has been pretty much entirely used as substitute for entwined_tails.

waydence said:
Definitely should be implications. Something like this:

imply tail_around_partner -> tail_around_another 
imply tail_around_another -> tail_coil
imply wrapping_tails -> entwined_tails

wrapping_tails has been pretty much entirely used as substitute for entwined_tails.

Do we need around partner as a distinct tag from around another? How would partner be twys and/or meaningful enough to be a separate tag?

waydence said:
Definitely should be implications. Something like this:

imply tail_around_partner -> tail_around_another 
imply tail_around_another -> tail_coil
imply wrapping_tails -> entwined_tails

wrapping_tails has been pretty much entirely used as substitute for entwined_tails.

why have wrapping_tails imply entwined_tails, rather than aliasing, then?

Speaking of entwined tails, should it also have subtags for when the tail is entwined around their own tail(s) and when its around someone else's tail?

snpthecat said:
Do we need around partner as a distinct tag from around another? How would partner be twys and/or meaningful enough to be a separate tag?

Fair enough, we do not.

isawoo1234 said:
why have wrapping_tails imply entwined_tails, rather than aliasing, then?

Forgot to change it. The final edit should look like this (you can edit BURs btw):

alias tail_around_partner -> tail_around_another 
imply tail_around_another -> tail_coil
alias wrapping_tails -> entwined_tails

waydence said:
Fair enough, we do not.
Forgot to change it. The final edit should look like this (you can edit BURs btw):

alias tail_around_partner -> tail_around_another 
imply tail_around_another -> tail_coil
alias wrapping_tails -> entwined_tails

Edited 12240

create implication tail_around_anothers_tail (0) -> tail_coil (7486)

is redundant, will imply through entwined tails

Also if anyone asks about tail around own tail, here are some examples: post #5170147 post #3247531 (i guess there's also the way of tying our tail into a knot, would that count?)

Also I just realised tail around another's tail is exactly equivalent to entwined tails if we go by the wiki. The question is whether we should open it up to self coiling tails but I suspect the answer will be a no

here's what I would put for the BUR to create the tail_coil implication tree:

alias tail_around_partner -> tail_around_another
imply tail_around_another -> tail_coil
imply entwined_tails -> tail_around_another
unimply entwined_tails -> tail_coil
imply tail_around_self -> tail_coil
imply tail_around_own_tail -> tail_around_self

snpthecat said:
is redundant, will imply through entwined tails

Also if anyone asks about tail around own tail, here are some examples: post #5170147 post #3247531 (i guess there's also the way of tying our tail into a knot, would that count?)

Also I just realised tail around another's tail is exactly equivalent to entwined tails if we go by the wiki. The question is whether we should open it up to self coiling tails but I suspect the answer will be a no

here's what I would put for the BUR to create the tail_coil implication tree:

alias tail_around_partner -> tail_around_another
imply tail_around_another -> tail_coil
imply entwined_tails -> tail_around_another
unimply entwined_tails -> tail_coil
imply tail_around_self -> tail_coil
imply tail_around_own_tail -> tail_around_self

Thanks, edited.