Topic: [CANCELLED] Ultimate Pokémon BUR

The bulk update request #4272 has been rejected.

create implication walking_wake (238) -> ancient_pokemon (2000)
create implication walking_wake (238) -> generation_9_pokemon (24810)
create implication iron_leaves (46) -> future_pokemon (1080)
create implication iron_leaves (46) -> generation_9_pokemon (24810)
create implication okidogi (198) -> generation_9_pokemon (24810)
create implication munkidori (40) -> generation_9_pokemon (24810)
create implication fezandipiti (80) -> generation_9_pokemon (24810)
create implication ogerpon (391) -> legendary_pokemon (68387)
create implication ogerpon (391) -> generation_9_pokemon (24810)
create implication terapagos (31) -> legendary_pokemon (68387)
create implication terapagos (31) -> generation_9_pokemon (24810)

Reason: These Pokémon were revealed in the Pokémon Presents on Feb 27, 2023

Edit: I decided to have all my Tag Alias and Implication Suggestions on this BUR
Index

New Gen 9 Pokémon

EDIT: The bulk update request #4272 (forum #359065) has been rejected by @JoaoBaiao777.

The bulk update request #4345 has been rejected.

create implication limited_build_koraidon (195) -> koraidon (1168)
remove implication sprinting_build_koraidon (5) -> koraidon (1168)
remove implication swimming_build_koraidon (0) -> koraidon (1168)
remove implication gliding_build_koraidon (2) -> koraidon (1168)
create implication apex_build_koraidon (927) -> koraidon (1168)
create alias koraidon_(limited_build) (0) -> limited_build_koraidon (195)
create alias koraidon_(apex_build) (0) -> apex_build_koraidon (927)
create implication low-power_mode_miraidon (107) -> miraidon (736)
remove implication drive_mode_miraidon (8) -> miraidon (736)
remove implication aquatic_mode_miraidon (0) -> miraidon (736)
remove implication glide_mode_miraidon (1) -> miraidon (736)
create implication ultimate_mode_miraidon (584) -> miraidon (736)
create alias miraidon_(low-power_mode) (0) -> low-power_mode_miraidon (107)
create alias miraidon_(ultimate_mode) (0) -> ultimate_mode_miraidon (584)

Reason: Koraidon and Miraidon can enter one of three different forms when they travel the Paldea region and two forms based on how much power they have. They can change their forms to better suit what they are doing or what terrain they are traveling over.

I had tried to request Koraidon's and Miraidon's three different forms to alias Koraidon's Limited Build and Miraidon's Low-Power Mode so I had to request to unimplicate them first

Bulbapedia

create alias sprinting_build_koraidon -> limited_build_koraidon # duplicate of has blocking transitive relationships, cannot be applied through BUR
create alias swimming_build_koraidon -> limited_build_koraidon # duplicate of has blocking transitive relationships, cannot be applied through BUR
create alias gliding_build_koraidon -> limited_build_koraidon # duplicate of has blocking transitive relationships, cannot be applied through BUR
create alias drive_mode_miraidon -> low-power_mode_miraidon # duplicate of has blocking transitive relationships, cannot be applied through BUR
create alias aquatic_mode_miraidon -> low-power_mode_miraidon # duplicate of has blocking transitive relationships, cannot be applied through BUR
create alias glide_mode_miraidon -> low-power_mode_miraidon # duplicate of has blocking transitive relationships, cannot be applied through BUR

Koraidon & Miraidon

EDIT: The bulk update request #4345 (forum #359809) has been rejected by @JoaoBaiao777.

The bulk update request #4346 has been rejected.

Reason: Alolan forms were introduced in Generation 7

Alolan Forms

EDIT: The bulk update request #4346 (forum #359810) has been rejected by @JoaoBaiao777.

The bulk update request #4347 has been rejected.

Reason: All of the alolan forms are forms of Pokémon who were introduced in Generation 1

EDIT: The bulk update request #4347 (forum #359811) has been rejected by @JoaoBaiao777.

The bulk update request #4348 has been rejected.

Reason: Galarian forms were introduced in Generation 8

EDIT: The bulk update request #4348 (forum #359813) has been rejected by @JoaoBaiao777.

The bulk update request #4348 (forum #359813) has been rejected by @JoaoBaiao777.

The bulk update request #4349 has been rejected.

Reason: Galarian forms are forms of Pokémon who were introduced in Generation 1, 2, 3 and 5

EDIT: The bulk update request #4349 (forum #359815) has been rejected by @JoaoBaiao777.

The bulk update request #4349 (forum #359815) has been rejected by @JoaoBaiao777.

The bulk update request #4350 has been rejected.

Reason: Galarian forms are forms of Pokémon who were introduced in Generation 1, 2, 3 and 5

EDIT: The bulk update request #4350 (forum #359818) has been rejected by @JoaoBaiao777.

The bulk update request #4351 has been rejected.

Reason: Galarian forms were introduced in Generation 8

EDIT: The bulk update request #4351 (forum #359819) has been rejected by @JoaoBaiao777.

The bulk update request #4351 (forum #359819) has been rejected by @JoaoBaiao777.

The bulk update request #4350 (forum #359818) has been rejected by @JoaoBaiao777.

The bulk update request #4352 has been rejected.

Reason: Galarian forms were introduced in Generation 8

Galarian Forms

EDIT: The bulk update request #4352 (forum #359824) has been rejected by @JoaoBaiao777.

The bulk update request #4353 has been rejected.

Reason: Galarian forms are forms of Pokémon who were introduced in Generation 1, 2, 3 and 5

EDIT: The bulk update request #4353 (forum #359825) has been rejected by @JoaoBaiao777.

The bulk update request #4354 has been rejected.

Reason: Hisuian forms are forms of Pokémon who were introduced in Generation 1, 2, 5, 6 and 7

EDIT: The bulk update request #4354 (forum #359826) has been rejected by @JoaoBaiao777.

The bulk update request #4354 (forum #359826) has been rejected by @JoaoBaiao777.

The bulk update request #4355 has been rejected.

Reason: Hisuian forms were introduced in Generation 8

Hisuian Forms

EDIT: The bulk update request #4355 (forum #359828) has been rejected by @JoaoBaiao777.

The bulk update request #4356 has been rejected.

Reason: Hisuian forms are forms of Pokémon who were introduced in Generation 1, 2, 5, 6 and 7

EDIT: The bulk update request #4356 (forum #359829) has been rejected by @JoaoBaiao777.

The bulk update request #4357 has been rejected.

create implication paldean_tauros (69) -> generation_9_pokemon (24810)
create implication paldean_wooper (128) -> generation_9_pokemon (24810)

Reason: Paldean forms were introduced in Generation 9

Paldean Forms

EDIT: The bulk update request #4357 (forum #359830) has been rejected by @JoaoBaiao777.

The bulk update request #4358 has been rejected.

create implication paldean_tauros (69) -> generation_1_pokemon (174870)
create implication paldean_wooper (128) -> generation_2_pokemon (91068)

Reason: Paldean forms are forms of Pokémon who were introduced in Generation 1 and 2

EDIT: The bulk update request #4358 (forum #359831) has been rejected by @JoaoBaiao777.

The bulk update request #4359 has been rejected.

create implication mega_venusaur (62) -> generation_6_pokemon (88936)
create implication mega_charizard (1473) -> generation_6_pokemon (88936)
create implication mega_blastoise (62) -> generation_6_pokemon (88936)
create implication mega_beedrill (30) -> generation_6_pokemon (88936)
create implication mega_pidgeot (53) -> generation_6_pokemon (88936)
create implication mega_alakazam (19) -> generation_6_pokemon (88936)
create implication mega_slowbro (9) -> generation_6_pokemon (88936)
create implication mega_gengar (178) -> generation_6_pokemon (88936)
create implication mega_kangaskhan (140) -> generation_6_pokemon (88936)
create implication mega_pinsir (10) -> generation_6_pokemon (88936)
create implication mega_gyarados (17) -> generation_6_pokemon (88936)
create implication mega_aerodactyl (19) -> generation_6_pokemon (88936)
create implication mega_mewtwo (534) -> generation_6_pokemon (88936)

Reason: Mega Evolution was introduced in Generation 6

Mega Evolution Part 1

EDIT: The bulk update request #4359 (forum #359838) has been rejected by @JoaoBaiao777.

The bulk update request #4360 has been rejected.

create implication mega_venusaur (62) -> generation_1_pokemon (174870)
create implication mega_charizard (1473) -> generation_1_pokemon (174870)
create implication mega_blastoise (62) -> generation_1_pokemon (174870)
create implication mega_beedrill (30) -> generation_1_pokemon (174870)
create implication mega_pidgeot (53) -> generation_1_pokemon (174870)
create implication mega_alakazam (19) -> generation_1_pokemon (174870)
create implication mega_slowbro (9) -> generation_1_pokemon (174870)
create implication mega_gengar (178) -> generation_1_pokemon (174870)
create implication mega_kangaskhan (140) -> generation_1_pokemon (174870)
create implication mega_pinsir (10) -> generation_1_pokemon (174870)
create implication mega_gyarados (17) -> generation_1_pokemon (174870)
create implication mega_aerodactyl (19) -> generation_1_pokemon (174870)
create implication mega_mewtwo (534) -> generation_1_pokemon (174870)

Reason: All these Mega Evolutions are of Pokémon who were introduced in Generation 1

EDIT: The bulk update request #4360 (forum #359842) has been rejected by @JoaoBaiao777.

The bulk update request #4361 has been rejected.

create implication mega_aerodactyl (19) -> fossil_pokemon (3139)

Reason: Mega Aerodactyl is the Mega Evolution of Aerodactyl, which is a fossil Pokémon

Mega Evolution Part 2

EDIT: The bulk update request #4361 (forum #359846) has been rejected by @JoaoBaiao777.

The bulk update request #4362 has been rejected.

create implication mega_ampharos (471) -> generation_6_pokemon (88936)
create implication mega_steelix (21) -> generation_6_pokemon (88936)
create implication mega_scizor (38) -> generation_6_pokemon (88936)
create implication mega_heracross (11) -> generation_6_pokemon (88936)
create implication mega_houndoom (181) -> generation_6_pokemon (88936)
create implication mega_tyranitar (34) -> generation_6_pokemon (88936)

Reason: Mega Evolution was introduced in Generation 6

Mega Evolution Part 3

EDIT: The bulk update request #4362 (forum #359847) has been rejected by @JoaoBaiao777.

The bulk update request #4363 has been rejected.

create implication mega_ampharos (471) -> generation_2_pokemon (91068)
create implication mega_steelix (21) -> generation_2_pokemon (91068)
create implication mega_scizor (38) -> generation_2_pokemon (91068)
create implication mega_heracross (11) -> generation_2_pokemon (91068)
create implication mega_houndoom (181) -> generation_2_pokemon (91068)
create implication mega_tyranitar (34) -> generation_2_pokemon (91068)

Reason: All these Mega Evolutions are of Pokémon who were introduced in Generation 2

EDIT: The bulk update request #4363 (forum #359853) has been rejected by @JoaoBaiao777.

The different forms are kept separate for tagging purposes. Mega Mewtwo is not a gen 1 pokemon as it's not standard Mewtwo, Hisuian Zoroark isn't a gen 5 pokemon as it's not standard Zoroark, etc.

The bulk update request #4364 has been rejected.

Reason: Mega Evolution and Primal Reversion were introduced in Generation 6

Mega Evolution Part 4 ft. Primal Reversion

EDIT: The bulk update request #4364 (forum #359850) has been rejected by @JoaoBaiao777.

The bulk update request #4365 has been rejected.

Reason: All these Mega Evolutions and Primal Reversions are of Pokémon who were introduced in Generation 3

EDIT: The bulk update request #4365 (forum #359851) has been rejected by @JoaoBaiao777.

The bulk update request #4366 has been rejected.

create implication mega_lopunny (2204) -> generation_6_pokemon (88936)
create implication mega_garchomp (102) -> generation_6_pokemon (88936)
create implication mega_lucario (1342) -> generation_6_pokemon (88936)
create implication mega_abomasnow (8) -> generation_6_pokemon (88936)
create implication mega_gallade (61) -> generation_6_pokemon (88936)
create implication mega_audino (253) -> generation_6_pokemon (88936)
create implication mega_diancie (65) -> generation_6_pokemon (88936)

Reason: Mega Evolution was introduced in Generation 6

Mega Evolution Part 5

EDIT: The bulk update request #4366 (forum #359852) has been rejected by @JoaoBaiao777.

The bulk update request #4367 has been rejected.

create implication mega_lopunny (2204) -> generation_4_pokemon (130223)
create implication mega_garchomp (102) -> generation_4_pokemon (130223)
create implication mega_lucario (1342) -> generation_4_pokemon (130223)
create implication mega_abomasnow (8) -> generation_4_pokemon (130223)
create implication mega_gallade (61) -> generation_4_pokemon (130223)
create implication mega_audino (253) -> generation_5_pokemon (77839)

Reason: These Mega Evolutions are of Pokémon who were introduced in Generation 4 and 5

EDIT: The bulk update request #4367 (forum #359853) has been rejected by @JoaoBaiao777.

The bulk update request #4368 has been rejected.

Reason: Gigantamax was introduced in Generation 8

Gigantamax Part 1

EDIT: The bulk update request #4368 (forum #359854) has been rejected by @JoaoBaiao777.

The bulk update request #4369 has been rejected.

Reason: These Gigantamax forms are of Pokémon who were introduced in Generation 1, 5 and 7

EDIT: The bulk update request #4369 (forum #359855) has been rejected by @JoaoBaiao777.

The bulk update request #4370 has been rejected.

Reason: Gigantamax was introduced in Generation 8

Gigantamax Part 2

EDIT: The bulk update request #4370 (forum #359856) has been rejected by @JoaoBaiao777.

The bulk update request #4371 has been rejected.

remove implication unown_(pokemon) (429) -> generation_2_pokemon (91068)
create implication unown_! (42) -> generation_3_pokemon (100403)
create implication unown_? (34) -> generation_3_pokemon (100403)

Reason: Unown ! and Unown ? were introduced in Generation 3

I couldn't create an implication for Unown A to Z to generation_2_pokemon due to it already being implied to unown_(pokemon)

unown_a already implies generation_2_pokemon through another implication (create implication unown_a -> generation_2_pokemon),
unown_b already implies generation_2_pokemon through another implication (create implication unown_b -> generation_2_pokemon),
unown_c already implies generation_2_pokemon through another implication (create implication unown_c -> generation_2_pokemon),
unown_d already implies generation_2_pokemon through another implication (create implication unown_d -> generation_2_pokemon),
unown_e already implies generation_2_pokemon through another implication (create implication unown_e -> generation_2_pokemon),
unown_f already implies generation_2_pokemon through another implication (create implication unown_f -> generation_2_pokemon),
unown_g already implies generation_2_pokemon through another implication (create implication unown_g -> generation_2_pokemon),
unown_h already implies generation_2_pokemon through another implication (create implication unown_h -> generation_2_pokemon),
unown_i already implies generation_2_pokemon through another implication (create implication unown_i -> generation_2_pokemon),
unown_j already implies generation_2_pokemon through another implication (create implication unown_j -> generation_2_pokemon),
unown_k already implies generation_2_pokemon through another implication (create implication unown_k -> generation_2_pokemon),
unown_l already implies generation_2_pokemon through another implication (create implication unown_l -> generation_2_pokemon),
unown_m already implies generation_2_pokemon through another implication (create implication unown_m -> generation_2_pokemon),
unown_n already implies generation_2_pokemon through another implication (create implication unown_n -> generation_2_pokemon),
unown_o already implies generation_2_pokemon through another implication (create implication unown_o -> generation_2_pokemon),
unown_p already implies generation_2_pokemon through another implication (create implication unown_p -> generation_2_pokemon),
unown_q already implies generation_2_pokemon through another implication (create implication unown_q -> generation_2_pokemon),
unown_r already implies generation_2_pokemon through another implication (create implication unown_r -> generation_2_pokemon),
unown_s already implies generation_2_pokemon through another implication (create implication unown_s -> generation_2_pokemon),
unown_t already implies generation_2_pokemon through another implication (create implication unown_t -> generation_2_pokemon),
unown_u already implies generation_2_pokemon through another implication (create implication unown_u -> generation_2_pokemon),
unown_v already implies generation_2_pokemon through another implication (create implication unown_v -> generation_2_pokemon),
unown_w already implies generation_2_pokemon through another implication (create implication unown_w -> generation_2_pokemon),
unown_x already implies generation_2_pokemon through another implication (create implication unown_x -> generation_2_pokemon),
unown_y already implies generation_2_pokemon through another implication (create implication unown_y -> generation_2_pokemon),
unown_z already implies generation_2_pokemon through another implication (create implication unown_z -> generation_2_pokemon)

Unown

EDIT: The bulk update request #4371 (forum #359859) has been rejected by @JoaoBaiao777.

The bulk update request #4372 has been rejected.

remove implication basculin (50) -> generation_5_pokemon (77839)
create implication white-striped_basculin (10) -> generation_8_pokemon (44095)

Reason: White-striped Basculin was introduced in Generation 8

red-striped_basculin already implies generation_5_pokemon through another implication (create implication red-striped_basculin -> generation_5_pokemon),
blue-striped_basculin already implies generation_5_pokemon through another implication (create implication blue-striped_basculin -> generation_5_pokemon)

Basculin

EDIT: The bulk update request #4372 (forum #359860) has been rejected by @JoaoBaiao777.

joaobaiao777 said:
create implication okidogi (50) -> legendary_pokemon (43970)
create implication munkidori (5) -> legendary_pokemon (43970)
create implication fezandipiti (13) -> legendary_pokemon (43970)

Do we know these are "Legendary Pokemon"? Bulbapedia doesn't describe them as legendary pokemon:

https://bulbapedia.bulbagarden.net/wiki/Okidogi_(Pok%C3%A9mon)#
Okidogi (Japanese: イイネイヌ Iineinu) is a Pokémon introduced in Generation IX.

https://bulbapedia.bulbagarden.net/wiki/Munkidori_(Pok%C3%A9mon)#
Munkidori (Japanese: マシマシラ Mashimashira) is a Pokémon introduced in Generation IX.

https://bulbapedia.bulbagarden.net/wiki/Fezandipiti_(Pok%C3%A9mon)#
Fezandipiti (Japanese: キチキギス Kichikigisu) is a Pokémon introduced in Generation IX.

Unlike the cover legendaries which is does:

https://bulbapedia.bulbagarden.net/wiki/Ogerpon_(Pok%C3%A9mon)#
Ogerpon (Japanese: オーガポン Ogerpon) is a Legendary Pokémon introduced in Generation IX.

https://bulbapedia.bulbagarden.net/wiki/Terapagos_(Pok%C3%A9mon)#
Terapagos (Japanese: テラパゴス Terapagos) is a Legendary Pokémon introduced in Generation IX.

At best, this seems to indicate their status as legendary is unclear at this time.

The bulk update request #4373 has been rejected.

remove implication zygarde (422) -> generation_6_pokemon (88936)
remove alias zygarde_50_forme (106) -> zygarde (422)
create implication zygarde_cell (31) -> generation_7_pokemon (61232)
create implication zygarde_cell (31) -> zygarde (422)
remove implication zygarde_cell (31) -> zygarde_core (89)
create implication zygarde_core (89) -> generation_7_pokemon (61232)
create implication zygarde_core (89) -> zygarde (422)
remove implication zygarde_core (89) -> legendary_pokemon (68387)
create implication zygarde_10_forme (204) -> generation_7_pokemon (61232)
create implication zygarde_10_forme (204) -> zygarde (422)
remove implication zygarde_10_forme (204) -> legendary_pokemon (68387)
create implication zygarde_complete_forme (38) -> generation_7_pokemon (61232)
create implication zygarde_complete_forme (38) -> zygarde (422)
remove implication zygarde_complete_forme (38) -> legendary_pokemon (68387)

Reason: Zygarde 50% forme was introduced in generation 6
Zygarde cell, Zygarde core, Zygarde 10% forme and Zygarde complete forme were introduced in generation 7
Since Zygarde already implies legendary_pokemon, Zygarde cell, Zygarde core, Zygarde 10% forme and Zygarde complete forme won't need the implication

I couldn't create an implication for Zygarde 50% forme to zygarde due to it already being aliased to zygarde

Antecedent tag must not be aliased to another tag (create implication zygarde_50_forme -> zygarde)

Zygarde

EDIT: The bulk update request #4373 (forum #359863) has been rejected by @JohnnyB777.
Reason: It's already active.

The bulk update request #4374 has been rejected.

create implication white_kyurem (158) -> reshiram (4479)
create implication black_kyurem (49) -> zekrom (1357)

Reason: White Kyurem is the fused form of Kyurem and Reshiram
Black Kyurem is the fused form of Kyurem and Zekrom

EDIT: The bulk update request #4374 (forum #359865) has been rejected by @JoaoBaiao777.

The bulk update request #4374 (forum #359865) has been rejected by @JoaoBaiao777.

The bulk update request #4375 has been rejected.

create implication white_kyurem (158) -> reshiram (4479)
create implication black_kyurem (49) -> zekrom (1357)

Reason: White Kyurem is the fused form of Kyurem and Reshiram
Black Kyurem is the fused form of Kyurem and Zekrom

EDIT: The bulk update request #4375 (forum #359868) has been rejected by @JoaoBaiao777.

The bulk update request #4375 (forum #359868) has been rejected by @JoaoBaiao777.

The bulk update request #4376 has been rejected.

create implication origin_forme_dialga (15) -> generation_8_pokemon (44095)
create implication origin_forme_palkia (19) -> generation_8_pokemon (44095)
create alias dialga_(origin_form) (0) -> origin_forme_dialga (15)
create alias palkia_(origin_form) (0) -> origin_forme_palkia (19)

Reason: Origin Forme Dialga and Origin Forme Palkia were introduced in Generation 8

Origin Formes

EDIT: The bulk update request #4376 (forum #359870) has been rejected by @JoaoBaiao777.

The bulk update request #4377 has been rejected.

create implication white_kyurem (158) -> reshiram (4479)
create implication black_kyurem (49) -> zekrom (1357)

Reason: White Kyurem is the fused form of Kyurem and Reshiram
Black Kyurem is the fused form of Kyurem and Zekrom

EDIT: The bulk update request #4377 (forum #359873) has been rejected by @JoaoBaiao777.

The bulk update request #4378 has been rejected.

remove implication dusk_mane_necrozma (32) -> legendary_pokemon (68387)
create implication dusk_mane_necrozma (32) -> necrozma (43)
remove implication dawn_wings_necrozma (40) -> legendary_pokemon (68387)
create implication dawn_wings_necrozma (40) -> necrozma (43)
remove implication ultra_necrozma (100) -> legendary_pokemon (68387)
create implication ultra_necrozma (100) -> necrozma (43)

Reason: Dusk Mane Necrozma, Dawn Wings Necrozma and Ultra Necrozma are fused forms of Necrozma

Necrozma

EDIT: The bulk update request #4378 (forum #359874) has been rejected by @JoaoBaiao777.

The bulk update request #4379 has been rejected.

create implication dusk_mane_necrozma (32) -> solgaleo (714)
create implication dawn_wings_necrozma (40) -> lunala (510)

Reason: Dusk Mane Necrozma is the fused form of Necrozma and Solgaleo
Dawn Wings Necrozma is the fused form of Necrozma and Lunala

EDIT: The bulk update request #4379 (forum #359875) has been rejected by @JoaoBaiao777.

joaobaiao777 said:
create implication origin_forme_dialga (11) -> dialga (510)
create implication origin_forme_palkia (11) -> palkia (532)
...
create implication white_kyurem (117) -> reshiram (2334)
create implication black_kyurem (34) -> zekrom (893)

Different forms are kept separate.

The bulk update request #4380 has been rejected.

create implication ice_rider_calyrex (11) -> calyrex (158)
create implication shadow_rider_calyrex (10) -> calyrex (158)

Reason: Ice Rider Calyrex and Shadow Rider Calyrex are "fused" forms of Calyrex, Calyrex becomes whiter and its cape grows longer when it "fuses" with Glastrier or Spectrier respectively

Calyrex
Ice Rider Calyrex
Shadow Rider Calyrex

Calyrex

EDIT: The bulk update request #4380 (forum #359884) has been rejected by @JoaoBaiao777.

The bulk update request #4381 has been rejected.

create implication ice_rider_calyrex (11) -> glastrier (102)
create implication shadow_rider_calyrex (10) -> spectrier (246)

Reason: Ice Rider Calyrex and Shadow Rider Calyrex are "fused" forms of Calyrex, Calyrex becomes whiter and its cape grows longer when it "fuses" with Glastrier or Spectrier respectively

Ice Rider Calyrex is the fused form of Calyrex and Glastrier
Shadow Rider Calyrex is the fused form of Calyrex and Spectrier

Calyrex
Ice Rider Calyrex
Shadow Rider Calyrex

EDIT: The bulk update request #4381 (forum #359885) has been rejected by @JoaoBaiao777.

The bulk update request #4382 has been rejected.

create implication shadow_lugia (964) -> generation_3_pokemon (100406)
create implication shadow_mewtwo (123) -> generation_6_pokemon (88936)

Reason: Shadow Lugia only appeared in Pokémon XD: Gale of Darkness which was a part of the Generaton 3 side series
Shadow Mewtwo first appeared in Pokkén Tournament which was a part of the Generaton 6 side series

Shadow Pokémon

EDIT: The bulk update request #4382 (forum #359888) has been rejected by @JoaoBaiao777.

The bulk update request #4383 has been rejected.

create implication shadow_lugia (964) -> lugia (8523)
create implication shadow_mewtwo (123) -> mewtwo (6554)

Reason: Shadow Lugia only appeared in Pokémon XD: Gale of Darkness which was a part of the Generaton 3 side series
Shadow Mewtwo first appeared in Pokkén Tournament which was a part of the Generaton 6 side series

EDIT: The bulk update request #4383 (forum #359889) has been rejected by @JoaoBaiao777.

joaobaiao777 said:
create implication shadow_lugia (654) -> lugia (5920)
create implication shadow_mewtwo (84) -> mewtwo (4364)

Again, separate forms are kept separate.

Please don't drop a bunch of separate BURs together like this. Replies get lost in the mix, it makes it very difficult to tell which I've looked at, and impossible to notice if any get edited. Splitting them into separate BURs to bypass 25-entry limit recreates the problem that limit is there to help with.

The bulk update request #4347 (forum #359811) has been rejected by @JoaoBaiao777.

The bulk update request #4353 (forum #359825) has been rejected by @JoaoBaiao777.

The bulk update request #4356 (forum #359829) has been rejected by @JoaoBaiao777.

The bulk update request #4358 (forum #359831) has been rejected by @JoaoBaiao777.

The bulk update request #4360 (forum #359842) has been rejected by @JoaoBaiao777.

The bulk update request #4363 (forum #359848) has been rejected by @JoaoBaiao777.

The bulk update request #4365 (forum #359851) has been rejected by @JoaoBaiao777.

The bulk update request #4367 (forum #359853) has been rejected by @JoaoBaiao777.

The bulk update request #4369 (forum #359855) has been rejected by @JoaoBaiao777.

The bulk update request #4383 (forum #359889) has been rejected by @JoaoBaiao777.

joaobaiao777 said:
create implication dusk_mane_necrozma (27) -> solgaleo (507)
create implication dawn_wings_necrozma (29) -> lunala (376)

Same issue as with White/Black Kyurem and Reshiram/Zekrom. Solgaleo and Lunala are their own distinct pokemon, Necrozma's forms shouldn't get mixed in with them.

joaobaiao777 said:
create implication primary_forme_dialga (0) -> dialga (510)
...
create implication primary_forme_palkia (0) -> palkia (532)

I don't think this will work well, since "primary_forme" isn't how they're known in lore, or how people think of them. Like how charizard, meowth, etc, refer to their normal form, dialga and palkia should stay as they are since that's how people will tag them. A new tag should be made to encompass all their forms, if such an all-encompassing tag is necessary.

The bulk update request #4377 (forum #359873) has been rejected by @JoaoBaiao777.

The bulk update request #4379 (forum #359875) has been rejected by @JoaoBaiao777.

The bulk update request #4381 (forum #359885) has been rejected by @JoaoBaiao777.

The bulk update request #4345 (forum #359809) has been rejected by @JoaoBaiao777.

The bulk update request #4346 (forum #359810) has been rejected by @JoaoBaiao777.

The bulk update request #4272 (forum #359065) has been rejected by @JoaoBaiao777.

The bulk update request #4352 (forum #359824) has been rejected by @JoaoBaiao777.

The bulk update request #4355 (forum #359828) has been rejected by @JoaoBaiao777.

The bulk update request #4380 (forum #359884) has been rejected by @JoaoBaiao777.

The bulk update request #4378 (forum #359874) has been rejected by @JoaoBaiao777.

The bulk update request #4382 (forum #359888) has been rejected by @JoaoBaiao777.

The bulk update request #4357 (forum #359830) has been rejected by @JoaoBaiao777.

The bulk update request #4359 (forum #359838) has been rejected by @JoaoBaiao777.