Posted under Tag Alias and Implication Suggestions
The bulk update request #2786 has been rejected.
remove implication mew_(pokémon) (0) -> generation_1_pokemon (148833)
create implication mew (0) -> generation_1_pokemon (148833)
Reason: they mistagged mew when they made the generation 1 pokemon implication
EDIT: The bulk update request #2786 (forum #339262) has been rejected by @JoaoBaiao777.
Updated
The bulk update request #3011 has been rejected.
remove implication omanyte (140) -> pokémon_(species) (0)
remove implication omastar (104) -> pokémon_(species) (0)
remove implication kabuto (105) -> pokémon_(species) (0)
remove implication kabutops (130) -> pokémon_(species) (0)
remove implication aerodactyl (222) -> pokémon_(species) (0)
remove implication mega_aerodactyl (18) -> pokémon_(species) (0)
create implication mega_aerodactyl (18) -> fossil_pokémon (0)
remove implication lileep (66) -> pokémon_(species) (0)
remove implication cradily (107) -> pokémon_(species) (0)
remove implication anorith (41) -> pokémon_(species) (0)
remove implication armaldo (102) -> pokémon_(species) (0)
remove implication cranidos (60) -> pokémon_(species) (0)
remove implication rampardos (125) -> pokémon_(species) (0)
remove implication shieldon (38) -> pokémon_(species) (0)
remove implication bastiodon (47) -> pokémon_(species) (0)
Reason: fossil_pokémon already implies pokémon_(species), so tags that imply the former directly already imply the latter indirectly
EDIT: The bulk update request #3011 (forum #341858) has been rejected by @Rainbow_Dash.
Updated by furrypickle
The bulk update request #3012 has been rejected.
remove implication tirtouga (29) -> pokémon_(species) (0)
remove implication carracosta (83) -> pokémon_(species) (0)
remove implication archen (212) -> pokémon_(species) (0)
remove implication archeops (297) -> pokémon_(species) (0)
remove implication tyrunt (73) -> pokémon_(species) (0)
remove implication tyrantrum (528) -> pokémon_(species) (0)
remove implication amaura (101) -> pokémon_(species) (0)
remove implication aurorus (371) -> pokémon_(species) (0)
remove implication dracozolt (177) -> pokémon_(species) (0)
remove implication arctozolt (35) -> pokémon_(species) (0)
remove implication dracovish (65) -> pokémon_(species) (0)
remove implication arctovish (25) -> pokémon_(species) (0)
Reason: fossil_pokémon already implies pokémon_(species), so tags that imply the former directly already imply the latter indirectly
EDIT: The bulk update request #3012 (forum #341859) has been rejected by @Rainbow_Dash.
Updated by furrypickle
I would like the fossil_pokémon tag to go away entirely please.
The bulk update request #3011 (forum #341858) has been rejected by @Rainbow_Dash.
The bulk update request #3012 (forum #341859) has been rejected by @Rainbow_Dash.
The bulk update request #3166 has been rejected.
create implication primal_kyogre (96) -> generation_6_pokemon (74514)
create implication primal_groudon (115) -> generation_6_pokemon (74514)
Reason:
primal reversion was introduced in generation 6
EDIT: The bulk update request #3166 (forum #342663) has been rejected by @JoaoBaiao777.
Updated by furrypickle
joaobaiao777 said:
create implication alolan_form (4140) -> generation_7_pokemon (28812)
create implication galarian_form (996) -> generation_8_pokemon (16648)
create implication hisuian_form (2096) -> generation_8_pokemon (16648)
create implication paldean_form (19) -> generation_9_pokemon (2455)
I don't think we should implicate <region>_form to specific generations. There's nothing stopping a new Alolan, Galarian, or Hisuian form from being introduced during gen 9 or later.
New mega evolutions were added post gen6, weren't they? The same could happen with Primal, Gigantamax, and regional forms. Those concepts should not implicate a generation.
furrin_gok said:
New mega evolutions were added post gen6, weren't they?
To the fanbase's eternal chagrin, no, they were not.
wat8548 said:
To the fanbase's eternal chagrin, no, they were not.
That's surprising. Still, they could, so it shouldn't implicate a generation.
furrin_gok said:
they could
They could have not erased half of all species from existence, but hope into one hand and shit in the other and see which fills up first.
The bulk update request #3215 has been rejected.
create implication mega_venusaur (58) -> generation_6_pokemon (74514)
create implication mega_charizard (1326) -> generation_6_pokemon (74514)
create implication mega_blastoise (59) -> generation_6_pokemon (74514)
create implication mega_beedrill (25) -> generation_6_pokemon (74514)
create implication mega_pidgeot (48) -> generation_6_pokemon (74514)
create implication mega_alakazam (16) -> generation_6_pokemon (74514)
create implication mega_slowbro (9) -> generation_6_pokemon (74514)
create implication mega_gengar (140) -> generation_6_pokemon (74514)
create implication mega_kangaskhan (123) -> generation_6_pokemon (74514)
create implication mega_pinsir (9) -> generation_6_pokemon (74514)
create implication mega_gyarados (13) -> generation_6_pokemon (74514)
create implication mega_aerodactyl (18) -> generation_6_pokemon (74514)
create implication mega_aerodactyl (18) -> fossil_pokémon (0)
create implication mega_mewtwo (469) -> generation_6_pokemon (74514)
Reason: mega evolution was introduced in generation 6
mega aerodactyl is a fossil pokémon
EDIT: The bulk update request #3215 (forum #343271) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3216 has been rejected.
create implication mega_ampharos (408) -> generation_6_pokemon (74514)
create implication mega_steelix (20) -> generation_6_pokemon (74514)
create implication mega_scizor (36) -> generation_6_pokemon (74514)
create implication mega_heracross (10) -> generation_6_pokemon (74514)
create implication mega_houndoom (163) -> generation_6_pokemon (74514)
create implication mega_tyranitar (25) -> generation_6_pokemon (74514)
Reason: mega evolution was introduced in generation 6
EDIT: The bulk update request #3216 (forum #343272) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3217 has been rejected.
create implication mega_sceptile (132) -> generation_6_pokemon (74514)
create implication mega_blaziken (274) -> generation_6_pokemon (74514)
create implication mega_swampert (286) -> generation_6_pokemon (74514)
create implication mega_gardevoir (795) -> generation_6_pokemon (74514)
create implication mega_sableye (39) -> generation_6_pokemon (74514)
create implication mega_mawile (338) -> generation_6_pokemon (74514)
create implication mega_aggron (24) -> generation_6_pokemon (74514)
create implication mega_medicham (41) -> generation_6_pokemon (74514)
create implication mega_manectric (41) -> generation_6_pokemon (74514)
create implication mega_sharpedo (13) -> generation_6_pokemon (74514)
create implication mega_camerupt (6) -> generation_6_pokemon (74514)
create implication mega_banette (483) -> generation_6_pokemon (74514)
create implication mega_absol (1236) -> generation_6_pokemon (74514)
create implication mega_glalie (11) -> generation_6_pokemon (74514)
create implication mega_salamence (16) -> generation_6_pokemon (74514)
create implication mega_latias (52) -> generation_6_pokemon (74514)
create implication mega_latios (35) -> generation_6_pokemon (74514)
create implication primal_kyogre (96) -> generation_6_pokemon (74514)
create implication primal_groudon (115) -> generation_6_pokemon (74514)
create implication mega_rayquaza (156) -> generation_6_pokemon (74514)
Reason: mega evolution and primal reversion were introduced in generation 6
EDIT: The bulk update request #3217 (forum #343273) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3218 has been rejected.
create implication mega_lopunny (1851) -> generation_6_pokemon (74514)
create implication mega_garchomp (102) -> generation_6_pokemon (74514)
create implication mega_lucario (1128) -> generation_6_pokemon (74514)
create implication mega_abomasnow (8) -> generation_6_pokemon (74514)
create implication mega_gallade (56) -> generation_6_pokemon (74514)
create implication mega_audino (217) -> generation_6_pokemon (74514)
create implication mega_diancie (48) -> generation_6_pokemon (74514)
Reason: mega evolution was introduced in generation 6
EDIT: The bulk update request #3218 (forum #343274) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3219 has been rejected.
create implication gigantamax_venusaur (10) -> generation_8_pokemon (36229)
create implication gigantamax_charizard (126) -> generation_8_pokemon (36229)
create implication gigantamax_blastoise (3) -> generation_8_pokemon (36229)
create implication gigantamax_butterfree (7) -> generation_8_pokemon (36229)
create implication gigantamax_pikachu (22) -> generation_8_pokemon (36229)
create implication gigantamax_meowth (19) -> generation_8_pokemon (36229)
create implication gigantamax_machamp (18) -> generation_8_pokemon (36229)
create implication gigantamax_gengar (1) -> generation_8_pokemon (36229)
create implication gigantamax_kingler (1) -> generation_8_pokemon (36229)
create implication gigantamax_lapras (13) -> generation_8_pokemon (36229)
create implication gigantamax_eevee (50) -> generation_8_pokemon (36229)
create implication gigantamax_garbodor (0) -> generation_8_pokemon (36229)
create implication gigantamax_melmetal (0) -> generation_8_pokemon (36229)
Reason: gigantamax pokémon were introduced in generation 8
EDIT: The bulk update request #3219 (forum #343275) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3220 has been rejected.
create implication gigantamax_rillaboom (1) -> generation_8_pokemon (36229)
create implication gigantamax_cinderace (170) -> generation_8_pokemon (36229)
create implication gigantamax_inteleon (22) -> generation_8_pokemon (36229)
create implication gigantamax_corviknight (4) -> generation_8_pokemon (36229)
create implication gigantamax_orbeetle (1) -> generation_8_pokemon (36229)
create implication gigantamax_drednaw (2) -> generation_8_pokemon (36229)
create implication gigantamax_coalossal (2) -> generation_8_pokemon (36229)
create implication gigantamax_flapple (0) -> generation_8_pokemon (36229)
create implication gigantamax_appletun (0) -> generation_8_pokemon (36229)
create implication gigantamax_sandaconda (1) -> generation_8_pokemon (36229)
create implication gigantamax_toxtricity (9) -> generation_8_pokemon (36229)
create implication gigantamax_centiskorch (7) -> generation_8_pokemon (36229)
create implication gigantamax_hatterene (9) -> generation_8_pokemon (36229)
create implication gigantamax_grimmsnarl (4) -> generation_8_pokemon (36229)
create implication gigantamax_alcremie (13) -> generation_8_pokemon (36229)
create implication gigantamax_copperajah (0) -> generation_8_pokemon (36229)
create implication gigantamax_duraludon (5) -> generation_8_pokemon (36229)
create implication eternamax_eternatus (4) -> generation_8_pokemon (36229)
create implication gigantamax_urshifu (4) -> generation_8_pokemon (36229)
Reason: gigantamax pokémon were introduced in generation 8
EDIT: The bulk update request #3220 (forum #343276) has been rejected by @JoaoBaiao777.
Updated by furrypickle
joaobaiao777 said:
alolan forms were introduced in generation 7
galarian and hisuian forms were introduced in generation 8
paldean forms were introduced in generation 9
And there's nothing stopping more being introduced in a later generation. The individual pokemon should implication the generation rather than the regional form tag, just like you're doing with mega_lopunny and gigantamax_charizard implicating their generation instead of mega_evolution or gigantamax_pokemon as a whole, so the regional forms should follow suit.
The bulk update request #3233 has been rejected.
remove implication unown_(pokémon) (0) -> generation_2_pokemon (76367)
create implication unown_! (42) -> generation_3_pokemon (85966)
create implication unown_? (34) -> generation_3_pokemon (85966)
Reason: unown a to unown z were introduced in generation 2
unown ! and unown ? were introduced in generation 3
I couldn't create an implication for unown a to unown z to generation_2_pokemon due to unown_(pokémon) already having an implication to generation_2_pokemon
EDIT: The bulk update request #3233 (forum #343385) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3234 has been rejected.
remove implication basculin (39) -> generation_5_pokemon (65185)
create implication white-striped_basculin (3) -> generation_8_pokemon (36229)
Reason: red-striped_basculin and blue-striped_basculin were introduced in generation 5
white-striped_basculin was introduced in generation 8
I couldn't create an implication for red-striped_basculin and blue-striped_basculin to generation_5_pokemon due to basculin already having an implication to generation_5_pokemon
EDIT: The bulk update request #3234 (forum #343386) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3250 has been rejected.
remove implication zygarde (342) -> generation_6_pokemon (74514)
remove alias zygarde_50_forme (92) -> zygarde (342)
remove implication zygarde_cell (25) -> zygarde_core (75)
remove implication zygarde_core (75) -> legendary_pokemon (58423)
remove implication zygarde_10_forme (161) -> legendary_pokemon (58423)
remove implication zygarde_complete_forme (32) -> legendary_pokemon (58423)
create implication zygarde_cell (25) -> generation_7_pokemon (51182)
create implication zygarde_core (75) -> generation_7_pokemon (51182)
create implication zygarde_10_forme (161) -> generation_7_pokemon (51182)
create implication zygarde_complete_forme (32) -> generation_7_pokemon (51182)
create implication zygarde_cell (25) -> zygarde (342)
create implication zygarde_core (75) -> zygarde (342)
create implication zygarde_10_forme (161) -> zygarde (342)
create implication zygarde_complete_forme (32) -> zygarde (342)
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 to imply legendary_pokemon
I couldn't create an implication for zygarde 50 forme to generation_6_pokemon and zygarde due to zygarde already having an implication to generation_6_pokemon and zygarde 50 forme already being aliased to zygarde
EDIT: The bulk update request #3250 (forum #343656) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3253 has been rejected.
create implication klawf (15) -> generation_9_pokemon (17081)
create implication armarouge (92) -> generation_9_pokemon (17081)
create implication ceruledge (150) -> generation_9_pokemon (17081)
Reason: klawf, armarouge and ceruledge were reavealed in the 8th trailer for scarlet and violet
EDIT: The bulk update request #3253 (forum #343732) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3253 (forum #343732) has been rejected by @JoaoBaiao777.
The bulk update request #3343 has been rejected.
create implication wiglett (112) -> generation_9_pokemon (17081)
Reason: wiglett is a pokémon that looks like diglett
wiglett was shown in World Pokémon Ecological Society Webinar on September 28th 2022
Source: Serebii.net
EDIT: The bulk update request #3343 (forum #346023) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3352 has been rejected.
create implication alolan_rattata (179) -> generation_7_pokemon (51182)
create implication alolan_raticate (47) -> generation_7_pokemon (51182)
create implication alolan_raichu (913) -> generation_7_pokemon (51182)
create implication alolan_sandshrew (46) -> generation_7_pokemon (51182)
create implication alolan_sandslash (202) -> generation_7_pokemon (51182)
create implication alolan_vulpix (3094) -> generation_7_pokemon (51182)
create implication alolan_ninetales (1252) -> generation_7_pokemon (51182)
create implication alolan_diglett (22) -> generation_7_pokemon (51182)
create implication alolan_dugtrio (41) -> generation_7_pokemon (51182)
create implication alolan_meowth (873) -> generation_7_pokemon (51182)
create implication alolan_persian (160) -> generation_7_pokemon (51182)
create implication alolan_geodude (6) -> generation_7_pokemon (51182)
create implication alolan_graveler (7) -> generation_7_pokemon (51182)
create implication alolan_golem (8) -> generation_7_pokemon (51182)
create implication alolan_grimer (24) -> generation_7_pokemon (51182)
create implication alolan_muk (60) -> generation_7_pokemon (51182)
create implication alolan_exeggutor (163) -> generation_7_pokemon (51182)
create implication alolan_marowak (163) -> generation_7_pokemon (51182)
Reason: alolan forms were introduced in generation 7
EDIT: The bulk update request #3352 (forum #346201) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3353 has been rejected.
create implication galarian_meowth (146) -> generation_8_pokemon (36229)
create implication galarian_ponyta (572) -> generation_8_pokemon (36229)
create implication galarian_rapidash (353) -> generation_8_pokemon (36229)
create implication galarian_slowpoke (20) -> generation_8_pokemon (36229)
create implication galarian_slowbro (24) -> generation_8_pokemon (36229)
create implication galarian_farfetch'd (16) -> generation_8_pokemon (36229)
create implication galarian_weezing (22) -> generation_8_pokemon (36229)
create implication galarian_mr._mime (8) -> generation_8_pokemon (36229)
create implication galarian_articuno (56) -> generation_8_pokemon (36229)
create implication galarian_zapdos (83) -> generation_8_pokemon (36229)
create implication galarian_moltres (53) -> generation_8_pokemon (36229)
create implication galarian_slowking (17) -> generation_8_pokemon (36229)
create implication galarian_corsola (27) -> generation_8_pokemon (36229)
create implication galarian_zigzagoon (264) -> generation_8_pokemon (36229)
create implication galarian_linoone (134) -> generation_8_pokemon (36229)
create implication galarian_darumaka (8) -> generation_8_pokemon (36229)
create implication galarian_darmanitan (16) -> generation_8_pokemon (36229)
create implication galarian_yamask (8) -> generation_8_pokemon (36229)
create implication galarian_stunfisk (9) -> generation_8_pokemon (36229)
Reason: galarian forms were introduced in generation 8
EDIT: The bulk update request #3353 (forum #346202) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3354 has been rejected.
create implication hisuian_growlithe (362) -> generation_8_pokemon (36229)
create implication hisuian_arcanine (146) -> generation_8_pokemon (36229)
create implication hisuian_voltorb (10) -> generation_8_pokemon (36229)
create implication hisuian_electrode (3) -> generation_8_pokemon (36229)
create implication hisuian_typhlosion (1785) -> generation_8_pokemon (36229)
create implication hisuian_qwilfish (2) -> generation_8_pokemon (36229)
create implication hisuian_sneasel (212) -> generation_8_pokemon (36229)
create implication hisuian_samurott (371) -> generation_8_pokemon (36229)
create implication hisuian_lilligant (162) -> generation_8_pokemon (36229)
create implication hisuian_zorua (746) -> generation_8_pokemon (36229)
create implication hisuian_zoroark (1278) -> generation_8_pokemon (36229)
create implication hisuian_braviary (48) -> generation_8_pokemon (36229)
create implication hisuian_sliggoo (21) -> generation_8_pokemon (36229)
create implication hisuian_goodra (195) -> generation_8_pokemon (36229)
create implication hisuian_avalugg (5) -> generation_8_pokemon (36229)
create implication hisuian_decidueye (130) -> generation_8_pokemon (36229)
Reason: hisuian forms were introduced in generation 8
EDIT: The bulk update request #3354 (forum #346203) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3355 has been rejected.
create implication paldean_wooper (84) -> generation_9_pokemon (17081)
Reason: paldean forms were introduced in generation 9
EDIT: The bulk update request #3355 (forum #346204) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3382 has been rejected.
create implication farigiraf (361) -> generation_9_pokemon (17081)
Reason: farigiraf is the evolved form of girafarig that was revealed on the 10th trailer for scarlet and violet
EDIT: The bulk update request #3382 (forum #346783) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3384 has been rejected.
create implication shadow_lugia (832) -> generation_3_pokemon (85966)
create implication shadow_mewtwo (121) -> generation_6_pokemon (74514)
Reason: shadow lugia only appeared in Pokémon XD: Gale of Darkness which was a part of generaton 3 side series
shadow mewtwo first appeared in Pokkén Tournament which was a part of generaton 6 side series
EDIT: The bulk update request #3384 (forum #346887) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3423 has been rejected.
create implication bellibolt (15) -> generation_9_pokemon (17081)
Reason: bellibolt was reavealed in the 12th trailer for scarlet and violet
EDIT: The bulk update request #3423 (forum #347450) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3455 has been rejected.
create implication greavard (88) -> generation_9_pokemon (17081)
Reason: greavard was reavealed in the 14th trailer for scarlet and violet
EDIT: The bulk update request #3455 (forum #348249) has been rejected by @JoaoBaiao777.
Updated by furrypickle
The bulk update request #3343 (forum #346023) has been rejected by @JoaoBaiao777.
The bulk update request #3382 (forum #346783) has been rejected by @JoaoBaiao777.
The bulk update request #3423 (forum #347450) has been rejected by @JoaoBaiao777.
The bulk update request #3455 (forum #348249) has been rejected by @JoaoBaiao777.
The bulk update request #3166 (forum #342663) has been rejected by @JoaoBaiao777.
The bulk update request #2786 (forum #339262) has been rejected by @JoaoBaiao777.
The bulk update request #3215 (forum #343271) has been rejected by @JoaoBaiao777.
The bulk update request #3216 (forum #343272) has been rejected by @JoaoBaiao777.
The bulk update request #3217 (forum #343273) has been rejected by @JoaoBaiao777.
The bulk update request #3218 (forum #343274) has been rejected by @JoaoBaiao777.
The bulk update request #3219 (forum #343275) has been rejected by @JoaoBaiao777.
The bulk update request #3220 (forum #343276) has been rejected by @JoaoBaiao777.
The bulk update request #3233 (forum #343385) has been rejected by @JoaoBaiao777.
The bulk update request #3234 (forum #343386) has been rejected by @JoaoBaiao777.
The bulk update request #3250 (forum #343656) has been rejected by @JoaoBaiao777.
The bulk update request #3352 (forum #346201) has been rejected by @JoaoBaiao777.
The bulk update request #3353 (forum #346202) has been rejected by @JoaoBaiao777.
The bulk update request #3354 (forum #346203) has been rejected by @JoaoBaiao777.
The bulk update request #3355 (forum #346204) has been rejected by @JoaoBaiao777.
The bulk update request #3384 (forum #346887) has been rejected by @JoaoBaiao777.
