The bulk update request #735 is active.
remove implication lance_(pokémon) (0) -> pokémon_champion (0)
remove implication steven_stone (34) -> pokémon_champion (0)
remove implication wallace_(pokémon) (0) -> pokémon_champion (0)
remove implication cynthia_(pokémon) (0) -> pokémon_champion (0)
remove implication alder_(pokémon) (0) -> pokémon_champion (0)
remove implication iris_(pokémon) (0) -> pokémon_champion (0)
remove implication diantha_(pokémon) (0) -> pokémon_champion (0)
remove implication leon_(pokémon) (0) -> pokémon_champion (0)
create implication lance_(pokémon) (0) -> pokemon_champion (831)
create implication steven_stone (34) -> pokemon_champion (831)
create implication wallace_(pokémon) (0) -> pokemon_champion (831)
create implication cynthia_(pokémon) (0) -> pokemon_champion (831)
create implication alder_(pokémon) (0) -> pokemon_champion (831)
create implication iris_(pokémon) (0) -> pokemon_champion (831)
create implication diantha_(pokémon) (0) -> pokemon_champion (831)
create implication leon_(pokémon) (0) -> pokemon_champion (831)
Reason: pokémon champion somehow currently has no uses, despite several characters implying it. However because of the non-ASCII é character, the site refuses to "create" the tag whenever a post tries to tag it via implication, causing a warning when posting and whenever the tags are edited with such a character tag in place. If the site's not going to allow non-ASCII characters on "new" tags, this may as well be changed to imply a non-ASCII version of the tag.
Alternatively, I could just do the deimplications and not imply the pokemon_champion version of the tag, if desired.
EDIT: The bulk update request #735 (forum #306242) has been approved by @Millcore.
Updated by auto moderator