The bulk update request #8327 is pending approval.

create alias naval_vore (0) -> navel_vore (75) # has blocking transitive relationships, cannot be applied through BUR
create alias naval_stimulation (0) -> navel_play (202)
create alias naval_tuft (9) -> navel_tuft (379)
create alias unusual_naval (0) -> unusual_navel (512)
create alias detailed_naval (0) -> detailed_navel (800)
create alias naval_outline (0) -> navel_outline (2811)
create alias naval_cutout (0) -> navel_cutout (252)

Reason: Checking for a naval_attire or naval_uniform I spotted a couple typo tags. A couple are empty, but have wikis and no aliases. A couple have posts in them, but no wikis.
naval_gem has an impending alias already.

The bulk update request #8331 is pending approval.

remove implication naval_vore (0) -> vore (70295)
create alias naval_gem (7) -> belly_gem (153)
create alias navel_stimulation (0) -> navel_play (202)

Reason: The first is to avoid above BURs BTR and the second is the location of where navel_gem went

I don't see why naval_stimulation should alias to navel_vore. At first glance it should probably alias to navel_stimulation, but that tag is empty, so i wonder if it should be kept at all. (Potential destination could be navel_play, or be left untouched)

Aliasing navel stimulation to navel play, stimulation type tags are pretty rare and this is not the rare case where it is appropriate

snpthecat said:
The bulk update request #8331 is pending approval.

remove implication naval_vore (0) -> vore (70295)
create alias naval_gem (7) -> belly_gem (153)
create alias navel_stimulation (0) -> navel_play (202)
I don't see why naval_stimulation should alias to navel_vore. At first glance it should probably alias to navel_stimulation, but that tag is empty, so i wonder if it should be kept at all. (Potential destination could be navel_play, or be left untouched)

I was eepy and made a mistake.