The bulk update request #445 is active.
remove implication baby_pokémon (0) -> pokémon (0)
remove implication pichu (2722) -> baby_pokémon (0)
remove implication cleffa (124) -> baby_pokémon (0)
remove implication igglybuff (126) -> baby_pokémon (0)
remove implication togepi (212) -> baby_pokémon (0)
remove implication tyrogue (118) -> baby_pokémon (0)
remove implication smoochum (119) -> baby_pokémon (0)
remove implication elekid (245) -> baby_pokémon (0)
remove implication magby (75) -> baby_pokémon (0)
remove implication azurill (165) -> baby_pokémon (0)
remove implication wynaut (92) -> baby_pokémon (0)
remove implication budew (92) -> baby_pokémon (0)
remove implication chingling (64) -> baby_pokémon (0)
remove implication bonsly (49) -> baby_pokémon (0)
remove implication mime_jr. (62) -> baby_pokémon (0)
remove implication happiny (82) -> baby_pokémon (0)
remove implication munchlax (124) -> baby_pokémon (0)
remove implication riolu (6326) -> baby_pokémon (0)
remove implication mantyke (60) -> baby_pokémon (0)
remove implication toxel (60) -> baby_pokémon (0)
remove implication erebebii (2) -> baby_pokémon (0)
remove implication pii (2) -> baby_pokémon (0)
remove implication beta_pichu (5) -> baby_pokémon (0)
remove implication mikon (5) -> baby_pokémon (0)
remove implication monja (9) -> baby_pokémon (0)
remove implication gyopin (2) -> baby_pokémon (0)
remove implication para_(pokémon_gold_beta) (0) -> baby_pokémon (0)
remove implication hina-zu (2) -> baby_pokémon (0)
remove implication ko-nya (21) -> baby_pokémon (0)
remove implication puchikon (3) -> baby_pokémon (0)
remove implication betobebii (2) -> baby_pokémon (0)
remove implication pudi (3) -> baby_pokémon (0)
remove implication bariri-na (1) -> baby_pokémon (0)
remove alias pokémon_baby (0) -> baby_pokémon (0)
remove alias baby_pokemon (0) -> baby_pokémon (0)
remove alias pokemon_baby (0) -> baby_pokémon (0)
Reason: The baby_pokémon tag doesn't work with TWYS, as it's a classification from lore information and says nothing about the age or appearance of the pokémon. Making it a lore tag would create a slippery slope with all the other pokémon classifications, as well as impact other franchises, so it's instead aliased away like ghost_pokémon and others are.
Step 1 is to remove the implications and aliases currently associated with the tag, so step 2 can then properly alias them away:
alias pokémon_baby -> pokémon alias baby_pokemon -> pokémon alias pokemon_baby -> pokémon alias baby_pokémon -> pokémon
EDIT: The bulk update request #445 (forum #300608) has been approved by @Millcore.
Updated by auto moderator