Topic: [CANCELLED] Regional Forms

Posted under Tag Alias and Implication Suggestions

The bulk update request #3480 has been rejected.

create implication alolan_rattata (177) -> generation_7_pokemon (50116)
create implication alolan_raticate (41) -> generation_7_pokemon (50116)
create implication alolan_raichu (886) -> generation_7_pokemon (50116)
create implication alolan_sandshrew (45) -> generation_7_pokemon (50116)
create implication alolan_sandslash (199) -> generation_7_pokemon (50116)
create implication alolan_vulpix (3003) -> generation_7_pokemon (50116)
create implication alolan_ninetales (1229) -> generation_7_pokemon (50116)
create implication alolan_diglett (22) -> generation_7_pokemon (50116)
create implication alolan_dugtrio (41) -> generation_7_pokemon (50116)
create implication alolan_meowth (852) -> generation_7_pokemon (50116)
create implication alolan_persian (159) -> generation_7_pokemon (50116)
create implication alolan_geodude (6) -> generation_7_pokemon (50116)
create implication alolan_graveler (7) -> generation_7_pokemon (50116)
create implication alolan_golem (8) -> generation_7_pokemon (50116)
create implication alolan_grimer (24) -> generation_7_pokemon (50116)
create implication alolan_muk (60) -> generation_7_pokemon (50116)
create implication alolan_exeggutor (158) -> generation_7_pokemon (50116)
create implication alolan_marowak (161) -> generation_7_pokemon (50116)

Reason: alolan forms were introduced in generation 7

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

Updated

The bulk update request #3481 has been rejected.

create implication galarian_meowth (142) -> generation_8_pokemon (35338)
create implication galarian_ponyta (550) -> generation_8_pokemon (35338)
create implication galarian_rapidash (347) -> generation_8_pokemon (35338)
create implication galarian_slowpoke (20) -> generation_8_pokemon (35338)
create implication galarian_slowbro (22) -> generation_8_pokemon (35338)
create implication galarian_farfetch'd (16) -> generation_8_pokemon (35338)
create implication galarian_weezing (22) -> generation_8_pokemon (35338)
create implication galarian_mr._mime (8) -> generation_8_pokemon (35338)
create implication galarian_articuno (55) -> generation_8_pokemon (35338)
create implication galarian_zapdos (83) -> generation_8_pokemon (35338)
create implication galarian_moltres (53) -> generation_8_pokemon (35338)
create implication galarian_slowking (17) -> generation_8_pokemon (35338)
create implication galarian_corsola (27) -> generation_8_pokemon (35338)
create implication galarian_zigzagoon (283) -> generation_8_pokemon (35338)
create implication galarian_linoone (130) -> generation_8_pokemon (35338)
create implication galarian_darumaka (8) -> generation_8_pokemon (35338)
create implication galarian_darmanitan (16) -> generation_8_pokemon (35338)
create implication galarian_yamask (8) -> generation_8_pokemon (35338)
create implication galarian_stunfisk (9) -> generation_8_pokemon (35338)

Reason: galarian forms were introduced in generation 8

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

Updated by furrypickle

The bulk update request #3482 has been rejected.

create implication hisuian_growlithe (360) -> generation_8_pokemon (35338)
create implication hisuian_arcanine (140) -> generation_8_pokemon (35338)
create implication hisuian_voltorb (10) -> generation_8_pokemon (35338)
create implication hisuian_electrode (3) -> generation_8_pokemon (35338)
create implication hisuian_typhlosion (1692) -> generation_8_pokemon (35338)
create implication hisuian_qwilfish (2) -> generation_8_pokemon (35338)
create implication hisuian_sneasel (205) -> generation_8_pokemon (35338)
create implication hisuian_samurott (367) -> generation_8_pokemon (35338)
create implication hisuian_lilligant (157) -> generation_8_pokemon (35338)
create implication hisuian_zorua (729) -> generation_8_pokemon (35338)
create implication hisuian_zoroark (1243) -> generation_8_pokemon (35338)
create implication hisuian_braviary (48) -> generation_8_pokemon (35338)
create implication hisuian_sliggoo (21) -> generation_8_pokemon (35338)
create implication hisuian_goodra (188) -> generation_8_pokemon (35338)
create implication hisuian_avalugg (5) -> generation_8_pokemon (35338)
create implication hisuian_decidueye (126) -> generation_8_pokemon (35338)

Reason: hisuian forms were introduced in generation 8

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

Updated by furrypickle

I've been manually adding generation_8_pokemon to Hisuian form Pokemon for a while now. Regional forms are among the only Pokemon that don't get the generation_[x]_pokemon tag. I'm personally in favor of them being tagged with the generation they were introduced in, and I'd love to see a ruling on this as well as the other alternate "gimmick" forms (Megas and Gigantamax).

Is there a particular reason why each species needs its own implication instead of just "alolan form -> generation 7" for example?

gattonero2001 said:
Is there a particular reason why each species needs its own implication instead of just "alolan form -> generation 7" for example?

It depends if you want to assume there will be no new pokemon in those various forms. If another alolan form shows up during gen 9 or 10 or something, they wouldn't be gen 7, making that a bad implication.

watsit said:
It depends if you want to assume there will be no new pokemon in those various forms. If another alolan form shows up during gen 9 or 10 or something, they wouldn't be gen 7, making that a bad implication.

Does Pokémon ever do that, though?

scaliespe said:
Does Pokémon ever do that, though?

It's only been a couple generations since they started doing regional forms, so I'm not sure we have enough data to say if they would ever do that. But during gen 8, they did revisit the gen 4 region and created new regional forms for it; if there had been Sinnoh forms back during Gen 4 originally, if Legends Arceus didn't use an alternate name for the Sinnoh region there would've been regional forms split across generations.

Personally I think regional forms should implicate both the generation of the initial Pokémon and the generation of the regional form—after all, the design work was obviously divided between the two. Furthermore, the regional form should implicate the main form. However, precedent (such as asriel_dreemurr and asriel_dreemurr_(god_form)) might be working against doing that.

  • 1