What you need to know
- After a week of downtime, the Pokémon Go Battle League is back.
- Season Two has been extended to July 27, 2020.
- Other modifications have been made to Season Two.
After a bug in the Pokémon Go Battle League was exploited, leading to at least one player topping the leaderboard seemingly overnight, Niantic disabled all battles a week ago. Now, the bug has been addressed and the Pokémon Go Battle League Season Two has resumed. As a result of the downtime, Season Two will now conclude on July 27, 2020. In addition to extending the season, Niantic has implemented the following changes:
- Daily set limits have been increased from five to six for the remainder of the season.
- Beginning on Tuesday, June 23, 2020, at 1 PM PST, rewards for the Pokémon Go Battle League will be boosted.
- Snivy, Tepig, and Oshawatt will no longer be reward encounters.
- Premium Track rewards will now feature Rare Candy on the fourth win, as opposed to the fifth.
- The Pokémon Go Battle League Leaderboard will be disabled until further notice.
Further, Niantic explained briefly how they fixed this particular bug. Now the battle system will completely ignore any sequence of attacks which are not logically possible. This seems to confirm that the issue in question was the Melmetal bug in which Melmetal was able to continue fast attacks while its charged attack was charging.
So there you have it Trainers. Time to get back to battling! And be sure to check out our Complete Pokédex, as well as our many Pokémon Go guides so you too can be the very best like no one ever was!
Get the best of iMore in in your inbox, every day!
Casian Holly has been writing about gaming at iMore since 2019, but their real passion is Pokémon. From the games to the anime, cards and toys, they eat, sleep, and breathe all things Pokémon. You can check out their many Pokémon Go and Pokémon Sword and Shield guides and coverage here on iMore.
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.