The bulk update request #2573 is active.

remove implication eeveelution (80897) -> pokémon (0)
create implication eeveelution (80897) -> pokémon_(species) (0)
remove implication vaporeon (15892) -> pokémon_(species) (0)
remove implication umbreon (20761) -> pokémon_(species) (0)
remove implication sylveon (17056) -> pokémon_(species) (0)
remove implication leafeon (8144) -> pokémon_(species) (0)
remove implication jolteon (7870) -> pokémon_(species) (0)
remove implication glaceon (13510) -> pokémon_(species) (0)
remove implication flareon (7482) -> pokémon_(species) (0)
remove implication espeon (9796) -> pokémon_(species) (0)
remove implication nucleon (0) -> eeveelution (80897)
remove implication olympeon (0) -> eeveelution (80897)
remove implication haunteon (1) -> eeveelution (80897)
remove implication oreon (0) -> eeveelution (80897)

Reason: All eeveelutions are species of Pokémon.

Vaporeon, Umbreon, Sylveon, Leafeon, Jolteon, Glaceon, Flareon and Espeon don't need a redundant implication.

Nucleon, Olympeon, Haunteon and Oreon are Fakémon.

EDIT: The bulk update request #2573 (forum #336313) has been approved by @bitWolfy.

gattonero2001 said:
The bulk update request #2573 is active.

remove implication eeveelution (80897) -> pokémon (0)
create implication eeveelution (80897) -> pokémon_(species) (0)
remove implication vaporeon (15892) -> pokémon_(species) (0)
remove implication umbreon (20761) -> pokémon_(species) (0)
remove implication sylveon (17056) -> pokémon_(species) (0)
remove implication leafeon (8144) -> pokémon_(species) (0)
remove implication jolteon (7870) -> pokémon_(species) (0)
remove implication glaceon (13510) -> pokémon_(species) (0)
remove implication flareon (7482) -> pokémon_(species) (0)
remove implication espeon (9796) -> pokémon_(species) (0)
remove implication nucleon (0) -> eeveelution (80897)
remove implication olympeon (0) -> eeveelution (80897)
remove implication haunteon (1) -> eeveelution (80897)
remove implication oreon (0) -> eeveelution (80897)

Reason: All eeveelutions are species of Pokémon.

Vaporeon, Umbreon, Sylveon, Leafeon, Jolteon, Glaceon, Flareon and Espeon don't need a redundant implication.

Nucleon, Olympeon, Haunteon and Oreon are Fakémon.

While I appreciate the thought, you're doing two separate things here. Removing the fakemon? Sure! But trying to do... whatever you're doing with changing the hierarchy of implication to, ultimately, the same end result? Seems a bit pointless.

votp said:
While I appreciate the thought, you're doing two separate things here. Removing the fakemon? Sure! But trying to do... whatever you're doing with changing the hierarchy of implication to, ultimately, the same end result? Seems a bit pointless.

Later on down the road when they inevitably come out with more eeveelutions, you'd only need to create the eeveelution implication. Not the eeveelution and pokemon_(species) implications. Streamlining is really the best way to consider it.

versperus said:
Later on down the road when they inevitably come out with more eeveelutions, you'd only need to create the eeveelution implication. Not the eeveelution and pokemon_(species) implications. Streamlining is really the best way to consider it.

Just seems like a lot of faff, although I question if any species with the "legendary" tag, assuming that's still around given I can't keep track of it, should also function the same way as. Seems weird that every single pokemon species except for eeveelutions and legendaries would imply the species tag, to me, though. Dunno.

votp said:
Just seems like a lot of faff, although I question if any species with the "legendary" tag, assuming that's still around given I can't keep track of it, should also function the same way as. Seems weird that every single pokemon species except for eeveelutions and legendaries would imply the species tag, to me, though. Dunno.

Not all pokémon do, though. It's an inconsistent mess. The shaymin form group does implicate pokémon_(species), and the individual forms, land_forme_shaymin and sky_forme_shaymin only implicate shaymin. In contrast, the mega charizard form group doesn't imply pokémon_(species) (and neither does Mega Evolution), expecting the individual forms of Mega Charizard X and Mega Charizard Y to implicate it. Giratina, cherrim, and castform follows shaymin's example, rather than Mega Charizard's, while Mega Mewtwo follows Mega Charizard instead of shaymin and the others.

As a consequence of this inconsistency, Shadow Mewtwo implies shadow pokémon and legendary pokémon, but is missing an implication to pokémon_(species), which neither shadow pokémon or legendary pokémon add, so Shadow Mewtwo won't automatically get the pokémon_(species) tag (even though it's impossible to have a legendary pokémon, shadow pokémon, mega evolution, eeveelution, etc, that is not a pokémon_(species)).

watsit said:
Not all pokémon do, though. It's an inconsistent mess. The shaymin form group does implicate pokémon_(species), and the individual forms, land_forme_shaymin and sky_forme_shaymin only implicate shaymin. In contrast, the mega charizard form group doesn't imply pokémon_(species) (and neither does Mega Evolution), expecting the individual forms of Mega Charizard X and Mega Charizard Y to implicate it. Giratina, cherrim, and castform follows shaymin's example, rather than Mega Charizard's, while Mega Mewtwo follows Mega Charizard instead of shaymin and the others.

As a consequence of this inconsistency, Shadow Mewtwo implies shadow pokémon and legendary pokémon, but is missing an implication to pokémon_(species), which neither shadow pokémon or legendary pokémon add, so Shadow Mewtwo won't automatically get the pokémon_(species) tag (even though it's impossible to have a legendary pokémon, shadow pokémon, mega evolution, eeveelution, etc, that is not a pokémon_(species)).

... Fuck. Maybe we should devote an entire thread to just unfucking that entire snarl.

votp said:
... Fuck. Maybe we should devote an entire thread to just unfucking that entire snarl.

If we go by the other species tags, then a given species should only tag the next higher group. Which would mean, for example, Mega Charizard X should only implicate Mega Charizard, which should only implicate Mega Evolution. which should implicate pokémon_(species). Like how red fox implicates fox and gets to canid through that series of implications instead of implicating canid directly itself, it doesn't make sense to have mega charizard x implicate pokémon_(species) directly itself, rather than getting it through the implication chain it fits in.

The bulk update request #2573 (forum #336313) has been approved by @bitWolfy.