June 15, 2014
“You remember where the heart is?”
Each season of Game of Thrones has been an exercise in selective adaptation, but its fourth season has been a feat of adaptive engineering. Working primarily with material from the third book but leaning heavily on the fourth and fifth in certain storylines, it is the season that has emphatically taken the “book-to-season” adaptation comparison off the table.
At the same time, though, the season has been organized around key climaxes taken directly from the third book in the series. Moreso than in other seasons, you could tell the writers were having to stretch storylines to maintain the timing they had established, creating material to flesh out the scenes on The Wall to justify the Battle of Castle Black taking place in episode nine or finding things for Arya and the Hound to do so that their scenes in “The Children” wouldn’t take place until the end of the season.
By and large, I would argue the show was successful in making the season work despite the delaying tactics. This is in part because the storyline in King’s Landing, arguably the most consistently substantial, was built for this timeline, clearly marked by two major events—the Purple Wedding and the Mountain vs. the Viper—with plenty of political intrigue in between. The other reason is that even if the material at the Wall was a bit thin in ways that even last week’s epic showdown couldn’t make up for, the season as a whole maintained a sense of forward momentum. Did this momentum extend to Bran, forgotten for multiple episodes, or to Stannis and Davos’ trip to Braavos? No. But it extended to pretty much every other storyline, and makes “The Children” the most climactic finale the series has managed yet. The inconclusiveness of “The Watchers On The Wall” may have been frustrating, but it guaranteed that there was still lots to resolve even for those of us who aren’t sitting at home with checklists of what’s “supposed” to happen in the episode.
And “The Children” resolved some of it, left some of it untouched, and by and large served as one big—and mostly effective—teaser for what’s to come.
“The Watchers On The Wall”
June 8, 2014
“Blackwater” was about convergence. It was the inevitable collision between Stannis’ claim to the throne and the Lannister powers controlling it. In truth, Stannis’ side of the battle was pretty thin, sketched in without a whole lot of detail beyond Davos and his son. It was really about how Stannis’ attack changed the power dynamics at King’s Landing, whether through Cersei’s steely resolve, Tyrion’s ingenuity and intelligence, or Joffrey’s cowardice. At a stage when this was still ostensibly a show with the Stark family as its protagonist, it was an early example of the richness of stories in King’s Landing, capable of carrying an entire episode on its own.
“The Watchers On The Wall” wants to be “Blackwater.” Neil Marshall has returned as director. Mance Rayder’s not dissimilar to Stannis, in terms of development at this stage in their respective narratives, an idea more than a person. We know characters on both sides. And like that episode, “The Watchers On The Wall” is exclusively focused on the attack on The Wall, eschewing other ongoing narratives in favor of the battle at hand.
The problem with this comparison is that I don’t know why I care about The Wall. Actually, that’s a lie: I know why I care about The Wall, which is the fact that I’ve known where this story is going from the beginning, and have been anticipating it playing out. But for those who aren’t book readers, this season has often struggled to make The Wall an integral part of this narrative. The season went through a lot of effort to flesh out the characterization. There was Jon’s attack on Craster’s Keep to keep the action quotient high and to build more content into the storyline to help delay the battle until the season’s climax. There was moving Gilly to Mole’s Town so she could offer perspective on the early phases of the attack. There was sticking with Ygritte and Tormund to preface the viciousness of the Thenns. And there was Ser Alliser and Janos Slynt conspiring to keep Jon Snow from preparing for the imminent attack in the proper fashion.
The problem is that none of this built momentum. It established the various players that are central to the battle, but it didn’t make it feel important, even though this is undoubtedly an important battle. It just paled in comparison to the immediacy of Tyrion’s plight, or the looseness of Arya and the Hound, or a range of other stories that were undoubtedly more dynamic. This doesn’t feel like the culmination of a season-long storyline. It feels like something that just got delayed, a logical climax to the season (and the book most of the season is based on) that required padding to land in this position.
The result is an episode that has to prove itself without the benefit of strong connections to the characters, or season-long storylines waiting for a climax. “The Watchers On The Wall” needs to be a self-starter, building anticipation for and delivering action that the episode’s pedigree has promised. And while a visceral piece of action filmmaking and a spectacle worthy of “Blackwater,” it proves less a climax so much as long-delayed rising action to finally bring The Wall into play in the season’s narrative.
“First Of His Name”
May 4th, 2014
“I need to be more than that.”
There’s two characters that this week’s episode title refers to, even if only one is made explicit.
“First Of His Name” directly refers to Tommen, who is indeed the first King by that name to rule over Westeros. Tommen doesn’t actually do much in the hour, though, his fate a topic of conversation for those around him more than something he gets to decide on his own. Whether in Margaery’s conversation with her grandmother last week, or Margaery’s oh-so calculated performance with Cersei this week, or Cersei’s careful conversation with her father, Tommen’s future is very much a matter of procedure.
By comparison, however, Petyr Baelish makes his own procedure. There is no coronation for “Littlefinger,” as he operates in the slimy underbelly of the political underworld (yes, underworlds have underbellies). He comes from no strong lineage, with no family to support him or noble deeds to give him claim to glory, and so he has had to toil for everything he’s ever earned. He is the first of his name in a different way, in that he is the first member of his family to be Machiavellian enough to angle his way into a position of power, providing the foundation for a legacy of his own moving forward.
This balance between the self-made Littlefinger and the anointed Tommen sits on the periphery of an episode that functions as a highly logical mid-point of the season. And yet their respective paths are placed as guideposts for other characters who are faced with decisions that could lead them down one path or the other, depending on the choices they make in a moment of transition.
June 9th, 2013
“Here only the family name matters.”
As Varys explains this fact to Shae, he’s being pragmatic: he’s trying to help someone whose very existence at King’s Landing threatens her own life and the life of the man she loves. Varys acknowledges that she has made Tyrion better. Varys acknowledges that hers is a true love. And yet Varys also gives her a collection of diamonds, telling her to sail to Pentos and start a new life for herself so that her love can do something good for Westeros without the threat of a single-named woman hanging over him.
It’s dark advice, advice that Shae refuses to take. Despite the fact that we just saw both Robb Stark and Talisa die for following true love over pragmatism, and despite the fact that Jon Snow just took three arrows from the woman he loves, Shae proves what many other characters have learned as well: there is still power in love even when all signs would suggest that trusting in such power will be your undoing.
“Mhysa” is about this love, which may seem strange in light of the fact that last week ended on such a foreboding sendoff for Robb and Catelyn Stark. And yet Game of Thrones needed a new motivation beyond ascending to the throne, a sense of purpose that could evolve beyond the War of the Five Kings and the deaths of Robert Baratheon and Ned Stark which set it off. What “Mhysa” seeks to accomplish is reframe the actions of its characters not as part of a larger power struggle, but rather as actions designed to protect their families or to protect the realm. This is not to say that we are to support the Lannisters’ cruelty or to endorse Melisandre’s sorcery, but rather that we can shift our understanding of their actions away from a part in a larger plot and instead toward what motivated them to take those steps in the first place.
It’s an enriching move that works to build a strong foundation for future seasons, although one that has some issues retroactively making some of the season’s storylines resonate in the way intended. “Mhysa” concludes a third season that was only retroactively revealed—for non-readers, at least—to be the season where Game of Thrones could no longer be simplified to a battle between the Starks of Winterfell and the Lannisters of Casterly Rock, one that did its job without necessarily connecting in the process.
“The Rains of Castamere”
June 2nd, 2013
“The closer you get, the worse the fear gets.”
Every season of Game of Thrones has built to a big event in the season’s ninth episode. As a result, the end of each season has continually created a conflict between those who have read the books and those who haven’t: the pattern means that both parties know the season is building to something major, but only those who have read the books know what that is. This wouldn’t be as much of a problem if those people didn’t really, really want to talk about it.
In the first season, I would say fans mostly tried to keep quiet about Ned Stark’s death. The first season hinged on Ned’s story, and the initial shock of his beheading gave the show its big hook that could make casual viewers into fans and help sustain the show moving forward. In the second season, the Battle of Blackwater Bay was a fairly spoiler-free form of anticipation, as there’s nothing to really spoil: no one major dies, Stannis’ attack on King’s Landing is never kept a secret, and the episode was more about execution than surprise (and well-executed it was).
The third season was always going to be the problem. The “Red Wedding” has been on the tips of readers’ tongues since they read the books, considered by most to be the definitive moment in the series. It’s the moment that makes Ned’s death look like just a drop in the bucket, and the clearest evidence of George R.R. Martin’s wanton disregard for his own characters and their happiness. From the time the show first sprung into existence, this has been the moment that book readers were waiting for, and by the time it arrived in the third season there was no longer any concern about letting viewers engage with the series on their own terms out of fear for its future. This season has all been a buildup to this moment, to the point where the phrase “Red Wedding” was something that even those who tried to avoid spoilers were probably familiar with because readers could not contain themselves.
“The Rains of Castamere” arrives with intense expectation, and like many other book readers I sat through the episode with a slightly higher heart rate. As much as I think the fans went too far in proliferating the use of “Red Wedding” and hyping this particular episode as noteworthy, thus providing non-readers enough information to potentially spoil the episode’s conclusion, I can understand why they were excited, and felt that excitement in the moments leading up to the episode and throughout. This is as intense an hour of television that Game of Thrones will produce over the course of its run, and I’d argue it’s a particularly well-executed adaptation that makes some smart choices to salt the wounds left behind by this most storied of literary–and now televisual—weddings.