Topic: [REJECTED] Plusterin livly tags

Posted under Tag Alias and Implication Suggestions

The bulk update request #3017 has been rejected.

create implication p1_variant_livly (3) -> livly_(species) (29)
create implication p2_variant_livly (1) -> livly_(species) (29)
create implication p3_variant_livly (0) -> livly_(species) (29)

Reason: Plusterin (p1 up to p3) livlies have aesthetic variations from their original species, but are still the same species. I think they should be tagged the same way as shiny pokémon.

EDIT: The bulk update request #3017 (forum #341922) has been rejected by @DimoretPinel.

Updated by auto moderator

dimoretpinel said:
I’m not sure if we should generalize the tag so much? A good example of the variations is post #3488678: personally, I’d keep the separation between Plusterin grades.

Imply, as in you'd still have the p# tags. You aren't losing anything in searchability.

furrin_gok said:
Imply, as in you'd still have the p# tags. You aren't losing anything in searchability.

Oh my, I read the previous comment too fast then. My bad.

Your idea sounds good, but I can’t edit this BUR to fit the better implications, which means I’ll have to make an entirely new one. Is it possible to discard/delete it so mods don’t mistakenly approve the wrong BUR?

Edit: I found out on my own, no need to answer! Also, thank you for the implications suggestion.

Updated

dimoretpinel said:
Oh my, I read the previous comment too fast then. My bad.

Your idea sounds good, but I can’t edit this BUR to fit the better implications, which means I’ll have to make an entirely new one. Is it possible to discard/delete it so mods don’t mistakenly approve the wrong BUR?

Edit: I found out on my own, no need to answer! Also, thank you for the implications suggestion.

You can edit the BUR, through the same location you rejected it through: The BUR page itself, accessed through the bulk update request #3017 link on the opening post above.

dimoretpinel said:
Oh shoot. Too late for this BUR (now moved to topic #34915), but thanks a lot for the information! I will do this next time.

Hey, don't worry, it's a learning experience. Might wanna link this thread in that one (and vice-versa) as a "see also" so people can check and compare discussion.

  • 1