Stay up to date with notifications from The Independent

Notifications can be managed in browser preferences.

Game of Thrones season 7 episode 4: Are Jaime and Bronn dead? That ending explained by the leaked script

The episode was left in a different place to the more revealing script

Christopher Hooton
Tuesday 08 August 2017 03:07 EDT
Comments
Game of Thrones: Season 7 Episode 4 Preview

Your support helps us to tell the story

From reproductive rights to climate change to Big Tech, The Independent is on the ground when the story is developing. Whether it's investigating the financials of Elon Musk's pro-Trump PAC or producing our latest documentary, 'The A Word', which shines a light on the American women fighting for reproductive rights, we know how important it is to parse out the facts from the messaging.

At such a critical moment in US history, we need reporters on the ground. Your donation allows us to keep sending journalists to speak to both sides of the story.

The Independent is trusted by Americans across the entire political spectrum. And unlike many other quality news outlets, we choose not to lock Americans out of our reporting and analysis with paywalls. We believe quality journalism should be available to everyone, paid for by those who can afford it.

Your support makes all the difference.

Whether you watched Game of Thrones season 7's fourth episode, 'The Spoils of War', via the much-talked about leak or remained Unsullied and watched the legal HBO broadcast, you might be wondering about its major cliffhanger.

*SPOILERS AHEAD - click away if you haven't seen episode 4*

Following a stunning battle dominated by Drogon, Jaime charged at Daenerys and the temporarily downed dragon only to have a jet of fire aimed at him, Tyrion uttering: "You fucking idiot," as he watched on.

Weighed down by armour, Jaime appeared to sink at the episode's close
Weighed down by armour, Jaime appeared to sink at the episode's close

An unidentified ally came to his aide, tackling Jaime out of the way of the flames and into a nearby river - but, as fire raged above the surface, the final shot saw Jaime sinking into the water's depths.

This ending came as a surprise to those of us who read the leaked script synopsis, which detailed a more transparent (and arguably better) ending. (For a spoiler-less analysis, read Jaime actor Nikolaj Coster-Waldau's thoughts on the scene here.)

It confirms not only that Jaime surives, but that it was Bronn who saved him (not Dickon as some wondered) and that he makes it out alive too.

The excerpt in question:

'Just before Drogon strikes, Bronn dives in from the side, and tackles Jaime off his horse and over the side of the bridge. They tumble into the Blackwater Rush as Drogon fries both their horses. The rapids rush Jaime and Bronn away from the bridge and battle, Bronn holding them underwater. Above them the water's surface boils and steams under dragonflame. Drogon does not like missing meals. Drowned men float alongside them. Jaime looks down and sees an even sadder sight: living soldiers trapped on the riverbottom, their armor too heavy to swim. Their eyes look up at Jaime, beseeching him for a help he can't give, as they drown.'

With everything else in the synopsis turning out to be correct, it would be very surprising if we don't witness some of these additional events next episode, and it would be almost unthinkable for the show to have decided to switch things up and kill off Jaime and Bronn without more dialogue/closure on their characters.

As stunning as episode 4 was, it was perhaps a bit of a shame they didn't choose the original ending, the sight of the Lannister guards drowning having the potential to drive home the recklessness and short temper of Daenerys.

Game of Thrones continues Sunday nights on HBO, Sky Atlantic and NOWTV.

Join our commenting forum

Join thought-provoking conversations, follow other Independent readers and see their replies

Comments

Thank you for registering

Please refresh the page or navigate to another page on the site to be automatically logged inPlease refresh your browser to be logged in