The bulk update request #4935 is active.

Reason: We've done biological relatives, we've done adopted relatives, now this should hopefully be the last of the Great Loreification.

I think these are all the existing aliases. There do not appear to be any existing implications. Some of these aliases are strangely haphazard, especially the last two. (stepsisters doesn't even have any posts.)

EDIT: The bulk update request #4935 (forum #367049) has been approved by @gattonero2001.

The bulk update request #4935 (forum #367049) has been approved by @gattonero2001.

The bulk update request #4936 is active.

Reason: Part 2: the main aliases.

EDIT: The bulk update request #4936 (forum #367052) has been approved by @gattonero2001.

The bulk update request #4937 is active.

Reason: Part 3: why

EDIT: The bulk update request #4937 (forum #367053) has been approved by @gattonero2001.

The bulk update request #4938 is active.

Reason: Part 4a: proposed new supplementary aliases.

Since the previous aliases were so spotty, I thought it best to redo them from the ground up instead of simply copying them. I tried to not leave random cases uncovered like the previous step-relative aliases, while not going completely overboard as in the infamous case of the biological relative aliases.

I also elected not to include any aliases for compound tags. This is something we could revisit in the future if it becomes necessary, but covering all cases would balloon this BUR to a silly size and I'm sure we're all sick of that by now. The only previously existing compound tag alias, step-mother_and_step-son, has been used twice in history (one of which was by klorpa) and the longest it remained on a post was three days.

EDIT: The bulk update request #4938 (forum #367054) has been approved by @gattonero2001.

The bulk update request #4939 is active.

create alias stepsiblings (0) -> stepsibling_(lore) (426)
create alias step_sibling (0) -> stepsibling_(lore) (426)
create alias step-sibling (0) -> stepsibling_(lore) (426)
create alias step_brothers (0) -> stepbrothers_(lore) (24)
create alias step-brothers (0) -> stepbrothers_(lore) (24)
create alias step_sisters (0) -> stepsisters_(lore) (0)
create alias step-sisters (0) -> stepsisters_(lore) (0)

Reason: Part 4b: the rest of the supplementary aliases.

EDIT: The bulk update request #4939 (forum #367055) has been approved by @gattonero2001.

wat8548 said:

change category *_(lore) (0) -> lore # missing

Reason: Part 3: why

The tags need to be added to a post before being used in a BUR. You can just add the relevant tags to a deleted post and then reverse the change, for example.

gattonero2001 said:
The tags need to be added to a post before being used in a BUR. You can just add the relevant tags to a deleted post and then reverse the change, for example.

It needs to be done by an admin. Regular users can't create lore tags, even in the general category.

The bulk update request #4941 is active.

Reason: Part 5: proposed new implication tree. (Woo, exactly 25 lines!)

I ran into an unexpected snag with this one. While looking at the existing umbrella tags - all of which have seen use, despite the lack of implications - I suddenly realised that we do not have any implications to or from parent_and_son or parent_and_daughter. Then I looked those tags up, and they have hundreds of uses each - again, despite having no implications. This presents a three-way dilemma:

• Should we declare all un-gendered parent with gendered offspring tags to be invalid, and nuke both the bio and step versions despite existing usage?
• Should we change the bio implication tree to match the step tags?
• Should we follow bio's lead and quietly pretend these tags don't exist?

My opinion is that we should go with option 2. Considering these tags have never been added automatically, they have amassed a quite impressive record of usage, which suggests there is a demand. So I incorporated them into the step-relative implication tree, and I'll make another BUR over on the Thread From Hell to sort the bio versions out.

The other interesting question here is whether we should make stepchild a valid tag. Technically, there is nothing stopping us. There is currently no umbrella tag for gender-neutral biological offspring because child is used to denote character age, and it is unlikely we will ever manage to shift that usage. But stepchild has no such issue hanging over its head. For consistency's sake, as well as the fact stepchild has 0 posts and no aliases, I decided not to.

EDIT: The bulk update request #4941 (forum #367058) has been approved by @gattonero2001.

gattonero2001 said:
The tags need to be added to a post before being used in a BUR. You can just add the relevant tags to a deleted post and then reverse the change, for example.

Approving part 2 should have the same effect of creating the tags, thus making part 3 work.

The bulk update request #4937 (forum #367053) has been approved by @gattonero2001.

The bulk update request #4936 (forum #367052) has been approved by @gattonero2001.

The bulk update request #4938 (forum #367054) has been approved by @gattonero2001.

The bulk update request #4939 (forum #367055) has been approved by @gattonero2001.

wat8548 said:
Approving part 2 should have the same effect of creating the tags, thus making part 3 work.

In this case, that would not have been a concern, but when a group of tags is in a very large number of posts, changing their category is extremely demanding in terms of server power and can cause the issues I mentioned elsewhere. Which is why it's better to always change the category while it affects 0 active posts as a habit.

faucet said:
It needs to be done by an admin. Regular users can't create lore tags, even in the general category.

In retrospect, that does make sense, but still unexpected :p

The bulk update request #4941 (forum #367058) has been approved by @gattonero2001.

I like how not a single one of these tags was above 100 posts before this thread, but now four of them are.

Implications: They Work.