Implicating regional_variant → pokémon
Link to implication

Reason:

For some reason this isn't implied to pokémon, which leads to some posts involving them not being tagged as pokémon despite containing pokémon. Implying to pokémon would fix this

Related Pokémon Implications

• alolan diglett → regional variant
• alolan dugtrio → regional variant
• alolan geodude → regional variant
• alolan golem → regional variant
• alolan graveler → regional variant
• alolan grimer → regional variant
• alolan muk → regional variant
• alolan persian → regional variant
• alolan raticate → regional variant
• alolan rattata → regional variant
• baile oricorio → oricorio²
• buzzwole → ultra beast
• celesteela → ultra beast
• dusk lycanroc → lycanroc²
• guzzlord → ultra beast
• kartana → ultra beast
• nihilego → ultra beast
• pa'u oricorio → oricorio²
• pheromosa → ultra beast
• pom-pom oricorio → oricorio²
• sensu oricorio → oricorio²
• ultra beast → pokémon
• xurkitree → ultra beast

Related Pokémon Aliases

• alolan variant → regional variant
• alolan → regional variant
• oricorio baile style → baile oricorio³
• oricorio pa'u style → pa'u oricorio³
• oricorio pom-pom style → pom-pom oricorio³
• oricorio sensu style → sensu oricorio³
• pau oricorio → pa'u oricorio³
• pompom oricorio → pom-pom oricorio³

Related Pokémon Unimplications

• Unimplicate pokémon from alolan exeggutor¹
• Unimplicate pokémon from alolan ninetales¹
• Unimplicate pokémon from alolan sandshrew¹
• Unimplicate pokémon from alolan vulpix¹
• Unimplicate pokémon from buzzwole¹
• Unimplicate pokémon from celesteela¹
• Unimplicate pokémon from guzzlord¹
• Unimplicate pokémon from kartana¹
• Unimplicate pokémon from nihilego¹
• Unimplicate pokémon from pheromosa¹
• Unimplicate pokémon from xurkitree¹

¹ Its implication to another tag I suggested will be implied to pokémon already, making this implication redundant.
² I understand that usually alternate forms do not get implied to the original, but similar to how midday and midnight lycanroc are implied to lycanroc and considering the unique circumstances of these species, I feel the implications in these cases are warranted. Ergo the implication suggestion.
³ Not used often, but could help fix mistags due to these being not too uncommon alternate names/misspellings

DiceLovesBeingBlown said:

• regional_variant → pokémon

-1. Explanation below:

I) Was previously discussed that all pokémon species should imply 'pokémon' directly.

II) There are fanmade regional variants (fakémon).

e.g. post #1269739

DiceLovesBeingBlown said:

Implications:

• alolan diglett → regional variant
• alolan dugtrio → regional variant
• alolan geodude → regional variant
• alolan golem → regional variant
• alolan graveler → regional variant
• alolan grimer → regional variant
• alolan muk → regional variant
• alolan persian → regional variant
• alolan raticate → regional variant
• alolan rattata → regional variant

+1. Seem appropriate.

DiceLovesBeingBlown said:

Aliases:

• alolan variant → regional variant
• alolan → regional variant

-1. Explanation below:

I) They are unused.

II) One among those may be necessary in the future.

DiceLovesBeingBlown said:

Implications:

• ultra beast → pokémon
• buzzwole → ultra beast
• celesteela → ultra beast
• guzzlord → ultra beast
• kartana → ultra beast
• nihilego → ultra beast
• pheromosa → ultra beast
• xurkitree → ultra beast

Already suggested at forum #227731.

DiceLovesBeingBlown said:

Implications:

• baile oricorio → oricorio
• pa'u oricorio → oricorio
• pom-pom oricorio → oricorio
• sensu oricorio → oricorio

• dusk lycanroc → lycanroc

Aliases:

• oricorio baile style → baile oricorio
• oricorio pa'u style → pa'u oricorio
• pau oricorio → pa'u oricorio
• oricorio pom-pom style → pom-pom oricorio
• pompom oricorio → pom-pom oricorio
• oricorio sensu style → sensu oricorio

-1. We are planning to standardize the names of the alternative forms for [pokémon]_([form]_form).
Actually, I volunteered doing the changes myself, but I am still waiting for permission.

DiceLovesBeingBlown said:

Unimplications:

• alolan exeggutor → pokémon
• alolan ninetales → pokémon
• alolan sandshrew → pokémon
• alolan vulpix → pokémon
• buzzwole → pokémon
• celesteela → pokémon
• guzzlord → pokémon
• kartana → pokémon
• nihilego → pokémon
• pheromosa → pokémon
• xurkitree → pokémon

-1. Was previously discussed that all pokémon species should imply 'pokémon' directly.

-/-/-/-/-/-/-/-

I suggest implying:

• alolan diglett → pokémon.
• alolan dugtrio → pokémon.
• alolan geodude → pokémon.
• alolan graveler → pokémon.
• alolan golem → pokémon.
• alolan grimer → pokémon.
• alolan muk → pokémon.
• alolan_meowth → pokémon.
• alolan persian → pokémon.
• alolan rattata → pokémon.
• alolan raticate → pokémon.
• alolan_sandslash → pokémon.
• alolan_raichu → pokémon.
• alolan_marowak → pokémon.

Bumping this. I don't know or want to bother with which direction this should go, all I do know is I ran into an alolan raichu that wasn't tagged pokemon.

Oricorios and Lycanrocs have no "default form," so I think they should stay as is.

Furrin_Gok said:
Oricorios and Lycanrocs have no "default form," so I think they should stay as is.

should we then make the plain lycanroc and oricorio tags aliased to pokemon so only the legit forms are used in tagging?

edit: or actually a disembag tag for both could be useful (aka, lycanroc (disambiguation) and oricorio (disambiguation))

DiceLovesBeingBlown said:
should we then make the plain lycanroc and oricorio tags aliased to pokemon so only the legit forms are used in tagging?

edit: or actually a disembag tag for both could be useful (aka, lycanroc (disambiguation) and oricorio (disambiguation))

No, the base tags are useful when you don't care what form you're finding, or don't know enough about the species to know which form it is. Some people who upload the pokemon related art might only know "oh these dancer birds are oricorio" and that's the limit of their knowledge.