'House of the Dragon' omits crucial details in Stark-Targaryen pact

'House of the Dragon' season 2 returns to Winterfell but omits key aspects of the Stark-Targaryen alliance.


Pop Culture & Art June 19, 2024
-Instagram@houseofthedragonhbo

'House of the Dragon' season 2 marks the franchise's return to Winterfell, but significant details about the Starks and Targaryens' alliance are notably absent. 

Warning: Episode one spoilers ahead.

As highlighted by ScreenRant, Winterfell, a well-known location from 'Game of Thrones,' reappears in the new episodes. However, key aspects of the meeting between Jacaerys Velaryon and Cregan Stark are omitted.

The opening sequence of 'House of the Dragon' season 2, episode 1, features Lord Cregan Stark explaining the history of the Night’s Watch and the Wall to Prince Jacaerys Velaryon. During their ride to the Wall's top, Cregan mentions it keeps out "death," not just poor weather and wildlings. The scene ends with a raven bringing news of Lucerys’ death, and Jacaerys later informs Queen Rhaenyra Targaryen that Cregan pledged the North's support and 2,000 "greybeards."

However, the episode does not show the crucial Pact of Ice & Fire. According to George R.R. Martin’s 'Fire & Blood,' the pact required Jacaerys’ firstborn daughter to marry Cregan’s firstborn son in exchange for Northern support. ScreenRant points out that despite this omission, the historical alliance remains significant, symbolising the bond between the Starks and Targaryens.

Jacaerys Velaryon’s death at the Battle of the Gullet prevented the pact from being fulfilled. The closest it came to realisation was through Prince Rhaegar Targaryen's secret marriage to Lyanna Stark, resulting in their son Jon Snow, who embodies both Ice and Fire. ScreenRant notes that the omission of this pact in 'House of the Dragon' leaves a gap in the narrative, missing an important link in the 'Game of Thrones' lore.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ