The bulk update request #4633 is active.

create implication mega_venusaur (58) -> generation_6_pokemon (71919)
create implication mega_charizard (1307) -> generation_6_pokemon (71919)
create implication mega_blastoise (59) -> generation_6_pokemon (71919)
create implication mega_alakazam (16) -> generation_6_pokemon (71919)
create implication mega_gengar (140) -> generation_6_pokemon (71919)
create implication mega_kangaskhan (124) -> generation_6_pokemon (71919)
create implication mega_pinsir (9) -> generation_6_pokemon (71919)
create implication mega_gyarados (12) -> generation_6_pokemon (71919)
create implication mega_aerodactyl (18) -> generation_6_pokemon (71919)
create implication mega_mewtwo (455) -> generation_6_pokemon (71919)
create implication mega_ampharos (400) -> generation_6_pokemon (71919)
create implication mega_scizor (36) -> generation_6_pokemon (71919)
create implication mega_heracross (10) -> generation_6_pokemon (71919)

Reason: Reason: These Mega Evolutions were officially introduced in Pokémon X & Y

Mega Evolution Part 1

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

The bulk update request #4634 is active.

create implication mega_houndoom (163) -> generation_6_pokemon (71919)
create implication mega_tyranitar (24) -> generation_6_pokemon (71919)
create implication mega_blaziken (272) -> generation_6_pokemon (71919)
create implication mega_gardevoir (772) -> generation_6_pokemon (71919)
create implication mega_mawile (332) -> generation_6_pokemon (71919)
create implication mega_aggron (24) -> generation_6_pokemon (71919)
create implication mega_medicham (41) -> generation_6_pokemon (71919)
create implication mega_manectric (38) -> generation_6_pokemon (71919)
create implication mega_banette (478) -> generation_6_pokemon (71919)
create implication mega_absol (1210) -> generation_6_pokemon (71919)
create implication mega_garchomp (101) -> generation_6_pokemon (71919)
create implication mega_lucario (1113) -> generation_6_pokemon (71919)
create implication mega_abomasnow (7) -> generation_6_pokemon (71919)

Reason: Reason: These Mega Evolutions were officially introduced in Pokémon X & Y

Mega Evolution Part 2

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

The bulk update request #4635 is active.

Reason: Reason: These Mega Evolutions were officially introduced in Pokémon Omega Ruby & Alpha Sapphire

Mega Evolution Part 3

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

The bulk update request #4636 is active.

create implication mega_aerodactyl (18) -> fossil_pokemon (2523)

Reason: Reason: Mega Aerodactyl is the Mega Evolution of Aerodactyl, which is a fossil Pokémon

Mega Evolution Part 4

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

The bulk update request #4637 is active.

create implication primal_kyogre (96) -> generation_6_pokemon (71919)
create implication primal_groudon (113) -> generation_6_pokemon (71919)

Reason: Reason: Primal Kyogre and Primal Groudon were officially introduced in Pokémon Omega Ruby & Alpha Sapphire

Primal Reversion

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

joaobaiao777 said:
Reason: Reason: Mega Aerodactyl is the Mega Evolution of Aerodactyl, which is a fossil Pokémon

Please stop rejecting and remaking the same implication requests again. It's one thing if the BUR has issues and need to be redone, and editing them is somehow less convenient, but some of these like this one are literally the same exact thing you've requested before (or three times, if we include the one in this thread ).

Watsit's right. If the problem is that the BURs are not being approved or rejected quickly enough for your tastes, rejecting and reposting the exact same BURs again won't get them approved/rejected any faster and might even slow things down because now the vetting process has to start over from the beginning. If you're concerned that your BURs aren't being approved quickly, link them in "this thread" and then do what the rest of us have to do: wait until an Admin can muster the energy to look it over, read through the opinions of those supporting and against it (if any; the previous threads had the discussions, and now an Admin has to go track them down, thus slowing approval/denial even further), do any necessary additional research, perhaps discuss it with other staff, hate their lives for a few minutes, and then make a decision. Patience is key.

I'm sorry, I had changed my mind and I wanted the Mega Aerodactyl BUR to be in this BUR

joaobaiao777 said:
I'm sorry, I had changed my mind and I wanted the Mega Aerodactyl BUR to be in this BUR

You can edit BURs...

I know, but I don't think we can move Tag Implications to BURs

joaobaiao777 said:
I know, but I don't think we can move Tag Implications to BURs

You can add new BURs to existing threads, as you've done here. And related requests don't have to all be moved to a single thread if they already exist and can't be put together. You can mention them in the description, like "See also topic #36965 for Mega Aerodactyl" or something.

You're right, I forgot to do that and rejected the Tag Implcation and I apologize for that

joaobaiao777 said:
I know, but I don't think we can move Tag Implications to BURs

On top of linking to and from a stray request's thread, you can also cancel the implication request yourself (as that's possible now) and then add the implication to a BUR as appropriate.

joaobaiao777 said:
You're right, I forgot to do that and rejected the Tag Implcation and I apologize for that

Learning curves. Mistakes can be embarrassing, but as long as we learn from them, they're not so bad.

clawstripe said:
Learning curves. Mistakes can be embarrassing, but as long as we learn from them, they're not so bad.

Thanks for understanding

clawstripe said:
On top of linking to and from a stray request's thread, you can also cancel the implication request yourself (as that's possible now) and then add the implication to a BUR as appropriate.

How does anyone cancel an implication or an alias request?

joaobaiao777 said:
Thanks for understanding

How does anyone cancel an implication or an alias request?

This is news to me too, but from the looks of it, you can click on a implication, alias, or BUR request that you made, which in your case would be the text bulk update request #4633 in the topic post, and so on. There, there's a button that says "reject", which I believe lets you cancel your own request. If it's a BUR, there will also be an "edit" button.

penguinempire-dennis said:
This is news to me too, but from the looks of it, you can click on a implication, alias, or BUR request that you made, which in your case would be the text bulk update request #4633 in the topic post, and so on. There, there's a button that says "reject", which I believe lets you cancel your own request. If it's a BUR, there will also be an "edit" button.

But the "reject" button lets you reject your own request, it doesn't cancel it. And I know how to reject and edit my requests but I don't know to cancel a request, but thank you anyways.

joaobaiao777 said:
But the "reject" button lets you reject your own request, it doesn't cancel it. And I know how to reject and edit my requests but I don't know to cancel a request, but thank you anyways.

Canceling a request is the same thing as rejecting it. They're the same thing, so you don't need to worry that you've missed any hidden commands or something.

clawstripe said:
Canceling a request is the same thing as rejecting it. They're the same thing, so you don't need to worry that you've missed any hidden commands or something.

Thank you for the explanation. I thought that they weren't the same.

bump

The bulk update request #4633 (forum #363718) has been approved by @Rainbow_Dash.

The bulk update request #4637 (forum #363722) has been approved by @Rainbow_Dash.

The bulk update request #4636 (forum #363721) has been approved by @Rainbow_Dash.

The bulk update request #4635 (forum #363720) has been approved by @Rainbow_Dash.

The bulk update request #4634 (forum #363719) has been approved by @Rainbow_Dash.