Topic: Curvy Figure Alias BUR

Posted under Tag Alias and Implication Suggestions

dfY6C

Privileged

The bulk update request #586 is pending approval.

remove implication curvaceous (1193) -> voluptuous (3901)
create alias curves (0) -> curvy_figure (5480)
create alias curvy_anthro (0) -> curvy_figure (5480)
create alias curvy_body (0) -> curvy_figure (5480)
create alias curvy_female (0) -> curvy_figure (5480)
create alias curvy_gynomorph (0) -> curvy_figure (5480)
create alias curvy_herm (0) -> curvy_figure (5480)
create alias curvy_human (0) -> curvy_figure (5480)
create alias curvy_humanoid (0) -> curvy_figure (5480)
create alias curvy_intersex (0) -> curvy_figure (5480)
create alias curvy_male (0) -> curvy_figure (5480)
create alias curvy_andromorph (0) -> curvy_figure (5480)
create alias curvy_feral (0) -> curvy_figure (5480)

EDIT: This BUR is now complementary to alias #60378 (topic #889). I have edited this BUR to add the first line unimplication as one aspect of the transitive change I'm not sure about is whether both tags having the voluptuous implication would create a conflict for the approval system. This BUR should be approved before the alias to potentially account for this.

ORIGINAL REASON:

Aliasing curvaceous -> curvy_figure is the main goal of this BUR, but can only be done in post-approval.

curvaceous and curvy_figure are currently split tags used to describe the same thing and these system changes match e621, outside of curvy_feral, curvy_andromorph, and curvy_human which I added myself based on the existence of the other tags in this list. I need to unalias curvy -> curvaceous first so that I can alias curvaceous -> curvy_figure and curvy -> curvy_figure in a post-approval BUR.

If you all feel that aliasing curvy_X -> curvy_figure is too much, then perhaps we can implicate those to curvy_figure instead, but it should be known that curvy_figure is meant to be the catch-all/umbrella tag for these.

Updated

kalethOrebiter

Privileged

For future BUR, what you can do is a follow up section with/instead of a long description.

e.g.

[ section,expanded=Follow up ]
curvaceous -> curvy_figure
curvy -> curvy_figure
[ /section ]

That help people understand where you go, and it allows the BUR approver to keep track of the future changes.

Like, imagine it takes 2 months for the BUR to be approved, there's good chance that no one remember to do the follow up.

FlowerSylveon

Privileged

kalethorebiter said:
For future BUR, what you can do is a follow up section with/instead of a long description.

e.g.

[ section,expanded=Follow up ]
curvaceous -> curvy_figure
curvy -> curvy_figure
[ /section ]

That help people understand where you go, and it allows the BUR approver to keep track of the future changes.

Like, imagine it takes 2 months for the BUR to be approved, there's good chance that no one remember to do the follow up.

section works but i personally prefer doing [code] because stands out more