What you need to know
- Niantic has teased the return of Team GO Rocket to Pokémon Go.
- Previously Niantic had announced that Team GO Rocket updates would be on hold until September.
- The Willow Report has resumed with a new Team GO Rocket storyline.
Although Niantic previously announced that Team GO Rocket would not be getting monthly updates again until September, today it teased the return of the villains of Pokémon Go with a new Willow Report. The story presented in this issue of the Willow Report referenced the recent Solstice Event, during which Team Mystic's Leader, Blanche discovered some scraps of paper containing notes linked to the infamous Team GO Rocket. Blanche brought these notes to Professor Willow saying a simple and straight forward, "Something's up."
The first scrap of paper depicted a Team GO Rocket grunt building a hot air balloon emblazoned with the Rocket R. The second scrap had the grunt in the hot air baloon dropping a net on a Pikachu from above. Recently, data miners found code in the Pokémon Go APK concerning Team GO Rocket balloons as well. It is certainly possible that the Willow Reports will continue through the summer - after all, the initial introduction to Team GO Rocket was extended over a long period of time with several Willow Reports fleshing out the story. However, I wouldn't count out Team GO Rocket showing up sooner, perhaps even in time for Pokémon GO Fest 2020.
Are you excited for the possibility of Team GO Rocket aerial attacks? Let us know in the comments below, and be sure to check out our Complete Pokédex, as well as our many Pokémon Go guides so you can be the very best like no one ever was!
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.