But Wait! There's Lore! cover logo

Incident Report

1h 9m · But Wait! There's Lore! · 29 Jun 13:00

Pride, Impervium, & Shanyn discuss the "Incident Report" and subsequent journal entries about the 'Cosmic Forces' of the universe.

The crew also disucsses the revelations from Ion Hazzikostas and Steve Danuser interviews that have come up recently about the fates of Sylvannas & Nathanos.

PLUS the crew spotlights a quiz making content creator and take on his lore challenge.

All this and more on But Wait! There's Lore!

The episode Incident Report from the podcast But Wait! There's Lore! has a duration of 1:09:42. It was first published 29 Jun 13:00. The cover art and the content belong to their respective owners.

More episodes from But Wait! There's Lore!

Not Metzen Around

Pride & Impervium share their thoughts on the announcements and information coming out of Blizzcon 2023!

Family

On this episode of But Wait! There's Lore! Pride & Impervium geek out over the return of Chris Metzen, as well as go into detail about the Azure Span main quest storyline, the history of some of the blue dragons that make cameo appearances. All this and more on a particular "Fast and Furious" episode!

The Meat is Good

Pride & Impervium join forces once again and fly through the new lore and story surrounding the first two zones of World of Warcraft : Dragonflight!

The Medivh Theory

Pride & Impervium are joined by special giest Dracoris of the LFR Podcast as they give their thoughts on where the last, secret chapter of the Chains of Domination campaign.

Dracoris drops a huge theory about the connections between Tal-Galan and the super mage Medivh. is the "Keeper of Secrets" hiding something sinister?

The New Cosmology

Pride & Impervium Share their favorite moments from the story (so far) of patch 9.1, and dip their toes into the "GGrimoire of the Shadowlands and Beyond" book including the "correct" cosmology chart, and the true motivations for Sylvanas burning Teldrassil to the ground!

Every Podcast » But Wait! There's Lore! » Incident Report