The bulk update request #5266 is active.

remove implication unown_(pokemon) (399) -> generation_2_pokemon (72639)
create implication unown_! (42) -> generation_3_pokemon (83395)
create implication unown_? (34) -> generation_3_pokemon (83395)

Reason: Unown A to Z were introduced in Generation 2 and Unown ! and ? were introduced in Generation 3

Unown A to M can be found here
Unown N to Z can be found here
"unown_(pokemon) -> pokemon_(species)" can be found here

Unown Part 1

EDIT: The bulk update request #5266 (forum #371802) has been approved by @Rainbow_Dash.

joaobaiao777 said:
The bulk update request #5266 is active.

remove implication unown_(pokemon) (399) -> generation_2_pokemon (72639)
create implication unown_! (42) -> generation_3_pokemon (83395)
create implication unown_? (34) -> generation_3_pokemon (83395)

Reason: Unown A to Z were introduced in Generation 2 and Unown ! and ? were introduced in Generation 3

I couldn't create an implication for Unown A to Z to generation_2_pokemon due to it already being implied to unown_(pokemon)

unown_a already implies generation_2_pokemon through another implication (create implication unown_a -> generation_2_pokemon),
unown_b already implies generation_2_pokemon through another implication (create implication unown_b -> generation_2_pokemon),
unown_c already implies generation_2_pokemon through another implication (create implication unown_c -> generation_2_pokemon),
unown_d already implies generation_2_pokemon through another implication (create implication unown_d -> generation_2_pokemon),
unown_e already implies generation_2_pokemon through another implication (create implication unown_e -> generation_2_pokemon),
unown_f already implies generation_2_pokemon through another implication (create implication unown_f -> generation_2_pokemon),
unown_g already implies generation_2_pokemon through another implication (create implication unown_g -> generation_2_pokemon),
unown_h already implies generation_2_pokemon through another implication (create implication unown_h -> generation_2_pokemon),
unown_i already implies generation_2_pokemon through another implication (create implication unown_i -> generation_2_pokemon),
unown_j already implies generation_2_pokemon through another implication (create implication unown_j -> generation_2_pokemon),
unown_k already implies generation_2_pokemon through another implication (create implication unown_k -> generation_2_pokemon),
unown_l already implies generation_2_pokemon through another implication (create implication unown_l -> generation_2_pokemon),
unown_m already implies generation_2_pokemon through another implication (create implication unown_m -> generation_2_pokemon),
unown_n already implies generation_2_pokemon through another implication (create implication unown_n -> generation_2_pokemon),
unown_o already implies generation_2_pokemon through another implication (create implication unown_o -> generation_2_pokemon),
unown_p already implies generation_2_pokemon through another implication (create implication unown_p -> generation_2_pokemon),
unown_q already implies generation_2_pokemon through another implication (create implication unown_q -> generation_2_pokemon),
unown_r already implies generation_2_pokemon through another implication (create implication unown_r -> generation_2_pokemon),
unown_s already implies generation_2_pokemon through another implication (create implication unown_s -> generation_2_pokemon),
unown_t already implies generation_2_pokemon through another implication (create implication unown_t -> generation_2_pokemon),
unown_u already implies generation_2_pokemon through another implication (create implication unown_u -> generation_2_pokemon),
unown_v already implies generation_2_pokemon through another implication (create implication unown_v -> generation_2_pokemon),
unown_w already implies generation_2_pokemon through another implication (create implication unown_w -> generation_2_pokemon),
unown_x already implies generation_2_pokemon through another implication (create implication unown_x -> generation_2_pokemon),
unown_y already implies generation_2_pokemon through another implication (create implication unown_y -> generation_2_pokemon),
unown_z already implies generation_2_pokemon through another implication (create implication unown_z -> generation_2_pokemon)

More

Ah, I see. Yeah, you'd need to manually replace those implications for each one once you remove the implication.

create implication unown_a -> generation_2_pokemon
create implication unown_b -> generation_2_pokemon
create implication unown_c -> generation_2_pokemon
create implication unown_d -> generation_2_pokemon
create implication unown_e -> generation_2_pokemon
create implication unown_f -> generation_2_pokemon
create implication unown_g -> generation_2_pokemon
create implication unown_h -> generation_2_pokemon
create implication unown_i -> generation_2_pokemon
create implication unown_j -> generation_2_pokemon
create implication unown_k -> generation_2_pokemon
create implication unown_l -> generation_2_pokemon
create implication unown_m -> generation_2_pokemon
create implication unown_n -> generation_2_pokemon
create implication unown_o -> generation_2_pokemon
create implication unown_p -> generation_2_pokemon
create implication unown_q -> generation_2_pokemon
create implication unown_r -> generation_2_pokemon
create implication unown_s -> generation_2_pokemon
create implication unown_t -> generation_2_pokemon
create implication unown_u -> generation_2_pokemon
create implication unown_v -> generation_2_pokemon
create implication unown_w -> generation_2_pokemon
create implication unown_x -> generation_2_pokemon
create implication unown_y -> generation_2_pokemon
create implication unown_z -> generation_2_pokemon

The bulk update request #5266 (forum #371802) has been approved by @Rainbow_Dash.

Weird, trying to create the BUR shows that already implied for those 2nd-gen Unown, but both metasearch and Wiki fail to show the implication. Is it just stuck in limbo/not cached yet, or what?

alphamule said:
Weird, trying to create the BUR shows that already implied for those 2nd-gen Unown, but both metasearch and Wiki fail to show the implication. Is it just stuck in limbo/not cached yet, or what?

Yeah, I've been trying to create the BURs (I can't create BURs with more than 25 entries so I have to split it in half) but it says those 2nd-gen Unown already imply generation_2_pokemon through another implication, probably unown_(pokemon) but I had requested to remove the implication

It's because the implication is still in effect.
Try removing the generation_2_pokemon tag from this post post #3270841

snpthecat said:
Try removing the generation_2_pokemon tag from this post post #3270841

According to "Preview Final Tags", generation_2_pokemon is implied by unown_? (such an implication has never existed, at least directly) but not by unown_(pokemon) or any other tag. In fact, unown_(pokemon) currently has no implications whatsoever. Something's gone fucky with the backend, I fear.

wat8548 said:
According to "Preview Final Tags", generation_2_pokemon is implied by unown_? (such an implication has never existed, at least directly) but not by unown_(pokemon) or any other tag. In fact, unown_(pokemon) currently has no implications whatsoever. Something's gone fucky with the backend, I fear.

Definitely seems like it, guess we should post in the bugs thread

The bulk update request #5340 has been rejected.

remove implication unown_? (34) -> generation_2_pokemon (72639)
remove implication unown_! (42) -> generation_2_pokemon (72639)

Reason: Hmmmmm, would this do anything? Probably not.

EDIT: The bulk update request #5340 (forum #372943) has been rejected by @Earlopain.

The bulk update request #5340 (forum #372943) has been rejected by @Earlopain.

The bulk update request #5343 is active.

create implication unown_a (187) -> generation_2_pokemon (72639)
create implication unown_b (74) -> generation_2_pokemon (72639)
create implication unown_c (132) -> generation_2_pokemon (72639)
create implication unown_d (116) -> generation_2_pokemon (72639)
create implication unown_e (198) -> generation_2_pokemon (72639)
create implication unown_f (90) -> generation_2_pokemon (72639)
create implication unown_g (81) -> generation_2_pokemon (72639)
create implication unown_h (127) -> generation_2_pokemon (72639)
create implication unown_i (141) -> generation_2_pokemon (72639)
create implication unown_j (27) -> generation_2_pokemon (72639)
create implication unown_k (95) -> generation_2_pokemon (72639)
create implication unown_l (103) -> generation_2_pokemon (72639)
create implication unown_m (118) -> generation_2_pokemon (72639)

Reason: Unown A to M were introduced in Generation 2

Unown Part 2

EDIT: The bulk update request #5343 (forum #372998) has been approved by @slyroon.

The bulk update request #5344 is active.

create implication unown_n (120) -> generation_2_pokemon (72639)
create implication unown_o (166) -> generation_2_pokemon (72639)
create implication unown_p (89) -> generation_2_pokemon (72639)
create implication unown_q (33) -> generation_2_pokemon (72639)
create implication unown_r (139) -> generation_2_pokemon (72639)
create implication unown_s (137) -> generation_2_pokemon (72639)
create implication unown_t (155) -> generation_2_pokemon (72639)
create implication unown_u (115) -> generation_2_pokemon (72639)
create implication unown_v (62) -> generation_2_pokemon (72639)
create implication unown_w (85) -> generation_2_pokemon (72639)
create implication unown_x (67) -> generation_2_pokemon (72639)
create implication unown_y (95) -> generation_2_pokemon (72639)
create implication unown_z (39) -> generation_2_pokemon (72639)

Reason: Unown N to Z were introduced in Generation 2

Unown Part 3

EDIT: The bulk update request #5344 (forum #372999) has been approved by @slyroon.

bump

bump

bump

bump

bump

johnnyb777 said:
bump

Hmm, might want to avoid bumping a thread without new content, too fast.

alphamule said:
Hmm, might want to avoid bumping a thread without new content, too fast.

Meh, what they're doing isn't too outrageous. And look on the bright side, if it is, they'll get a staff response

alphamule said:
Hmm, might want to avoid bumping a thread without new content, too fast.

I'm sorry I'll stop bumping

johnnyb777 said:
I'm sorry I'll stop bumping

It actually wasn't too often. There is a huggggge wall of automod bumps recently that basically made the forum almost useless without going 5+ pages down. :facepalm:

snpthecat said:
Meh, what they're doing isn't too outrageous. And look on the bright side, if it is, they'll get a staff response

Well, true, TBF. I have a ton of BURs and such that seem uncontroversial, but still sitting in approval queue so I know it gets frustrating.

The bulk update request #5343 (forum #372998) has been approved by @slyroon.

The bulk update request #5344 (forum #372999) has been approved by @slyroon.