Topic: [APPROVED] Generation from gigantamax

Posted under Tag Alias and Implication Suggestions

The bulk update request #6020 is active.

create implication gigantamax_inteleon (22) -> generation_8_pokemon (35607)
create implication gigantamax_cinderace (169) -> generation_8_pokemon (35607)
create implication gigantamax_hatterene (9) -> generation_8_pokemon (35607)
create implication gigantamax_toxtricity (9) -> generation_8_pokemon (35607)
create implication gigantamax_centiskorch (7) -> generation_8_pokemon (35607)
create implication gigantamax_grimmsnarl (4) -> generation_8_pokemon (35607)
create implication gigantamax_corviknight (4) -> generation_8_pokemon (35607)
create implication gigantamax_orbeetle (1) -> generation_8_pokemon (35607)
create implication gigantamax_drednaw (2) -> generation_8_pokemon (35607)
create implication gigantamax_coalossal (2) -> generation_8_pokemon (35607)
create implication gigantamax_flapple (0) -> generation_8_pokemon (35607)
create implication gigantamax_alcremie (13) -> generation_8_pokemon (35607)
create implication gigantamax_copperajah (0) -> generation_8_pokemon (35607)
create implication gigantamax_duraludon (5) -> generation_8_pokemon (35607)
create implication eternamax_eternatus (4) -> generation_8_pokemon (35607)
create implication gigantamax_rillaboom (1) -> generation_8_pokemon (35607)
create implication gigantamax_venusaur (10) -> generation_8_pokemon (35607)
create implication gigantamax_charizard (126) -> generation_8_pokemon (35607)
create implication gigantamax_blastoise (3) -> generation_8_pokemon (35607)
create implication gigantamax_butterfree (7) -> generation_8_pokemon (35607)
create implication gigantamax_pikachu (22) -> generation_8_pokemon (35607)
create implication gigantamax_meowth (19) -> generation_8_pokemon (35607)
create implication gigantamax_machamp (18) -> generation_8_pokemon (35607)
create implication gigantamax_gengar (1) -> generation_8_pokemon (35607)
create implication gigantamax_kingler (1) -> generation_8_pokemon (35607)

Reason: it seems necessary to me

EDIT: The bulk update request #6020 (forum #383877) has been approved by @Rainbow_Dash.

Updated by auto moderator

anguirus12345 said:
The bulk update request #6020 is active.

create implication gigantamax_inteleon (22) -> generation_8_pokemon (35607)
create implication gigantamax_cinderace (169) -> generation_8_pokemon (35607)
create implication gigantamax_hatterene (9) -> generation_8_pokemon (35607)
create implication gigantamax_toxtricity (9) -> generation_8_pokemon (35607)
create implication gigantamax_centiskorch (7) -> generation_8_pokemon (35607)
create implication gigantamax_grimmsnarl (4) -> generation_8_pokemon (35607)
create implication gigantamax_corviknight (4) -> generation_8_pokemon (35607)
create implication gigantamax_orbeetle (1) -> generation_8_pokemon (35607)
create implication gigantamax_drednaw (2) -> generation_8_pokemon (35607)
create implication gigantamax_coalossal (2) -> generation_8_pokemon (35607)
create implication gigantamax_flapple (0) -> generation_8_pokemon (35607)
create implication gigantamax_alcremie (13) -> generation_8_pokemon (35607)
create implication gigantamax_copperajah (0) -> generation_8_pokemon (35607)
create implication gigantamax_duraludon (5) -> generation_8_pokemon (35607)
create implication eternamax_eternatus (4) -> generation_8_pokemon (35607)
create implication gigantamax_rillaboom (1) -> generation_8_pokemon (35607)
create implication gigantamax_venusaur (10) -> generation_8_pokemon (35607)
create implication gigantamax_charizard (126) -> generation_8_pokemon (35607)
create implication gigantamax_blastoise (3) -> generation_8_pokemon (35607)
create implication gigantamax_butterfree (7) -> generation_8_pokemon (35607)
create implication gigantamax_pikachu (22) -> generation_8_pokemon (35607)
create implication gigantamax_meowth (19) -> generation_8_pokemon (35607)
create implication gigantamax_machamp (18) -> generation_8_pokemon (35607)
create implication gigantamax_gengar (1) -> generation_8_pokemon (35607)
create implication gigantamax_kingler (1) -> generation_8_pokemon (35607)

Reason: it seems necessary to me

I have a doubt, although some pokemons on this list have original forms from the first generation, all gigantamax forms were introduced in the 8th generation. Would it be correct to mark them as octave or should I keep the generation of the original form?

Watsit

Privileged

The forms should only implicate the generation it was added in, not the generation the base form was added in. Gigantamax charizard and the others weren't added in gen 1, just like mega forms, alolan forms, etc, weren't.

watsit said:
The forms should only implicate the generation it was added in, not the generation the base form was added in. Gigantamax charizard and the others weren't added in gen 1, just like mega forms, alolan forms, etc, weren't.

So they all have to be on the 8th generation?

  • 1