Sumeru Is Almost Here: Genshin Impact’s Next Special Program Will Air Early Saturday
The time to learn more about Sumeru has almost arrived.
Set your clocks and prepare your caffeine, the second half of the Genshin Impact Version 3.0 Special Program is taking place early on Saturday. At least, if you catch the Twitch version. If you’d rather get more sleep, the YouTube version will air a bit later in the day, as is normal. The Twitch version will take place a 7:00 am Eastern. Check for The YouTube version around 11:00 am Eastern.
Version 3.0 Special Program Preview
Dear Travelers,
The special program will premiere on the official Twitch on 8/13/2022 at 08:00 AM (UTC-4)!
>>>https://t.co/iSfDaE9iy6It will feature juicy details about V3.0. It will also "drop" some redemption codes & more!#GenshinImpact pic.twitter.com/4aay5YQeJ8
— Genshin Impact (@GenshinImpact) August 11, 2022
The program will cover details for the upcoming update and offer players more information on the new Sumeru region and the characters that can be found there. Players can also probably expect more details on the new creatures they’ll run into as well as the update’s associated events. As always, be sure to catch the stream the same day, even if you watch it on VOD as HoYoVerse drops codes for Primogems and other goodies. In the meantime, feel free to check out Aspen's guide on Beidou to tide you over until the stream takes place.
Related Articles
About the Author
QuintLyn is a long-time lover of all things video game related will happily talk about them to anyone that will listen. She began writing about games for various gaming sites a little over ten years ago and has taken on various roles in the games community.
More Stories by QuintLyn BowersRead Next
The back-and-forth between Microsoft and Sony only continues.
You May Enjoy
Now we have to see what fruits contract negotiations bear.
Face off against Limbo and take part in the most twisted Maplemas to date.
The game’s first ever skirmish starts today.
Current outage estimates point to at least 12 hours of downtime.
Discussion (0)