The bulk update request #5934 is pending approval.

Reason: Stumbled across a post tagged with son_penetrating_mother and realized that such a tag in the general category violates TWYS. Going deeper, it seems like there are a LOT of tags like this, so I decided to alias them all to the appropriate lore tags. If you need lore for each character, you cannot use TWYS to state what the characters are doing to each other.

Also, parent_penetrating_duaghter is not a typo in the BUR, that's the actual tag that was created.

This is the first of three BURs, there are a total of 53 lines including a correction for the erroneous spelling noted above, this exceeds the 25-entry maximum of a BUR. This BUR will handle "parent" and "father". The second BUR will handle the spelling correction, "mother", and "child". The final BUR will handle "son" and "daughter"

The bulk update request #5935 is pending approval.

Reason: This is the second aforementioned BUR

The bulk update request #5936 is pending approval.

Reason: This is the third aforementioned BUR

Also, I can't find any info on this error I see in these BURs: "duplicate of has blocking transitive relationships, cannot be applied through bur". Could someone please explain that to me?

atomicblaze21 said:
Also, I can't find any info on this error I see in these BURs: "duplicate of has blocking transitive relationships, cannot be applied through bur". Could someone please explain that to me?

I assume it's blocked by other pending AIBURs like this one

snpthecat said:
I assume it's blocked by other pending AIBURs like this one

Good catch. Didn't realize that pending BURs could cause issues with new ones. Interestingly enough, one of the admins rejected that BUR you linked soon after you posted this reply, not likely a coincidence.

After looking at it in more detail, you have
create alias parent_penetrating_duaghter (1) -> parent_and_daughter_(lore) (11973) in the first BUR but then you have
mass update parent_penetrating_duaghter -> parent_penetrating_daughter in the second BUR. I assume it would be best to swap the BUR they're in, and have the correct spelling aliased to parent_and_daughter_(lore)

snpthecat said:
I assume it's blocked by other pending AIBURs like this one

BURs don't generate conflicts, but standalone alias/implication requests do. In this case, the responsible thread appears to be topic #40641.

snpthecat said:
After looking at it in more detail, you have
create alias parent_penetrating_duaghter (1) -> parent_and_daughter_(lore) (11973) in the first BUR but then you have
mass update parent_penetrating_duaghter -> parent_penetrating_daughter in the second BUR. I assume it would be best to swap the BUR they're in, and have the correct spelling aliased to parent_and_daughter_(lore)

I decided to change the spelling in a separate BUR than the one that would have the alias, I though I was gonna run into the "transitive properties" error since I didn't know that that error is caused by pending BURs. I could have re-ordered it to have the Parent prefix be in one of the later BURs thus allowing a spelling correction before an alias assignment. However, I'm pretty sure that the thing with aliases is that the alias tag is still able to be renamed just like a canonical tag.

Okay, I'd forgotten I'd made these, so I'm bumping this back up with a couple changes, as well as updated issues with new transitive relationships:

I removed the mass update parent_penetrating_duaghter -> parent_penetrating_daughter in the second BUR and replaced it with adding create alias parent_penetrating_daughter -> parent_and_daughter_(lore) to the first BUR. This should rectify both the original issue as well as the spelling issue.

The alias create alias father_penetrating_son -> father_and_son_(lore) has been blocked by topic #44908, which has overwhelmingly negative feedback.

There is a new issue with aliasing child_swap, son_swap, and daughter_swap, which were added to new implications as shown in topic #32151. The problem here is that parent/child relationships aren't reliably TWYS and should be aliased to their respective lore tags.