Topic: *_transformation (2/2)

Posted under Tag Alias and Implication Suggestions

The bulk update request #12935 is pending approval.

create implication alioramus (6) -> tyrannosaurid (8209)
create implication nanotyrannus (4) -> tyrannosaurid (8209)
remove implication guanlong (21) -> tyrannosauroid (8357)
remove implication kileskus (1) -> tyrannosauroid (8357)
remove implication proceratosaurus (3) -> tyrannosauroid (8357)
remove implication yutyrannus (84) -> tyrannosauroid (8357)
create implication proceratosaurid (1) -> tyrannosauroid (8357)
create implication proceratosaurus (3) -> proceratosaurid (1)
create implication guanlong (21) -> proceratosaurid (1)
create implication kileskus (1) -> proceratosaurid (1)
create implication yutyrannus (84) -> proceratosaurid (1)
create implication sinotyrannus (1) -> proceratosaurid (1)
create implication leptorhynchos (1) -> caenagnathid (23)

Reason: Missing implications found when reviewing tag_implications-2025-12-25 DB dump.

Also alias nullo_transformation and null_transformation because it's literally the same thing.

greycat8 said:
The bulk update request #12935 is pending approval.

create implication alioramus (6) -> tyrannosaurid (8209)
create implication nanotyrannus (4) -> tyrannosaurid (8209)
remove implication guanlong (21) -> tyrannosauroid (8357)
remove implication kileskus (1) -> tyrannosauroid (8357)
remove implication proceratosaurus (3) -> tyrannosauroid (8357)
remove implication yutyrannus (84) -> tyrannosauroid (8357)
create implication proceratosaurid (1) -> tyrannosauroid (8357)
create implication proceratosaurus (3) -> proceratosaurid (1)
create implication guanlong (21) -> proceratosaurid (1)
create implication kileskus (1) -> proceratosaurid (1)
create implication yutyrannus (84) -> proceratosaurid (1)
create implication sinotyrannus (1) -> proceratosaurid (1)
create implication leptorhynchos (1) -> caenagnathid (23)

Reason: Missing implications found when reviewing tag_implications-2025-12-25 DB dump.

Also alias nullo_transformation and null_transformation because it's literally the same thing.

Damn, i just realized there is so much more i missed than what i found.

Also clone_transformation probably should be aliased to twinning.

Watsit

Privileged

You can add multiple related BURs to the same thread by providing the forum topic ID to the BUR. That helps keep discussions together instead of being split across multiple threads. Also to repeat here, topic #60952 handles some of these tags already.

In this case consensual_tranformation should be aliased away since consent is assumed by default. Tags like self_transformation and intentional_self_transformation are problematic by TWYS, since you can't always see the cause, let alone see that it's intentional, without subjective inference that people can disagree on.

transformation_by_fictional_prop also seems unnecessarily specific, and "fictional prop" is a rather vague term given that the image is already depicting a fictional scenario. Any "prop" in an image is fictional, making the distinction from transformation_by_item seem arbitrary.

demi_transformation is also rather confusing. "involving humans transforming, with skin and other human features intact, in a similar fashion to beast_boy", but people unfamiliar with Beast Boy won't have a very clear understanding. There aren't many beast_boy transformation posts either, and a number don't have "skin and other human features intact" as the wiki suggests. The tag is on posts like
post #5414660 post #5503428 post #5733113
which is typical mid_transformation stuff, and given that there are creatures that have skin and other human features that humans can transform into, seems like the tag is rather arbitrary (does keeping humanoid hands and feet count as "human features"?). It would be better to tag that kind of animal depiction separate from transformation, so it can also apply to non-transformation posts that still show that kind of creature; as it is, there are posts like
post #5343328
vs
post #4733638
that I think would be worth separating.

Transformation tags really need more individualized discussion since some tags may be fine while others need some discussion, and others need to go away, which makes BURs with a lot of tags difficult to handle.

Original page: https://e621.net/forum_topics/61285?page=1