Topic: [APPROVED] The Alcremie Issue

Posted under Tag Alias and Implication Suggestions

The bulk update request #9344 is active.

create implication vanilla_cream_alcremie (323) -> alcremie (535)
create implication ruby_cream_alcremie (37) -> alcremie (535)
create implication matcha_cream_alcremie (12) -> alcremie (535)
create implication mint_cream_alcremie (31) -> alcremie (535)
create implication lemon_cream_alcremie (8) -> alcremie (535)
create implication salted_cream_alcremie (21) -> alcremie (535)
create implication ruby_swirl_alcremie (39) -> alcremie (535)
create implication caramel_swirl_alcremie (19) -> alcremie (535)
create implication rainbow_swirl_alcremie (6) -> alcremie (535)
create implication strawberry_sweet_alcremie (391) -> alcremie (535)
create implication berry_sweet_alcremie (43) -> alcremie (535)
create implication love_sweet_alcremie (50) -> alcremie (535)
create implication star_sweet_alcremie (13) -> alcremie (535)
create implication clover_sweet_alcremie (17) -> alcremie (535)
create implication flower_sweet_alcremie (7) -> alcremie (535)
create implication ribbon_sweet_alcremie (22) -> alcremie (535)

Reason:
Right now we have individual species tags for the alternate forms of every pokemon that has them, except for the one with the highest amount: Alcremie (https://bulbapedia.bulbagarden.net/wiki/Alcremie_(Pok%C3%A9mon)#Form_data).

Alcremie has 70 total forms if you count the 7 shiny versions. These are combinatory, being created from 7 different sweets and 9 different creams (plus its shiny form, which is sort of a 10th cream). These forms should be searchable, but if we went with an individual tag for every form we would have an absurd number of long and unwieldy tags such as strawberry_sweet_vanilla_cream_alcremie or flower_sweet_caramel_swirl_alcremie. We would also run into an issue with the shiny forms: we would have to break the rule of how we currently tag shiny pokemon (with just the pokemon's regular species tag plus shiny_pokemon) in order for the 7 different shiny forms to be searchable.

I propose that we instead just keep the two form elements separate, resulting in a much more manageable 17 form tags, two of which would be applied per Alcremie. So instead of alcremie strawberry_sweet_vanilla_cream_alcremie we would have alcremie strawberry_sweet_alcremie vanilla_cream_alcremie. This also solves the shiny problem, for example if you had a ribbon sweet shiny alcremie you would tag alcremie ribbon_sweet_alcremie shiny_pokemon.

Let me know your thoughts.

EDIT: The bulk update request #9344 (forum #420562) has been approved by @spe.

Updated by auto moderator

  • 1