“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.